MetaMCP
2.2K stars. Solves 'too many MCP servers' — consolidates all tool connections into one managed proxy.
MCP aggregator that combines multiple MCP servers into a unified endpoint with namespace management, tool selection, and OAuth. Single Docker container.
- Combine all your MCP servers into one unified endpoint
- Manage namespaces so tools from different servers do not conflict
- Add or remove MCP servers without reconfiguring Claude
2.2K stars. Solves 'too many MCP servers' — consolidates all tool connections into one managed proxy.
Power users with 5+ MCP servers who want a single unified endpoint instead of managing each separately.
https://github.com/metatool-ai/metamcp
By metatool-ai
How to Get It
git clone https://github.com/metatool-ai/metamcp.git && cd metamcp && cp example.env .env && docker compose up -d
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Once it’s connected, paste this into Claude:
Help me combine all my MCP servers into one unified endpoint
Trust Signals Reviewed
Data & Access
Community Pulse Active
Discussed on Hacker News, Reddit
- MetaMCP is rewritten to 2.0 and here is what it may help (500+ github stars MIT — Reddit · 63 pts
- I built MetaMCP: a middleware MCP to manage all your MCPs (open source with GUI, — Reddit · 17 pts
- Meta MCP: Chaining Tools via Prompt-Driven Arguments — Hacker News · 16 pts
3 mentions across 2 sources
Reviewer notes
Reviewed review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 2,202 GitHub stars; 20 contributors; last commit 101d ago; license MIT.
2026-05-10: Useful when you're running 5+ MCP servers and the per-connection config overhead is becoming a real maintenance problem—MetaMCP collapses them into a single endpoint with namespaced tooling and OAuth in one Docker container. The tradeoff is real: you're introducing a proxy layer that becomes a single point of failure, and any downstream MCP instability now surfaces through a shared chokepoint. OAuth config per backend still requires upfront work, so don't expect zero setup. Pairs well with stable, well-maintained MCP servers; less suited to experimental or unreliable ones.
Things to check
- Aggregation adds a network hop and a potential single point of failure; OAuth needs upfront per-backend configuration. Note: the author has publicly acknowledged maintenance delays — recent AI-assisted changes ship on an 'ai-dev' branch ('please test before you build the image'), and a community-maintained fork exists.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 2,202 GitHub stars; 20 contributors; last commit 101d ago; license MIT.