nacos

This MCP server provides read-only tools to interact with a Nacos cluster. It exposes actions to list namespaces, list services within a namespace, fetch detailed service information, retrieve service instances, and explore Nacos configurations and their history. You can query namespaces via list_namespaces, view services in a namespace with list_services, inspect a specific service with get_service, and fetch service instances using list_service_instances. For configurations, you can list, read, and view history through list_configs, get_config, list_config_history, get_config_history, list_config_listeners, and list_listened_configs. The server is designed to work with Nacos 3.x+ and focuses on read, search, and read-only listing capabilities; write operations are not yet supported but may be added in future releases. To get started, run the MCP server with the uvx command corresponding to the mcp-server-nacos package, then invoke the available tools via the MCP interface to explore namespaces, services, configurations, and their metadata. The tools are intended to help your LLMs understand the Nacos cluster structure and configuration landscape for safer and more informed orchestration.

Prerequisites:

• A Nacos cluster (Nacos 3.0.0+ recommended).
• Python 3.x (recommended 3.13+).
• Access credentials if your Nacos cluster is secured.

Installation steps:

1. Ensure Python 3.x is installed on your machine.
2. Install the MCP server package via uv (recommended):
   • Run: uvx install mcp-server-nacos
   • This registers the MCP server with the uv environment.
3. Run the MCP server:
   • Run: uvx run nacos
   • If you need to override defaults, set environment variables (see env notes below).
4. Verify the server is reachable via your MCP interface and start issuing read-only tool commands (list_namespaces, list_services, get_service, list_service_instances, list_configs, get_config, list_config_history, get_config_history, list_config_listeners, list_listened_configs).

Notes:

• The server is read-only in this initial version. Write operations will be added in future releases.
• If your Nacos cluster requires authentication, configure NACOS_API_BASE_URL and any pertinent credentials as environment variables or through your uv configuration.

Environment and configuration tips:

• NACOS_API_BASE_URL can be set to the base URL of your Nacos Admin API (for example, http://nacos-host:8848/nacos/v1).
• The toolset supports pagination and filtering when listing namespaces, services, and configurations. Use pageNo/pageSize and optional filters like namespaceId, groupName, serviceName, dataId, etc.
• Because listing services can be memory-intensive when withInstances is true, consider using withInstances=false for broad queries and then selectively requesting instance lists for specific services.
• This server emphasizes read-only access; no write operations are supported in this version. Future updates may introduce write capabilities such as creating/updating namespaces, services, or configurations.
• Ensure network connectivity between your MCP runtime (where uvx runs) and your Nacos cluster, including any required TLS/authorization settings.