metamcp and agent
These are competitors offering similar MCP aggregation functionality—both serve as proxy layers that consolidate multiple MCP servers into a single unified interface, so implementations would typically choose one based on deployment preference (Docker vs. native) rather than use them together.
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.
About agent
1mcp-app/agent
A unified Model Context Protocol server implementation that aggregates multiple MCP servers into one.
Implements stdio transport isolation with subprocess management for child MCP servers, featuring OAuth 2.1 authentication, hot-reload configuration, and health check monitoring. Designed as a proxy layer that aggregates tools across multiple AI assistants (Claude Desktop, Cursor, VSCode) through a single HTTP endpoint, eliminating per-client configuration overhead.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work