The design still reads sensibly — configuration lives in an app with a GUI rather than in JSON you hand-edit, workspaces let you swap whole tool sets in one click, and namespace isolation keeps merged tool names apart. But the maintainers have marked this local proxy deprecated in the 2.0 all-in-one architecture, so check what MetaMCP 2.0 offers before building around this package.
A local proxy server that aggregates multiple MCP servers behind one connection. It fetches tool, prompt and resource configuration from MetaMCP App and routes each request to the correct underlying server, aggregating the tool lists into one. Its README opens with a deprecation warning: the package is deprecated in MetaMCP's 2.0 all-in-one architecture, which lives at github.com/metatool-ai/metamcp.
- Tools, prompts and resources from every configured server merged into a single list, with calls routed to the right backend
- Configuration driven from MetaMCP App rather than a local file, with GUI updates to the MCP configs
- Multi-workspace support — switch to a different set of MCP configs in one click
- Namespace isolation across the joined servers, so tool names do not collide
- Three transports from one binary: stdio by default, SSE with `--transport sse --port 12006`, or Streamable HTTP with `--transport streamable-http`, optionally `--stateless`
- `--require-api-auth` to demand the API key in the SSE or Streamable HTTP URL path
- `--use-docker-host`, which rewrites localhost and 127.0.0.1 URLs to `host.docker.internal` so a containerised proxy can still reach services on the host
- Control over child-process stderr — `ignore` by default, or `inherit`, `pipe` or `overlapped` — which matters when a backend is failing silently
- Compatibility with any MCP client
Node with `npx`, and a MetaMCP API key in `METAMCP_API_KEY` — the proxy has nothing to serve without it, since the configuration comes from MetaMCP App. Run it as `npx -y @metamcp/mcp-server-metamcp@latest` (0.6.5), or pass `--metamcp-api-key` on the command line; `METAMCP_API_BASE_URL` points at a different API host. The README notes that Smithery installation is sometimes unstable because MetaMCP runs other MCP servers on top of itself, and recommends manual installation when it misbehaves. Read the deprecation notice first: this local proxy is superseded by MetaMCP 2.0's all-in-one architecture.
One command plus a key — npx -y @metamcp/mcp-server-metamcp@latest, then supply credentials