nacos-config-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_HOST | No | HTTP listen address | 127.0.0.1 |
| MCP_HTTP_PATH | No | HTTP endpoint path | /mcp |
| MCP_HTTP_PORT | No | HTTP listen port | 3000 |
| MCP_TRANSPORT | No | MCP transport: stdio or http | stdio |
| NACOS_VERSION | No | Force major version: auto, 1, 2, 3 | auto |
| MCP_HTTP_TOKEN | No | Bearer token required for HTTP requests; no validation if not set | |
| NACOS_BASE_URL | Yes | Nacos server address, e.g. http://127.0.0.1:8848 (required) | |
| NACOS_PASSWORD | No | Nacos password | |
| NACOS_USERNAME | No | Nacos username | |
| NACOS_AUTH_TYPE | No | Authentication type: none, nacos, or bearer. Defaults to nacos if credentials are provided. | |
| NACOS_LOG_LEVEL | No | Log level: debug, info, warn, error, silent | warn |
| NACOS_NAMESPACE | No | Default namespace when tool does not specify one | |
| NACOS_TIMEOUT_MS | No | HTTP timeout in milliseconds | 10000 |
| NACOS_CONSOLE_URL | No | Nacos 3.x Console address, defaults to NACOS_BASE_URL | |
| NACOS_ACCESS_TOKEN | No | Preset access token | |
| NACOS_CONTEXT_PATH | No | Server context path | /nacos |
| NACOS_TLS_INSECURE | No | Skip TLS certificate verification (true/false) | false |
| NACOS_SERVER_IDENTITY_KEY | No | Server identity header name | |
| NACOS_CONSOLE_CONTEXT_PATH | No | Console context path | |
| NACOS_SERVER_IDENTITY_VALUE | No | Server identity header value |
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": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nacos_server_infoA | Report how this MCP server is connected to Nacos: detected server version, major version, the API endpoints actually in use, context path and authentication mode. Use this first when troubleshooting connectivity or version compatibility. |
| nacos_list_namespacesA | List the namespaces (tenants) available on the Nacos server, optionally filtered to a single namespace ID. Works across Nacos 1.x, 2.x and 3.x. |
| nacos_search_configsA | Search or page through configuration entries in a namespace. Supports exact and fuzzy matching on dataId, plus filters for group, application name, tags and content type. Returns paged summaries (without content); call nacos_get_config to read a value. Compatible with Nacos 1.x, 2.x and 3.x. |
| nacos_get_configA | Read the full content and metadata of a single configuration entry identified by dataId + group + namespace. Compatible with Nacos 1.x, 2.x and 3.x; on Nacos 1.x the raw text body is returned. |
| nacos_list_config_historyA | List the revision history of a configuration entry. Each item carries the revision id (nid) that can be passed to nacos_get_config_history_detail to read that revision. Compatible with Nacos 1.x, 2.x and 3.x. |
| nacos_get_config_history_detailA | Read the content and metadata of one historical revision of a configuration entry. Use the revision id (nid) returned by nacos_list_config_history. Compatible with Nacos 1.x, 2.x and 3.x. |
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 6 tools
Each tool targets a distinct action: server info, namespace listing, config search, config content retrieval, and history list/detail. The search tool explicitly returns summaries without content and points to get_config, so there is no functional overlap.
All tool names share a consistent nacos_ prefix and mostly follow the verb_noun pattern (list_namespaces, search_configs, get_config, list_config_history). The only deviation is nacos_server_info, which lacks a verb, but this is a minor inconsistency.
Six tools is a well-scoped set for reading Nacos configurations and their history. Each tool has a clear purpose and none feel redundant.
The read-side coverage is solid: namespaces, search, content retrieval, and full history review are all present. However, there are no create, update, delete, publish, or remove operations, leaving the configuration lifecycle incomplete.