Huawei DCS MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUAWEI_REGION | Yes | Huawei Cloud region. Can be overridden per tool call by the region argument. | |
| HUAWEI_ACCESS_KEY | Yes | Huawei Cloud access key (AK). | |
| HUAWEI_PROJECT_ID | Yes | Huawei Cloud project ID. Can be overridden per tool call by the project_id argument. | |
| HUAWEI_SECRET_KEY | Yes | Huawei Cloud secret key (SK). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Query Huawei Cloud DCS through an explicit read-only tool catalog.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
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 28 tools
Most tools target clearly distinct resources or actions: instance listing vs. detail, config parameters vs. config history, and diagnosis vs. hotkey/bigkey analysis are separated. A few pairs are close enough to require care, such as ShowNodesInformation vs. BatchShowNodesInformation, ListMonitoredObjects vs. ListMonitoredObjectsOfInstance, and ListConfigurations vs. ListConfigHistories, but the descriptions distinguish them.
The names follow a consistent PascalCase verb-noun convention throughout, using List/Show/BatchShow prefixes with descriptive resource nouns. The List vs. Show distinction is applied consistently across collections and individual resources.
At 28 tools, the surface is heavy for a server whose tools are all read-only query operations. Many tools form narrow pairs around diagnostics, hotkeys, bigkeys, nodes, and config history, which could likely be consolidated.
The server covers a broad read-only observability surface, but it has no create, update, delete, restart, backup, scaling, or whitelist modification operations. For a DCS instance management domain, this is a significant lifecycle gap that would block common agent workflows.