MCP Servers · metatool-ai

metamcp

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.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/metatool-ai/metamcp

2.5k

GitHub stars

375

Forks

TypeScript

Primary language

MIT

License (OSI-approved)

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.

Quickstart

Get the metamcp source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/metatool-ai/metamcp.git2cd metamcp3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Multi-tool Agent Infrastructure

Host and dynamically switch between groups of MCP servers as unified endpoints for AI agents, eliminating need to reconfigure client connections when toolsets change.

Enterprise Tool Access Control

Aggregate internal and third-party MCP servers with centralized authentication (OIDC), role-based tool filtering, and audit logging through a single gateway.

Development and Integration Testing

Use as enhanced MCP inspector with persistent server configs and endpoint testing; validate composed tool behavior before pushing to production agents.

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

Security considerations

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.

Software development agency

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.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

fastmcp xmcp MCPJungle

Related on DEV.co

Explore the category and the services that help you build with it.

MCP Servers AI Application Development API Development DevOps & Infrastructure Talk to DEV.co

metamcp FAQ

Can I use MetaMCP with Claude Desktop?

Yes, via stdio configuration in mcp.json. MetaMCP itself runs as an MCP server, so it can be configured as a transport for Claude Desktop; see 'Connecting Claude Desktop' in README.

How do I handle secrets for MCP servers running under MetaMCP?

Use environment variable references in config (e.g., `${OPENAI_API_KEY}`) or rely on auto-matching if env var names match exactly. Secrets are resolved from the MetaMCP container's environment at runtime, not stored in config.

Is MetaMCP production-ready?

Core functionality is actively maintained and used (2.5k+ stars, active community). However, some features are marked 'coming soon' (e.g., Elasticsearch-style tool selection, advanced middleware). Test thoroughly in your environment before production deployment.

Can I extend MetaMCP with custom middleware?

Framework supports middleware concept at namespace level (filtering, logging, validation examples mentioned). Detailed middleware extension API and examples are not clearly documented; requires code review and community examples.

Software developers & web developers for hire

DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If metamcp is part of your mcp servers roadmap, our team can implement, customize, migrate, and maintain it.

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.

Talk to DEV.co Schedule a Consultation