Instead of wiring every server into the client up front, you describe the task and it locates, installs and proxies the one that fits — which is also how a stdio-only server ends up reachable over Streamable HTTP.
A router that sits in front of other MCP servers. In router mode, the default, it searches for servers by task description — through Nacos service discovery with vector similarity, and through a Compass registry endpoint — then installs and proxies them. In proxy mode it converts SSE and stdio servers into Streamable HTTP.
- MCP servers searched by task description and keywords, with vector similarity and relevance scoring
- Results aggregated from Nacos service discovery and a Compass registry endpoint
- A server added, then its tools called through this one connection
- A minimum similarity score and a result limit you set
- SSE and stdio servers converted to Streamable HTTP in proxy mode
A Nacos instance for the local provider. Outer search goes to a Compass registry endpoint, which defaults to https://registry.mcphub.io and can be repointed; the minimum similarity score and the number of results are tunable, and MODE=proxy selects proxy mode.
One command plus a key — uvx nacos-mcp-router@latest, then supply credentials