Nacos MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_namespacesB | Retrieves the list of namespaces in the current Nacos cluster. |
| list_servicesA | This interface retrieves the list of services under a specified namespace. The response format depends on the |
| get_serviceA | This interface retrieves detailed information of a specified service, including metadata and clusters, not including instance list. |
| list_service_instancesC | This interface retrieves the list of instances for a specified service. |
| list_service_subscribersC | This interface retrieves the list of subscribers for a specified service. |
| list_configsC | This interface retrieves the list of configurations under a specified namespace. |
| get_configC | This interface retrieves the details of the specified configuration. |
| list_config_historyC | This interface retrieves the complete publish history of a configuration. |
| get_config_historyB | This interface retrieves a specific historical change record of a configuration. |
| list_config_listenersB | This interface retrieves the list of listeners subscribed to a specific configuration. |
| list_listened_configsC | This interface lists the configurations subscribed to by a specific client IP address. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in the Nacos domain (configurations, services, namespaces, listeners/subscribers). No tools appear to overlap or cause confusion, as each name precisely indicates its function, such as get_config vs. list_configs or get_service vs. list_services.
All tool names follow a consistent verb_noun pattern with snake_case throughout, using clear verbs like 'get', 'list', and specific nouns like 'config', 'service', 'namespace'. There are no deviations or mixed conventions, making the naming highly predictable and readable.
With 11 tools, this server is well-scoped for managing configurations and services in Nacos, covering key operations like retrieval, listing, and history tracking. Each tool earns its place without feeling excessive or insufficient for the domain's needs.
The tool set provides strong coverage for read operations on configurations, services, namespaces, and related metadata, but lacks explicit create, update, or delete tools for these resources. This minor gap means agents can query effectively but may need workarounds for full lifecycle management.