#1212th of 14 in Gateways
MetaMCP
Aggregates MCP servers into namespaced endpoints with auth and middleware
- Stars
- 2.7k
- License
- MIT
- Last commit
- Jun 2026
- Last release
- Dec 2025
Overview
MetaMCP groups MCP servers into namespaces and publishes each as one MCP endpoint over SSE, Streamable HTTP or OpenAPI, with API-key or OAuth auth, per-tool toggles, name overrides and middleware. It runs with Docker Compose beside PostgreSQL on port 12008, adds OIDC SSO, multi-tenancy and rate limits, and includes an inspector with saved configs. The author reports maintenance delays.
Who it is for: teams curating MCP tool sets for many clients
Strengths
- Namespaces group servers, toggle tools and override names and annotations
- Endpoints over SSE, Streamable HTTP and OpenAPI with API key or MCP OAuth
- OIDC SSO, multi-tenancy and registration controls for organizations
- Built-in inspector with saved server configs
Weaknesses
- Author notes maintenance delays; a community fork exists
- Endpoints are remote-only; stdio clients like Claude Desktop need mcp-proxy
- Rate-limit counters are in-memory per instance, not cluster-wide
- MCP servers needing more than uvx or npx require a custom Dockerfile
What it needs
- no GPU
- Docker + Compose
- Needs PostgreSQL
- port 12008
Also in Gateways
See all 14| Rank | Project | Score |
|---|---|---|
| 1 | OmniRouteOpenAI-compatible gateway that routes requests across hundreds of AI providers | 86 out of 100 |
| 2 | LiteLLMOpenAI-format gateway and Python SDK for calling 100+ LLM providers | 84 out of 100 |
| 3 | freellmapiOpenAI-compatible router that fails over across free LLM provider tiers | 76 out of 100 |
| #4 | ContextForge MCP GatewayRegistry and proxy federating MCP, A2A, REST and gRPC behind one endpoint | 68 out of 100 |
| #5 | HigressEnvoy-based API gateway with LLM proxy plugins and MCP server hosting | 61 out of 100 |