AI Agents
Unla
Unla MCP Gateway: turn existing APIs and MCP servers into MCP endpoints with zero code changes.
★ 2.2k starsMIT
View guide →MCP aggregator, orchestrator, middleware and gateway in one Docker — compose many servers into one endpoint
metamcp is an open-source ai agents project by metatool-ai (metatool-ai/metamcp on GitHub). It has 2,698 GitHub stars and 436 forks, is released under the MIT license, and was last updated on GitHub on 22 June 2026.
List the MCP servers you want behind one endpoint and which tools each audience should see.
Clone the repo and copy example.env to .env.
Start it with docker compose up -d, then add your MCP server configurations in the UI.
Create a namespace from your servers, assign it to an endpoint, and connect your client to that endpoint URL.
Combines many MCP servers into one unified MCP server at runtime — no client-side config sprawl.
Group servers into namespaces, enable/disable servers or individual tools, and switch a namespace on an endpoint in one click.
Publish SSE, Streamable HTTP or OpenAPI endpoints with API-key auth (header or query) or standard MCP OAuth.
Namespace-level middleware intercepts and transforms requests/responses; a built-in example filters inactive tools to save context.
Rename tools, edit titles/descriptions and attach custom annotations per namespace without losing upstream metadata.
Built-in inspector with saved server configs, plus multi-tenancy with private/public scopes and per-user API keys.
Clone MetaMCP and enter the directory.
git clone https://github.com/metatool-ai/metamcp.git
cd metamcpCopy the example env file and start the stack with Docker Compose.
cp example.env .env
docker compose up -dPoint an MCP client at your MetaMCP endpoint (example for Cursor in the README).
{
"mcpServers": {
"MetaMCP": { "url": "http://localhost:12008/metamcp/<endpoint>/sse" }
}
}metatool-ai maintains it; docs are at docs.metamcp.com, and the README also links a community-maintained fork.
Yes, it is MIT-licensed and self-hosted in one Docker Compose stack.
No. It issues its own API keys for endpoint access; the MCP servers you aggregate may have their own credentials, handled via env references.
Both are self-hosted MCP gateways. MetaMCP emphasizes dynamic namespaces, middleware and tool overrides; MCPHub emphasizes smart routing, per-user credentials and operations monitoring.
Clone, cp example.env .env, docker compose up -d, add a server in the UI, create a namespace and endpoint, and connect your client.
Unla MCP Gateway: turn existing APIs and MCP servers into MCP endpoints with zero code changes.
Self-hosted MCP gateway and control plane — connect, control and operate all your MCP servers from one place
The fast, Pythonic way to build MCP servers and clients.
An open-source auth gateway connecting 1,500+ SaaS providers to AI agents via SDK, CLI, MCP and HTTP.
Archestra: the enterprise AI platform — chat UI, LLM gateway, and MCP gateway with guardrails
Shrimp Task Manager: an MCP server that turns natural language into structured, dependent dev tasks.
The most-starred other AI Agents projects in the LibreAI catalogue — the realistic shortlist if metamcp is not the right fit.
A personal AI that really does things — on any OS, with your data staying yours.
An agentic skills framework & software development methodology that works.
Agent harness optimization system with skills, memory and security for Claude Code, Codex and more
The agent that grows with you — a Python framework for adaptive AI agents.
DeepSeek's plugin-based agent harness where everything is a plugin.
Free and open — grab the source, star the repo, and start creating.