MetaMCP
A self-hosted MCP gateway that combines tool servers behind shared endpoints. Runs in Docker under the MIT license and connects to Cursor and Open WebUI.
MetaMCP is a self-hosted gateway for developers and teams who want to give AI clients access to several MCP servers through one endpoint. It runs on your own machine or server with Docker and is open source under the MIT license. You choose which tools clients see.
Servers can be grouped into namespaces, each with its own selection of enabled tools. An endpoint can switch between these groups, so different agents or users can receive different tool collections. You can also edit tool names, descriptions and annotations without changing the upstream server. Its middleware can modify requests and responses, with a built-in filter that excludes inactive tools from the model's context.
MetaMCP supports MCP tools, resources and prompts. It exposes SSE and Streamable HTTP endpoints for MCP clients such as Cursor, plus OpenAPI endpoints for Open WebUI. Clients that only accept local STDIO connections can connect through mcp-proxy. A built-in inspector keeps saved server configurations for checking servers and aggregated endpoints.
For shared deployments, MetaMCP supports API keys, OAuth and private or public access scopes. Organizations can use existing identity providers through OpenID Connect, including Keycloak, Auth0 and Azure AD. Administrators can control account registration separately for password and SSO signups, and apply rate limits to endpoints or individual clients. Server deployments require at least 2 to 4 GB of memory.
The maintainer reports delayed maintenance and recommends testing development-branch changes before building a deployment image.
