metamcp
MetaMCP is an MCP proxy that aggregates several MCP servers into one unified server, and is itself an MCP server so any MCP client can plug into it. The README describes it as an aggregator, orchestrator, middleware and gateway in one Docker deployment. Its concepts are: an MCP Server entry (how to start a STDIO server, or where a remote one is), a Namespace that groups servers, an Endpoint that publishes a namespace over SSE or Streamable HTTP with auth, plus middleware, an Inspector and tool overrides and annotations.
Use cases in the README include grouping servers into namespaces and switching which one an endpoint exposes, picking only the tools you need when remixing servers, and using the built-in inspector with saved configs to test endpoints. It also exposes OpenAPI endpoints for clients such as Open WebUI. For STDIO servers it supports raw values, and other ways to handle environment variables and secrets. Authentication covers API keys and OIDC providers, and there are registration controls for organisations. Protocol support is listed as tools, resources and prompts, with OAuth-enabled servers tested against the 03-26 spec.
Quick start is `git clone`, copy `example.env` to `.env`, and `docker compose up -d`, with Dev Containers and `pnpm dev` options for development. The licence is MIT. A note at the top of the README apologises for maintenance delays and says the author will at least keep merging PRs, so check recent activity before depending on it; last push was 2026-06-22. This review is based on the README and repository data; we have not run it ourselves.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-06-22
- Commits, last 90 days
- 0
- Releases, last 90 days
- 0
- Latest release
- v2.4.22 (2025-12-19)
- Open issues
- 127
- Recent issues with at least one comment
- 4/24
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #149 [Middleware Design Discussion] Override tool title, description, annotations25 comments · 2025-09-01
- #162 MCP server processes never terminate, accumulating until OOM13 comments · 2025-09-12
- #131 [Docker-per-MCP] For people having issues with memory/crash, those related to "sub-MCP crashes main app"; let's try out new architecture var12 comments · 2025-08-14
- #103 Is there any plan for creating rbac for mcp and namespaces11 comments · 2025-07-18
- #147 [Feature] Possibility to pull from custom and private registry10 comments · 2025-08-31
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You want one endpoint for many MCP servers, grouped into namespaces and served over SSE, Streamable HTTP or OpenAPI.
- You need API key or OIDC authentication and registration controls for a team.
- You want to remix tools with overrides and annotations and test them in a built-in inspector.
- You want a single binary: it needs Docker and a Postgres database.
- You need active maintenance: the README itself notes maintenance delays, and our data shows the last push on 2026-06-22.
- You are counting on pluggable middleware or MCP tool search: the README marks them as coming soon.
How it differs
Both aggregate servers behind one endpoint with a dashboard. MetaMCP uses namespaces and OIDC and requires Postgres. MCPHub starts with one Docker command and a JSON file, and has smart routing and OAuth 2.0, with PostgreSQL optional for production.
Compatibility
Quick start
Use cases
Alternatives
Featured in these lists
Comments
No comments yet. Be the first!