MetaMCP
A self-hosted gateway that merges several MCP servers into one endpoint with auth and tool selection
Install
git clone https://github.com/metatool-ai/metamcp.git
cd metamcp
cp example.env .env
docker compose up -dThis is third-party code. Review the repository files before installing.
What it does
MetaMCP runs in Docker and is itself an MCP server, so any client can connect to it. In the web UI servers are grouped into namespaces where individual servers and tools can be toggled, and tools renamed or re-described. A namespace is published as an endpoint over SSE, Streamable HTTP or OpenAPI with API key or OAuth auth. It includes request middleware, a built-in inspector, rate limiting and OpenID Connect login.
Who it is for. For teams and agent builders who need a single access point to a set of MCP servers.
Good fit when
- You want to give a team one endpoint instead of a dozen server configs
- You need to hide extra tools to keep model context lean
- You need OpenAPI access to MCP servers, for example from Open WebUI
Not a fit when
- You only need one or two servers locally
- You cannot run Docker and PostgreSQL
Example request
Through the MetaMCP endpoint find recent HackerNews threads and save the links to a noteLimitations
Requires Docker and the PostgreSQL from docker-compose. The author warns of maintenance delays; the main ai-dev branch includes AI-made changes and should be tested before building. Stdio-only clients need a local mcp-proxy. Access is allowed only from the APP_URL address.
How to disable. Remove the MetaMCP endpoint from client configs and stop the containers with docker compose down.
MCP
- Transport
- sse, http
- Authentication
- API key
| Environment variables | |
|---|---|
| APP_URL required | The URL MetaMCP is accessed from |
Security check
- Stores secrets and launches the connected MCP servers
- Exposes tool access over the network
README in short
The README opens with the author's note on maintenance status and a community fork. It then explains concepts: server, namespace, endpoint, middleware, inspector and tool overrides. It covers Docker Compose and Dev Containers setup, Cursor and Claude Desktop configs, auth, OIDC, rate limits and Nginx settings. MIT licensed.
FAQ
How do I connect Claude Desktop?
Via uvx mcp-proxy with the endpoint URL and the key in API_ACCESS_TOKEN. mcp-remote does not work with MetaMCP keys.
Where should server secrets live?
In the container's environment, referenced as ${VAR_NAME} in server settings.
Related
An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
AWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring
A GitHub Action that runs Claude Code in pull requests and issues: answers mentions, reviews and makes changes