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
This tool helps developers consolidate multiple MCP (Meta-Communication Protocol) servers into a single, unified gateway. You input various individual MCP server configurations, and it outputs a single, aggregated MCP endpoint that can be easily connected to any MCP client. This is ideal for developers who manage multiple AI tools or services and need to streamline their access and management.
About agent
1mcp-app/agent
A unified Model Context Protocol server implementation that aggregates multiple MCP servers into one.
This tool simplifies managing multiple AI assistants and the various Model Context Protocol (MCP) servers they might use. It takes inputs from different MCP servers and provides a single, unified access point for your AI assistants like Cursor, VSCode, or Claude Code. Developers and power users who work with multiple AI coding assistants will find this useful for streamlining their workflow.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work