Nacos-MCP-Router MCP Server

What does “Nacos-MCP-Router” MCP Server do?

Nacos-MCP-Router is an MCP (Model Context Protocol) Server that acts as a powerful intermediary to connect AI assistants and clients with other MCP servers and their functionalities. It enables centralized search, installation, and proxying of various MCP servers, streamlining the development workflow for cloud-native applications and microservices. By operating in either “router” or “proxy” mode, Nacos-MCP-Router can recommend, distribute, install, and proxy the functions of other MCP servers, or convert different MCP server protocols (such as SSE and stdio) into a unified streamable HTTP protocol. This makes it easier for developers and AI agents to interact with external data sources, APIs, and tools—enabling tasks such as database queries, file management, and service orchestration with enhanced flexibility and convenience.

List of Prompts

• No specific prompt templates are listed in the repository or documentation.

List of Resources

• No specific resources are described or exposed by the Nacos-MCP-Router in the available documentation.

List of Tools

• search_mcp_server
  Search MCP servers by task and keywords, returning a list of suitable MCP servers and instructions for completing the task.
• add_mcp_server
  Add a new MCP server (supports stdio and sse servers), install if necessary, and establish a connection. Returns available tools and usage instructions for the added server.
• use_tool
  Proxy requests to a specific tool on a target MCP server, allowing LLMs to use tools exposed by other MCP servers via the router.

Use Cases of this MCP Server

• Centralized MCP Server Discovery
  Easily search for MCP servers relevant to specific tasks or keywords, streamlining the process of finding and integrating the right capabilities for your workflow.
• One-Click MCP Server Installation
  Quickly add and install MCP servers (including protocol handling) through a single interface, reducing setup time and complexity for developers.
• Unified Tool Proxying
  Use tools from different MCP servers via a single API, allowing LLMs and clients to interact with a variety of external services without manual integration.
• Protocol Bridging and Compatibility
  Convert SSE and stdio protocol MCP servers into the streamable HTTP protocol with simple configuration, increasing compatibility with modern clients and AI agents.
• Service Management and Orchestration
  Manage the lifecycle of multiple MCP servers, distribute workloads, and orchestrate service interactions through a centralized router interface.

How to set it up

Windsurf

1. Prerequisites: Ensure you have Node.js installed and access to the Windsurf MCP settings.
2. Locate MCP Configuration: Open the Windsurf MCP settings panel.
3. Add Nacos-MCP-Router: Insert the following JSON snippet into the mcpServers object:

   {
     "nacos-mcp-router": {
       "command": "uvx",
       "args": ["nacos-mcp-router@latest"],
       "env": {
         "NACOS_ADDR": "<NACOS-ADDR, optional, default is 127.0.0.1:8848>",
         "NACOS_USERNAME": "<NACOS-USERNAME, optional, default is nacos>",
         "NACOS_PASSWORD": "<NACOS-PASSWORD, required>"
       }
     }
   }
   

4. Save and Restart: Save changes and restart Windsurf if necessary.
5. Verify Setup: Test by searching for MCP servers or adding a new one via the interface.

Claude

1. Prerequisites: Ensure Claude supports MCP integration. Install Node.js if needed.
2. Locate Configuration: Open Claude’s MCP or plugin settings.
3. Add Nacos-MCP-Router: Use this JSON snippet:

   {
     "mcpServers": {
       "nacos-mcp-router": {
         "command": "uvx",
         "args": ["nacos-mcp-router@latest"],
         "env": {
           "NACOS_ADDR": "<NACOS-ADDR, optional, default is 127.0.0.1:8848>",
           "NACOS_USERNAME": "<NACOS-USERNAME, optional, default is nacos>",
           "NACOS_PASSWORD": "<NACOS-PASSWORD, required>"
         }
       }
     }
   }
   

4. Save and Restart: Save and restart Claude as needed.
5. Verify: Confirm by searching/adding servers through Claude’s interface.

Cursor

1. Prerequisites: Node.js must be installed; access the Cursor MCP server settings.
2. Configuration: Open settings and add:

   {
     "mcpServers": {
       "nacos-mcp-router": {
         "command": "uvx",
         "args": ["nacos-mcp-router@latest"],
         "env": {
           "NACOS_ADDR": "<NACOS-ADDR, optional, default is 127.0.0.1:8848>",
           "NACOS_USERNAME": "<NACOS-USERNAME, optional, default is nacos>",
           "NACOS_PASSWORD": "<NACOS-PASSWORD, required>"
         }
       }
     }
   }
   

3. Save Settings: Save and restart Cursor.
4. Verify: Run a search or add a new MCP server to verify functionality.

Cline

1. Prerequisites: Node.js installed, Cline with MCP support.
2. Edit Configuration: Open Cline’s MCP server configuration.
3. Insert MCP Server: Use the following JSON:

   {
     "mcpServers": {
       "nacos-mcp-router": {
         "command": "uvx",
         "args": ["nacos-mcp-router@latest"],
         "env": {
           "NACOS_ADDR": "<NACOS-ADDR, optional, default is 127.0.0.1:8848>",
           "NACOS_USERNAME": "<NACOS-USERNAME, optional, default is nacos>",
           "NACOS_PASSWORD": "<NACOS-PASSWORD, required>"
         }
       }
     }
   }
   

4. Save and Restart: Apply changes and restart Cline.
5. Verification: Confirm by using MCP functions from Cline.

Securing API Keys

To secure API keys, use environment variables in your configuration. Example:

{
  "mcpServers": {
    "nacos-mcp-router": {
      "command": "uvx",
      "args": ["nacos-mcp-router@latest"],
      "env": {
        "NACOS_ADDR": "127.0.0.1:8848",
        "NACOS_USERNAME": "nacos",
        "NACOS_PASSWORD": "${NACOS_PASSWORD}"
      }
    }
  }
}

Set the NACOS_PASSWORD environment variable in your system before starting the server.

How to use this MCP inside flows

Using MCP in FlowHunt

To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:

{
  "nacos-mcp-router": {
    "transport": "streamable_http",
    "url": "https://yourmcpserver.example/pathtothemcp/url"
  }
}

Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “nacos-mcp-router” to whatever the actual name of your MCP server is and replace the URL with your own MCP server URL.

Overview

Roots support: Not mentioned in documentation.

Between these two tables, the Nacos-MCP-Router MCP server provides strong core functionality for MCP server orchestration and tool proxying, but lacks documentation on prompt templates and resource exposure. Sampling and roots features are not clearly described. I would rate this MCP implementation a 6/10 based on completeness and documentation.

MCP Score