Combine MCP Server
Multiple MCP server aggregation into one interface for client compatibility.
Data last scanned yesterday · Reviewed today
Overview
This aggregator functions as a bridge, allowing users to bypass limitations in clients like Cursor that restrict the number of concurrent MCP server connections. It operates by acting as both an MCP client to backend servers and an MCP server to your primary interface, consolidating multiple inputs into a single stdio stream. The tool includes features such as automatic tool name sanitization, replacing dashes with underscores to ensure compatibility, and prefixing backend methods to prevent naming collisions. Configuration is handled via JSON files or environment variables, with support for adjustable debug logging levels.
Our verdict
With a security score of 16/100, this tool carries a high risk level. It is a community-maintained project with no detected license, and it has not been editorially reviewed. Given that the code is noted as being primarily AI-generated and the last commit occurred over 240 days ago, users should exercise significant caution. This aggregator is best suited for experimental environments rather than sensitive workflows.
- Zero direct dependencies reduce supply-chain surface area.
- Bypasses MCP connection limits in clients like Cursor.
- Provides documented installation via shell script or Docker.
- High risk level due to lack of security review.
- Unclear legal terms due to missing license.
- Bus factor risk with only one contributor.
- Stale repository with no updates for 246 days.
Compatibility
No compatibility data yet.
Badge
Maintain this server? Add the live badge to your README.