mcp-proxy and agent
These are **competitors** — both aggregate multiple MCP servers into a single unified interface, with the primary difference being that mcp-app/agent targets direct MCP server integration while mcp-proxy/mcp-proxy adds an HTTP abstraction layer, but they solve the same core problem of MCP server consolidation and you would choose one based on your deployment architecture rather than use both together.
About mcp-proxy
tbxark/mcp-proxy
An MCP proxy server that aggregates and serves multiple MCP resource servers through a single HTTP server.
This tool helps developers streamline access to various Modular Chat Protocol (MCP) servers. It takes connections to multiple MCP servers as input and provides a single, unified HTTP endpoint for all of them. Software architects, DevOps engineers, and backend developers who manage and deploy chat protocol servers would use this.
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