MetaMCP MCP Server

Example Use Cases

• 1

  Aggregate tool lists from multiple MCP servers into a single unified catalog so clients can discover tools across installations.

• 2

  Forward tool/prompt/resource calls to the correct underlying MCP server while preserving namespace isolation and workspace selection.

• 3

  Run MCPs in varying transports (stdio, SSE, streamable HTTP) or inside Docker with automatic localhost-to-host.docker.internal URL transformation.

Description

MetaMCP MCP Server acts as a local proxy to join and unify multiple MCP servers into a single endpoint for MCP clients. It fetches tool/prompt/resource configurations from the MetaMCP App, initializes clients for each underlying MCP, and routes calls to the appropriate target server while providing namespace isolation and multi-workspace support. The server supports multiple transports (stdio, SSE, streamable HTTP), Docker host URL transformation, and configurable stderr handling for child processes. It is designed to let MCP clients (e.g., Claude Desktop) see an aggregated tool list and call tools across different MCP installations.