metamcp
by metatool-ai·★ 2,328·Score 55
MetaMCP is a unified MCP proxy that aggregates multiple MCP servers into one with middleware support.
Overview
MetaMCP acts as both an MCP server and proxy, allowing developers to dynamically combine multiple MCP servers into unified endpoints. It provides features like namespace management, middleware support, authentication through API keys or OAuth, and tool customization. The project is actively maintained with Docker support and comprehensive documentation. Its architecture allows for traffic management, rate limiting, and future extensions for tool logging and error tracing.
Try asking AI
After installing, here are 5 things you can ask your AI assistant:
When to choose this
Choose MetaMCP when you need to manage multiple MCP servers in a unified infrastructure with authentication, tool overrides, and middleware capabilities.
When NOT to choose this
Avoid MetaMCP for simple use cases with just one MCP server or if you require direct tool access without aggregation layer overhead.
Comparable tools
Installation
Installation
- **Docker Compose (Recommended)**:
git clone https://github.com/metatool-ai/metamcp.git
cd metamcp
cp example.env .env
docker compose up -d- **Local Development**:
pnpm install
pnpm devClaude Desktop Configuration
Add to claude_desktop_config.json:
{
"mcpServers": {
"metamcp": {
"command": "docker",
"args": ["run", "--rm", "metatool-ai/metamcp"]
}
}
}FAQ
- What MCP versions does MetaMCP support?
- MetaMCP supports MCP with Tools, Resources, and Prompts. It has tested OAuth-enabled MCP servers for the 03-26 version.
- How does authentication work with MetaMCP?
- MetaMCP supports both API-Key authentication (in header or query param) and standard OAuth according to MCP Spec 2025-06-18.
On Hacker News
Recent discussion from the developer community.
- Story by jczhang141 · 2025-07-16
Compare metamcp with
Last updated · Auto-generated from public README + GitHub signals.