mcp -metamcp

This MCP server acts as a proxy that aggregates multiple MCP servers into a single interface. It fetches tool, prompt, and resource configurations from the MetaMCP App and routes requests to the appropriate underlying MCP servers. The example setup shows MetaMCP being run via npx to pull the latest version and expose the joined MCP experience. You can run the server in different transports (stdio, SSE, or streamable-http) and configure how it exposes its endpoints, including optional Docker-host URL translation when running inside containers. To begin, install the MetaMCP MCP Server and provide your API key for MetaMCP; then use the command line options to select the transport and port you want. Available transports (stdio, SSE, streamable-http) determine how clients communicate with the proxy and how tool lists are fetched and invoked.

The server supports a variety of runtime options, including:

• --metamcp-api-key for authenticating with MetaMCP
• --transport to choose between stdio, sse, or streamable-http
• --port to set the listening port for SSE or streamable-http transports
• --use-docker-host to translate localhost URLs when running in Docker
• --stderr to control how child MCP process errors are surfaced
• Environment variables like METAMCP_API_KEY and METAMCP_API_BASE_URL for configuration

In practice, you’ll typically run the server with a single MCP profile (e.g., MetaMCP) and let it fetch tool configurations from MetaMCP App, then call tools as if they were provided locally. If you have additional MCP servers to join, you can extend the mcpServers mapping by adding more entries (name, command, args, and any env vars) so the proxy can route calls to them seamlessly.

Prerequisites:

• Node.js and npm installed on your machine
• Access to the internet to fetch MCP packages from npm
• An API key for MetaMCP (if using MetaMCP integration)

Option A: Installing via Smithery (automatic/setup-assisted)

• Install MetaMCP MCP Server for Claude Desktop automatically via Smithery:

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

Option B: Manual installation (recommended for flexibility)

• Set your API key in the environment (example shown) and install/run the latest MCP server package via npx:

export METAMCP_API_KEY=<your api key>
npx -y @metamcp/mcp-server-metamcp@latest

Configured mcpServers example (as used by manual installation):

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

To persist this configuration, save it to a file named mcpConfig.json (or as required by your deployment) and reference it when launching the server.

Important: This MCP server is marked as deprecated within MetaMCP's 2.0 all-in-one architecture. Consider migrating to the recommended setup at metamcp/metamcp for long-term support. Keep your METAMCP_API_KEY secure and avoid publishing it in public repos. If you’re running inside Docker, remember to use --use-docker-host to translate localhost URLs to host.docker.internal so the proxy can reach services on the host. The server supports multiple transports; choose stdio for simple embedded usage, SSE for streaming tool updates to clients, or streamable-http for HTTP-based interactions. If you run into connectivity issues, verify API key validity, base URL configuration (METAMCP_API_BASE_URL), and that the target MCP servers are reachable from the proxy.