mcphub and metamcp
Both are MCP aggregation/gateway solutions that compete for the same use case—centralizing multiple MCP servers behind a single endpoint—though metamcp emphasizes Docker-based deployment while mcphub focuses on dynamic routing strategies.
About mcphub
samanhappy/mcphub
A unified hub for centrally managing and dynamically orchestrating multiple MCP servers/APIs into separate endpoints with flexible routing strategies
Exposes MCP servers via HTTP/SSE endpoints with vector-powered semantic routing for intelligent tool discovery, while supporting OAuth 2.0 authentication and hot-swappable configuration through JSON or PostgreSQL backends. Built on Node.js/Express and implements the Model Context Protocol SDK to aggregate heterogeneous server capabilities into a unified interface accessible by AI clients like Claude Desktop and Cursor.
About metamcp
metatool-ai/metamcp
MCP Aggregator, Orchestrator, Middleware, Gateway in one docker
Supports dynamic MCP server aggregation with middleware injection and tool-level filtering, enabling selective exposure of capabilities across namespaces. Implements a proxy architecture using stdio transport with environment variable management, allowing configuration-driven composition of multiple MCP servers into unified endpoints with granular access control via API-key or OAuth authentication.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work