MetaMCP MCP Server is a proxy server that combines multiple MCP servers into one. It retrieves tool, prompt, and resource configurations from MetaMCP App and routes requests to the appropriate underlying server, allowing you to manage multiple MCP servers through a single interface.
The simplest way to install and run MetaMCP MCP Server is using the API key directly:
npx -y @metamcp/mcp-server-metamcp@latest --metamcp-api-key <your-api-key>
If you want to install it for Claude Desktop manually, you can add this configuration:
{
"mcpServers": {
"MetaMCP": {
"command": "npx",
"args": ["-y", "@metamcp/mcp-server-metamcp@latest"],
"env": {
"METAMCP_API_KEY": "<your api key>"
}
}
}
}
The default mode uses stdio for communication:
mcp-server-metamcp --metamcp-api-key <your-api-key>
To run as a Server-Sent Events (SSE) server:
mcp-server-metamcp --metamcp-api-key <your-api-key> --transport sse --port 12006
This starts an Express.js web server that listens for SSE connections on the /sse
endpoint and accepts messages on the /messages
endpoint.
For HTTP-based communication:
mcp-server-metamcp --metamcp-api-key <your-api-key> --transport streamable-http --port 12006
You can add the --stateless
flag for stateless operation if needed.
When running in Docker and connecting to services on the host machine:
mcp-server-metamcp --metamcp-api-key <your-api-key> --transport sse --port 12006 --use-docker-host
This transforms any localhost or 127.0.0.1 URLs to host.docker.internal
, allowing proper connection to host services.
For stdio transport, you can control how stderr is handled:
# See stderr output from child processes
mcp-server-metamcp --metamcp-api-key <your-api-key> --stderr inherit
# Capture stderr (default is ignore)
mcp-server-metamcp --metamcp-api-key <your-api-key> --stderr pipe
# Using environment variable
METAMCP_STDERR=inherit mcp-server-metamcp --metamcp-api-key <your-api-key>
Available options:
ignore
(default): Ignore stderr from child processesinherit
: Pass through stderr to the parentpipe
: Capture stderr in a pipeoverlapped
: Use overlapped I/O (Windows-specific)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, sse, or streamable-http) (default: "stdio")
--port <port> Port to use for SSE or Streamable HTTP transport, defaults to 12006 (default: "12006")
--require-api-auth Require API key in SSE or Streamable HTTP URL path
--stateless Use stateless mode for Streamable HTTP transport
--use-docker-host Transform localhost URLs to use host.docker.internal (can also be set via USE_DOCKER_HOST env var)
--stderr <type> Stderr handling for STDIO transport (overlapped, pipe, ignore, inherit) (default: "ignore")
-h, --help display help for command
Configure the server using these environment variables:
METAMCP_API_KEY
: Your MetaMCP API keyMETAMCP_API_BASE_URL
: Base URL for the MetaMCP APIUSE_DOCKER_HOST
: Set to "true" for Docker compatibilityMETAMCP_STDERR
: Controls stderr handling (overlapped, pipe, ignore, inherit)To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "MetaMCP" '{"command":"npx","args":["-y","@metamcp/mcp-server-metamcp@latest"],"env":{"METAMCP_API_KEY":"<your api key>"}}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"MetaMCP": {
"command": "npx",
"args": [
"-y",
"@metamcp/mcp-server-metamcp@latest"
],
"env": {
"METAMCP_API_KEY": "<your api key>"
}
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"MetaMCP": {
"command": "npx",
"args": [
"-y",
"@metamcp/mcp-server-metamcp@latest"
],
"env": {
"METAMCP_API_KEY": "<your api key>"
}
}
}
}
3. Restart Claude Desktop for the changes to take effect