native-mcpOne binary. Every MCP.

A suite of Model Context Protocol servers packaged as a single static binary — no Node, no Python, no uv. Drop-in for any MCP-aware client.

Install

View on GitHub

Single static binary

One ~3 MB executable replaces N npm/uvx tool installs. No runtime to install, no version drift.

Fast cold start

Sub-50ms startup, ~10 MB resident memory. Built for stdio MCP clients that spawn servers per session.

MCP-conformant

Strict JSON-RPC 2.0 over stdio. Works with Claude Code, Claude Desktop, Cursor, Continue, Cline, Zed, the official MCP Inspector, and anything else that speaks the protocol.

Sandbox-first

Every server that touches the system declares its scope via CLI flags. No implicit access, no surprises.

Why native-mcp

The official MCP ecosystem ships some servers as npm packages, others through uvx/PyPI. That fragmentation costs every consumer:

Slow startup — npm/uv resolve dependencies and warm up runtimes on every spawn.
High memory — 30–60 MB per running server.
Runtime sprawl — users have to install Node and Python just to run a tool server.
Painful packaging — distributing apps that depend on these servers means bundling entire language runtimes.

native-mcp collapses the suite into one statically-linked Go binary that dispatches by subcommand:

bash

native-mcp time
native-mcp filesystem /tmp /home/user/docs
native-mcp fetch

Every subcommand is a fully MCP-conformant server. Because it speaks the standard protocol, the same binary plugs into any MCP client — see the client guides for setup snippets.