Nacos

You use the Nacos MCP Server to read, search, and list information from a Nacos cluster through MCP. It helps you access namespaces, services, and configurations for integration with large language models and automated workflows without performing write operations on the Nacos data.

How to use

You will connect your MCP client to the Nacos MCP Server and issue read, search, and list operations to retrieve namespaces, services, configurations, and related metadata. Use the server to discover what exists in your Nacos cluster and feed that information into your automation or LLM-driven workflows. When you need to inspect or enumerate items, request lists (namespaces, services, configs) or detailed views for a given service or configuration, and you will receive structured results that you can use to inform decisions or generate prompts for language models.

How to install

{ 
  "mcpServers": {
    "nacos_mcp": {
      "command": "uvx",
      "args": [
        "nacos-mcp-server",
        "--host",
        "your_nacos_host",
        "--port",
        "your_nacos_main_port, such as 8848",
        "--access_token",
        "your_nacos_access_token, get from `login` api: /nacos/v3/auth/user/login with `username` and `password`"
      ]
    }
  }
}
```"}],

Configuration and notes

The server can be run via a local development flow using a JavaScript/TypeScript toolchain or directly through Python. The provided examples show how to start the MCP server using uvx with the Nacos MCP Server package, or by invoking the Python module version. Use the following runtime options that match your environment.

Development and runtime notes

• The server currently supports read, search, and list operations for namespaces, services, configurations, and related data. Write operations are not yet supported in this version but are planned for future updates. - Ensure you provide your Nacos host, port, and an access token when starting the server to enable authorized access to Nacos Admin APIs. - If you are using a local development setup, you can run the MCP server via uvx or via Python by running the corresponding module. - For integration with Claude Desktop, place the MCP server configuration in your claude_desktop_config.json using the same host/port and access token details.

Troubleshooting

If you encounter connection issues, verify that your Nacos instance is reachable at the specified host and port, and that the access token is valid. Check that the MCP server process has the necessary network permissions to reach the Nacos Admin API. Review the host, port, and token values in your MCP server configuration and ensure they match what you use in your Nacos cluster. If memory usage spikes when requesting service lists with instances, consider setting withInstances to false to retrieve metadata first and fetch instances selectively.

Available tools

list_namespaces

Retrieves the list of namespaces in the current Nacos cluster.

list_services

Retrieves the list of services under a specified namespace. Can include or exclude instance data via withInstances parameter.

get_service

Retrieves detailed information of a specified service, including metadata and clusters, but not the instance list.

list_service_instances

Retrieves the list of instances for a specified service.

list_service_subscribers

Retrieves the list of subscribers for a specified service.

list_configs

Retrieves the list of configurations under a specified namespace.

get_config

Retrieves the details of a specified configuration.

list_config_history

Retrieves the complete publish history of a configuration.

get_config_history

Retrieves a specific historical change record of a configuration.

list_config_listeners

Retrieves the list of listeners subscribed to a specific configuration.

list_listened_configs

Retrieves the configurations subscribed to by a specific client IP address.