hybrid server

The server is able to function both locally and remotely, depending on the configuration or use case.

Integrations

The README includes a Mermaid sequence diagram to illustrate the architecture of the MetaMCP MCP Server, showing how it interacts with MCP clients, the MetaMCP App, and installed MCP servers.

MetaMCP MCP Server

https://metamcp.com: The One MCP to manage all your MCPs

MetaMCP MCP Server is a proxy server that joins multiple MCP⁠ servers into one. It fetches tool/prompt/resource configurations from MetaMCP App⁠ and routes tool/prompt/resource requests to the correct underlying server.

MetaMCP App repo: https://github.com/metatool-ai/metatool-app

Installation

Installing via Smithery

Sometimes Smithery works (confirmed in Windsurf locally) but sometimes it is unstable because MetaMCP is special that it runs other MCPs on top of it. Please consider using manual installation if it doesn't work instead.

To install MetaMCP MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @metatool-ai/mcp-server-metamcp --client claude

Manual Installation

export METAMCP_API_KEY=<env>
npx -y @metamcp/mcp-server-metamcp@latest

{
  "mcpServers": {
    "MetaMCP": {
      "command": "npx",
      "args": ["-y", "@metamcp/mcp-server-metamcp@latest"],
      "env": {
        "METAMCP_API_KEY": "<your api key>"
      }
    }
  }
}

Usage

Using as a stdio server (default)

mcp-server-metamcp --metamcp-api-key <your-api-key>

Using as an SSE server

mcp-server-metamcp --metamcp-api-key <your-api-key> --transport sse --port 12006

With the SSE transport option, the server will start an Express.js web server that listens for SSE connections on the /sse endpoint and accepts messages on the /messages endpoint.

Command Line Options

Options:
  --metamcp-api-key <key>       API key for MetaMCP (can also be set via METAMCP_API_KEY env var)
  --metamcp-api-base-url <url>  Base URL for MetaMCP API (can also be set via METAMCP_API_BASE_URL env var)
  --report                      Fetch all MCPs, initialize clients, and report tools to MetaMCP API
  --transport <type>            Transport type to use (stdio or sse) (default: "stdio")
  --port <port>                 Port to use for SSE transport (default: "12006")
  -h, --help                    display help for command

Environment Variables

METAMCP_API_KEY: API key for MetaMCP
METAMCP_API_BASE_URL: Base URL for MetaMCP API

Development

# Install dependencies
npm install

# Build the application
npm run build

# Watch for changes
npm run watch

Highlights

Compatible with ANY MCP Client
Multi-Workspaces layer enables you to switch to another set of MCP configs within one-click.
GUI dynamic updates of MCP configs.
Namespace isolation for joined MCPs.

Architecture Overview

Credits

Inspirations and some code (refactored in this project) from https://github.com/adamwattis/mcp-proxy-server/

You must be authenticated.

A

security – no known vulnerabilities

A

license - permissive license

A

quality - confirmed to work

A proxy server that unifies multiple MCP servers, enabling seamless tool, prompt, and resource management via the MetaMCP App.

Related Resources

Reddit Discussion about this server