spring-nacos-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NACOS_PASSWORD | No | Global fallback password for Nacos authentication. | |
| NACOS_USERNAME | No | Global fallback username for Nacos authentication. | |
| SPRING_NACOS_MCP_MASK | No | Enable masking of secret values (e.g., '1' or custom list like 'password,apikey'). |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nacos_list_envsA | List the environments (Spring profiles) auto-discovered from this repository's application/bootstrap files, with each environment's Nacos server address, namespace and groups. Call this first if you are unsure which environments exist. |
| nacos_get_configA | Read the raw content of one Nacos config by its exact dataId (e.g. 'order-service.properties'). Use nacos_search_config first when you don't know which dataId contains a key. |
| nacos_get_app_configA | Read the effective configuration of one application: its own config (.) plus the shared/extension configs declared in the project (spring.cloud.nacos.config.shared-configs). Prefer this over nacos_get_config when asked about an app's settings. |
| nacos_list_configsA | List config dataIds in an environment's namespace (no content by default). Optionally fuzzy-filter by dataId substring. |
| nacos_search_configA | Full-text search across all config contents in one environment. Returns matching dataIds with the matching lines. Use this to find which config file defines a property key. |
| nacos_diff_configA | Compare one config (dataId) between two environments and return a structured key-level diff: keys only in A, only in B, and changed values. The best tool for questions like 'is X consistent between dev and test?'. |
| nacos_list_servicesC | List service names registered in the Nacos naming/discovery registry of one environment. |
| nacos_list_instancesA | List the online instances (IP, port, health) of one service. Use for 'is service X up / why is it offline' questions. |
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 8 tools
Each tool targets a distinct resource and action: diff config, get config (raw or app-level), list configs, list environments, list instances, list services, search config. No two tools have overlapping purposes, making selection unambiguous.
All tool names follow the consistent pattern 'nacos_verb_noun' in snake_case (e.g., nacos_diff_config, nacos_list_services). Verbs and nouns are clear and uniform, with no mixing of conventions.
With 8 tools covering both configuration and service discovery, the count is well-scoped for the domain. Each tool serves a distinct purpose without bloat or insufficiency.
The toolset provides comprehensive read and comparison capabilities for Nacos configs and services, including diff, search, and app-level config resolution. It lacks write operations (create/update/delete), but given the diagnostic focus, this is a minor gap.