MCP Router
Related Servers
Alternatives to MCP Router
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAggregates and routes multiple MCP servers with intelligent tool recommendation and batch parallel execution, enabling unified access and efficient tool usage.2144MIT
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP server that enables intelligent tool management and semantic search for APIs using sentence-transformers. It supports both REST and MCP interfaces across dual transport modes, allowing users to upload, manage, and query API tools with natural language.1MIT
- AlicenseNot gradedqualityDmaintenanceA smart proxy that aggregates multiple downstream MCP servers and enables natural language search for tools, allowing clients like Claude Desktop to discover and use tools through semantic queries.11ISC
- FlicenseNot gradedqualityNot gradedmaintenanceProvides a unified MCP interface that proxies requests to multiple backend servers including memory/knowledge graph and vector database services. Enables seamless access to distributed MCP tools through a single endpoint with automatic routing, health monitoring, and retry logic.-
- AlicenseNot gradedqualityAmaintenanceAI-first MCP server discovery tool that enables agents to search, inspect, and install MCP servers from multiple registries.12AGPL 3.0
- FlicenseAqualityDmaintenanceUniversal MCP proxy server that discovers, searches, and executes tools across all configured MCP servers from a single entry point.7-
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: add_mcp_server registers servers, exec_mcp_tool executes tools on servers, and search_mcp_server searches for servers. The descriptions reinforce these distinct roles, making misselection unlikely.
All tool names follow a consistent verb_noun pattern with snake_case: add_mcp_server, exec_mcp_tool, and search_mcp_server. This predictable naming scheme enhances readability and usability for agents.
With only 3 tools, the server feels thin for a router's scope, which typically involves more operations like listing, updating, or removing servers. While the core functions are present, the count is borderline for comprehensive routing capabilities.
The tool set covers basic registration, execution, and search, but lacks operations for updating or deleting servers, which are common in lifecycle management. This creates notable gaps that agents might need to work around for full server management.