AI ERP with agents inside the systems you run
AI phone and voice agents for real calls
LLM.coPrivate, self-hosted LLM deployments
Legal AI infrastructure for firms
AI RFP discovery and response drafting
Automatic.coBusiness process automation
CyberAttack.aiThreat detection and defense
Secure AI virtual data roomsmetamcp
MetaMCP is a Docker-based MCP proxy that aggregates multiple MCP servers into a unified endpoint, enabling dynamic composition and management of tools through namespaces, middleware, and flexible authentication. It serves as both a gateway and an enhanced inspector for MCP servers.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | metatool-ai/metamcp |
| Owner | metatool-ai |
| Primary language | TypeScript |
| License | MIT — OSI-approved |
| Stars | 2.5k |
| Forks | 375 |
| Open issues | 89 |
| Latest release | v2.4.22 (2025-12-19) |
| Last updated | 2026-06-22 |
| Source | https://github.com/metatool-ai/metamcp |
What metamcp is
MetaMCP implements MCP protocol aggregation and orchestration via TypeScript/Node.js, supporting STDIO and SSE/Streamable HTTP transports. It provides namespace-based server grouping, tool filtering middleware, OIDC authentication, rate limiting, and OpenAPI endpoint exposure for non-MCP clients.
Get the metamcp source
Clone the repository and explore it locally.
git clone https://github.com/metatool-ai/metamcp.gitcd metamcp# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Plan MCP server inventory and grouping strategy before deploying; namespace structure affects tool discovery and client switching complexity.
- Secrets management: use environment variable references (`${VAR_NAME}`) rather than raw values in config; ensure MetaMCP container has access to secrets at runtime.
- SSE and Streamable HTTP transports require proper reverse-proxy configuration (Nginx SSE example provided); test connection resilience and reconnection handling.
- Cold-start latency for STDIO servers can be significant; custom Dockerfile optimization and server pre-warming strategies may be needed for production.
- Tool override and annotation system requires coordination; establish naming conventions and metadata standards to avoid conflicts across namespaces.
When to avoid it — and what to weigh
- Simple Single-Server Deployments — If you only run one or two non-aggregated MCP servers, MetaMCP adds unnecessary orchestration overhead; connect servers directly to clients instead.
- Strict Latency-Critical Workloads — Proxy layer introduces additional network hops and processing; measure end-to-end impact for latency-sensitive applications before committing.
- Minimal Operational Capacity — Requires Docker/container infrastructure, environment variable management, and ongoing namespace/endpoint configuration; teams without DevOps support should start simpler.
- Closed-Source/Proprietary Deployment Only — MIT license requires attribution and allows commercial use, but self-hosting and operational complexity may conflict with zero-touch managed-service expectations.
License & commercial use
MIT License (MIT). Permits commercial use, modification, and distribution; requires attribution. No restriction on proprietary deployments.
MIT license clearly permits commercial and proprietary use, including self-hosted enterprise deployments. No royalties or licensing restrictions apply. Standard attribution required in derivative works and distributions.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Strong |
| Assessment confidence | High |
Project does not claim formal security audit or certification. OIDC and API-key auth are standard patterns; implementation details unknown. Environment variable handling uses reference syntax (`${VAR}`) to avoid embedding secrets in config. Middleware extensibility and tool override features increase attack surface if custom logic is untrusted. Rate limiting available but configuration/enforcement details are unclear. Self-hosted nature places responsibility on deployer for network isolation, secret storage, and access control.
Alternatives to consider
Anthropic MCP Inspector (Official)
Lightweight, official reference implementation for testing single MCP servers; no aggregation, authentication, or hosting features; suitable if you don't need gateway functionality.
LangChain Tool Hub / Custom LLM Middleware
Alternative tool orchestration at application layer rather than protocol layer; tighter integration with LLM frameworks but less transparent to MCP clients; no centralized endpoint.
Kong / API Gateway (Generic)
Mature reverse-proxy with authentication, rate limiting, and plugin ecosystem; can proxy MCP-over-HTTP, but no MCP-native aggregation or namespace logic; steeper learning curve.
Build on metamcp with DEV.co software developers
Deploy MetaMCP in Docker or explore the documentation to aggregate and manage multiple MCP servers through a single gateway endpoint.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
metamcp FAQ
Can I use MetaMCP with Claude Desktop?
How do I handle secrets for MCP servers running under MetaMCP?
Is MetaMCP production-ready?
Can I extend MetaMCP with custom middleware?
Software developers & web developers for hire
metamcp rarely ships on its own. As a software development company, DEV.co handles the surrounding work — data modeling, service integration, deployment, and the mcp servers glue code that production actually requires.
Ready to Orchestrate Your MCP Servers?
Deploy MetaMCP in Docker or explore the documentation to aggregate and manage multiple MCP servers through a single gateway endpoint.