search_mcp_serverLABSCO SUMMARY
One connection that goes and finds the others.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command plus credentials — uvx nacos-mcp-router@latest, then supply credentials
USE CASES
01
Finding a server for a job you have not done before
Describe the task in words and get matching servers ranked by similarity.
02
Adding one without editing client config
Register the server through the router and call it from the same connection.
03
Keeping a client's tool list short
Tools are reached through the router instead of every server being connected at once.
04
Getting a stdio-only server onto HTTP
Proxy mode converts SSE and stdio servers into Streamable HTTP.
3 tools
Listed in project docs. Your client may show a different list.
add_mcp_serveruse_toolBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- uvx on PATH
- NACOS_PASSWORD in your environment
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx nacos-mcp-router@latestMCP Clients
Cline, Cursor
JSON
{
"mcpServers": {
"nacos-mcp-router": {
"command": "uvx",
"args": [
"nacos-mcp-router@latest"
],
"env": {
"NACOS_ADDR": "127.0.0.1:8848",
"NACOS_USERNAME": "nacos",
"NACOS_PASSWORD": "<YOUR_NACOS_PASSWORD>"
}
}
}
}NACOS_ADDR and NACOS_USERNAME are set to the README defaults (127.0.0.1:8848 and nacos) — change them if your Nacos runs elsewhere, keeping the port. <YOUR_NACOS_PASSWORD> is your Nacos password. It is the one required value.
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"nacos-mcp-router": {
"command": "npx",
"args": [
"nacos-mcp-router@latest"
],
"env": {
"NACOS_ADDR": "127.0.0.1:8848",
"NACOS_USERNAME": "nacos",
"NACOS_PASSWORD": "<YOUR_NACOS_PASSWORD>"
}
}
}
}NACOS_ADDR and NACOS_USERNAME are set to the README defaults (127.0.0.1:8848 and nacos) — change them if your Nacos runs elsewhere, keeping the port. <YOUR_NACOS_PASSWORD> is your Nacos password. It is the one required value.
