MetaMCP

MetaMCP is a self-hosted MCP gateway for developers and teams connecting AI clients to multiple tool servers. It lets you manage the tool collections those clients receive through shared endpoints.

• Tool collections: Group servers into namespaces, enable or disable individual servers and tools, and switch which collection an endpoint exposes.
• Client connections: Share MCP tools, resources and prompts through SSE or Streamable HTTP with clients such as Cursor, or expose OpenAPI endpoints for Open WebUI.
• Tool customization: Override names, descriptions and annotations within each namespace, and apply middleware to requests and responses, including a built-in filter that removes inactive tools from the model's context.
• Authentication: Protect endpoints with API keys or OAuth, and connect organizational sign-in through OpenID Connect providers such as Keycloak, Auth0 and Azure AD. Separate controls govern registration through the UI form and through SSO.
• Server inspection: Check connected servers and combined endpoints with an inspector that saves server configurations for reuse.

MetaMCP runs in Docker on your own machine or server and is open source under the MIT license. Its endpoints use network transports. Clients that accept only local STDIO connections need a proxy such as mcp-proxy; mcp-remote doesn't work with MetaMCP's API key authentication.