MetaMCP

MetaMCP is a MCP proxy that lets you dynamically aggregate MCP servers into a unified MCP server, and apply middlewares. MetaMCP itself is a MCP server so it can be easily plugged into ANY MCP clients. It functions as an MCP Aggregator, Orchestrator, Middleware, and Gateway all in one docker image, enabling scalable, configurable hosting of multiple MCP servers behind a single endpoint with flexible authentication, tooling, and annotations. This README introduces core concepts such as MCP Server configurations, Namespaces, Endpoints, Middleware, Inspector, and Tool Overrides & Annotations, and provides quick-start guidance for running MetaMCP with Docker, building a development environment, and integrating with clients like Claude Desktop via proxies. It also covers MCP protocol compatibility, authentication options (including API keys, OAuth, and OIDC), and integration guidance for developers looking to remix MCP tool flows and middleware pipelines.

MetaMCP serves as infrastructure to host dynamically composed MCP servers behind a unified endpoint. It enables grouping MCP servers into namespaces, hosting them as a meta-MCP, applying middlewares, and optionally overriding tool metadata per namespace. This is useful for organizations wanting to aggregate tools, prompts, and resources from multiple MCP servers, then expose a single endpoint with configurable authentication (API keys or OAuth) and transport options (SSE or Streamable HTTP). Example usage includes configuring a MetaMCP endpoint that aggregates multiple underlying MCP servers, then calling tools across those servers via the aggregated interface. See code examples for mcp.json configuration and client integrations (Claude Desktop and others) to illustrate how to connect and use the proxy. For example, a simple mcp.json to point to a MetaMCP endpoint looks like:

{
  "mcpServers": {
    "MetaMCP": {
      "url": "http://localhost:12008/metamcp/<YOUR_ENDPOINT_NAME>/sse"
    }
  }
}

To connect Claude Desktop or other stdio clients, you can proxy the remote MCP endpoint with mcp-proxy as shown in the docs:

Using Streamable HTTP

{
  "mcpServers": {
    "MetaMCP": {
      "command": "uvx",
      "args": [\
        "mcp-proxy",\
        "--transport",\
        "streamablehttp",\
        "http://localhost:12008/metamcp/<YOUR_ENDPOINT_NAME>/mcp"\
      ],
      "env": {
        "API_ACCESS_TOKEN": "<YOUR_API_KEY_HERE>"
      }
    }
  }
}

Using SSE

{
  "mcpServers": {
    "ehn": {
      "command": "uvx",
      "args": [\
        "mcp-proxy",\
        "http://localhost:12008/metamcp/<YOUR_ENDPOINT_NAME>/sse"\
      ],
      "env": {
        "API_ACCESS_TOKEN": "<YOUR_API_KEY_HERE>"
      }
    }
  }
}

Local development guidance also includes steps to install dependencies and run the project locally via pnpm, and Docker-based quick-start instructions for running the full stack in production.