jewei-mcp-nacos
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NACOS_HOST | No | Nacos server address (Nacos 服务地址) | localhost |
| NACOS_API_PORT | No | API port used for login (API 端口,用于登录) | 8848 |
| NACOS_PASSWORD | No | Password for authentication (密码) | |
| NACOS_USERNAME | No | Username for authentication (用户名) | |
| NACOS_NAMESPACE | No | Default namespace ID (默认命名空间 ID) | public |
| NACOS_READ_ONLY | No | Read-only mode, disables publishing functions (只读模式,禁用发布功能) | false |
| NACOS_CONSOLE_PORT | No | Console port used for configuration operations (Console 端口,用于配置操作) | 8080 |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nacos_get_configB | 获取 Nacos 配置内容。 |
| nacos_publish_configA | 发布 Nacos 配置。 |
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 2 tools
The two tools have clearly distinct purposes: one retrieves configuration content from Nacos, while the other publishes/updates configuration. There is no overlap in functionality, and the descriptions clearly differentiate between read and write operations.
Both tools follow a consistent naming pattern: 'nacos_' prefix followed by verb_noun (get_config, publish_config). This pattern is uniform across all tools, making them easily identifiable and predictable.
With only two tools, this server feels severely under-scoped for managing a configuration system like Nacos. Essential operations like listing configurations, deleting configurations, or monitoring changes are missing, making the toolset incomplete for typical configuration management workflows.
The toolset covers basic get and publish operations but lacks critical CRUD/lifecycle coverage for a configuration management system. There are no tools for listing available configurations, deleting configurations, or handling configuration versioning, which are standard needs in this domain.