home / mcp / metamcp mcp server
MCP Server MetaMCP manages all your other MCPs in one MCP.
Configuration
View docs{
"mcpServers": {
"metatool-ai-mcp-server-metamcp": {
"command": "npx",
"args": [
"-y",
"@metamcp/mcp-server-metamcp@latest"
],
"env": {
"METAMCP_STDERR": "ignore",
"METAMCP_API_KEY": "<your api key>",
"USE_DOCKER_HOST": "true",
"METAMCP_API_BASE_URL": "https://api.metamcp.example.com"
}
}
}
}MetaMCP MCP Server acts as a proxy that joins multiple MCP servers into a single interface. It fetches tool/prompt/resource configurations from MetaMCP App and routes requests to the appropriate underlying MCP server, enabling centralized management and seamless tool access across merged MCPs.
You use this MCP Server to connect several MCP servers under one umbrella. Start by configuring your MetaMCP API key, then run the server in one of several transports (stdio, SSE, or streamable HTTP). The server will fetch configurations from MetaMCP App and expose a unified toolset to your MCP clients.
Typical flows include starting the server in standard stdio mode for local development, or using SSE/streamable-http transports to enable more scalable or remote communication. You can also run the server inside Docker and adapt localhost references when talking to host services.
Prerequisites: Node.js and npm should be installed on your machine. You will also need access to a MetaMCP API key.
Option 1: Install via Smithery (auto-setup provided by Smithery for Claude Desktop)
npx -y @smithery/cli install @metatool-ai/mcp-server-metamcp --client claudeOption 2: Manual installation (recommended if Smithery is unstable for your setup)
export METAMCP_API_KEY=<env>
npx -y @metamcp/mcp-server-metamcp@latestExample configuration (JSON) for the MCP server to run with the MetaMCP server included
{
"mcpServers": {
"MetaMCP": {
"command": "npx",
"args": ["-y", "@metamcp/mcp-server-metamcp@latest"],
"env": {
"METAMCP_API_KEY": "<your api key>"
}
}
}
}