Cisco CX Cloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_DIR | No | Set log directory | ./logs |
| LOG_LEVEL | No | Set log level (ERROR, WARN, INFO, DEBUG) | INFO |
| LOG_TO_FILE | No | Enable file logging | false |
| CISCO_CLIENT_ID | Yes | Your Cisco API Client ID obtained from the Cisco API Console | |
| CISCO_CLIENT_SECRET | Yes | Your Cisco API Client Secret obtained from the Cisco API Console |
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 |
|---|---|
| get_customer_accountsA | Get all accessible CX Cloud customer accounts and their IDs. Use this first to get customer IDs for other operations. |
| get_hardware_inventoryB | Get hardware inventory for a specific customer. Returns details about all hardware assets. |
| get_network_elementsC | Get network elements inventory for a specific customer. Returns network devices and their details. |
| get_contractsC | Get all contracts for a specific customer. Returns contract details including coverage periods. |
| get_covered_assetsB | Get all assets covered by contracts for a specific customer. |
| get_uncovered_assetsB | Get all assets NOT covered by contracts for a specific customer. Useful for identifying coverage gaps. |
| get_field_noticesB | Get field notices for a specific customer. Returns important product notifications and bulletins. |
| get_hardware_eolC | Get hardware end-of-life information for a specific customer. Shows which hardware is reaching end-of-life. |
| get_software_eolC | Get software end-of-life information for a specific customer. Shows which software versions are reaching end-of-life. |
| get_security_advisoriesC | Get security advisories for a specific customer. Returns security alerts and recommendations. |
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 10 tools
Every tool has a clearly distinct purpose targeting specific data types like contracts, assets, accounts, field notices, hardware/software EOL, inventory, network elements, security advisories, and uncovered assets. The descriptions explicitly differentiate each tool's function, eliminating any ambiguity or overlap.
All tool names follow a consistent 'get_' prefix with descriptive nouns (e.g., get_contracts, get_covered_assets), using snake_case uniformly throughout. This predictable pattern makes the tool set easy to navigate and understand.
With 10 tools, the server is well-scoped for its purpose of retrieving various customer-specific data from Cisco CX Cloud. Each tool serves a distinct and necessary function, covering key areas like contracts, assets, inventory, and advisories without being overly sparse or bloated.
The tool set provides comprehensive read-only coverage for retrieving customer data, including contracts, assets, inventory, and advisories, with no obvious gaps for its apparent domain. However, it lacks write or update operations (e.g., create or modify contracts), which might limit full lifecycle management but is typical for a data retrieval-focused server.