Multi MCP
Related Servers
Alternatives to Multi MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA flexible MCP proxy server that connects to and routes between multiple backend MCP servers over STDIO or SSE, enabling dynamic management and namespacing of tools.111MIT
- AlicenseNot gradedqualityAmaintenanceAggregates multiple backend MCP servers (Stdio, SSE, and Streamable HTTP) and exposes their combined tools and resources through a single unified SSE or Streamable HTTP endpoint, or as a standalone Stdio server. It routes requests to the correct backend, supports optional API key/bearer token authentication, and offers an optional web admin UI for managing servers, toggling tools, and monitoring installations.27 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables clients to connect to, manage, and aggregate multiple backend MCP servers and access their combined tools and resources through unified SSE or Streamable HTTP endpoints, or as a single Stdio server. It provides request routing, optional authentication, granular tool controls, and an optional web admin interface.27 npmMIT
- AlicenseNot gradedqualityAmaintenanceAggregates and routes requests across multiple backend MCP servers, exposing their combined tools and resources through unified SSE, Streamable HTTP, or Stdio endpoints. Supports optional Web UI management, granular tool control, and endpoint authentication.27 npmMIT
- AlicenseNot gradedqualityAmaintenanceAggregates multiple backend MCP servers (Stdio, SSE, and Streamable HTTP) into a single unified endpoint, exposing their combined tools and resources via SSE, Streamable HTTP, or Stdio. It also offers an optional web admin UI for managing server connections, tool enablement, and live configuration reloads.27 npmMIT
- FlicenseNot gradedqualityAmaintenanceAggregates multiple backend MCP servers (Stdio, SSE, and Streamable HTTP) and exposes their combined tools and resources through a single unified SSE or Streamable HTTP endpoint, or as a standalone Stdio server. It routes tool calls and resource requests to the right backend and offers optional web-based admin, authentication, and per-tool control.-
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: two are for mathematical operations (addition and multiplication) and one is for weather retrieval. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool.
The naming is mixed: 'calculator__add' and 'calculator__multiply' follow a consistent 'domain__verb_noun' pattern, but 'weather__get_weather' uses a different structure with a redundant 'weather' term. This inconsistency reduces predictability, though the names remain readable.
With only three tools, the server feels thin and under-scoped for a 'Multi MCP' name that suggests broader functionality. The tools cover two unrelated domains (calculator and weather), lacking depth in either area, which may limit agent effectiveness.
The tool surface is severely incomplete. For the calculator domain, basic operations like subtraction and division are missing, and for weather, there are no tools for forecasts or historical data. This creates significant gaps that will likely cause agent failures in handling related tasks.