nvidia-cumulus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CUMULUS_HOST | No | Cumulus VX or switch hostname/IP | 127.0.0.1 |
| CUMULUS_PORT | No | NVUE API HTTPS port | 8765 |
| CUMULUS_TIMEOUT | No | HTTP timeout in seconds | 10 |
| CUMULUS_PASSWORD | Yes | NVUE basic-auth password | |
| CUMULUS_USERNAME | No | NVUE basic-auth username | cumulus |
| CUMULUS_CA_BUNDLE | No | Optional CA bundle path for TLS validation | |
| CUMULUS_VERIFY_TLS | No | Enable TLS certificate validation | false |
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 | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nvue_getA | Read any safe relative NVUE path with HTTP GET. |
| get_platformB | Get platform hardware and software information. |
| get_systemC | Get system information. |
| get_system_resourcesA | Get system CPU and memory information. |
| list_interfacesA | Get all interfaces. |
| get_interfaceC | Get one interface. |
| get_interface_countersA | Get link counters for one interface. |
| list_bridgesA | Get all bridge domains. |
| get_bridgeB | Get one bridge domain. |
| get_mac_tableB | Get the bridge domain MAC table. |
| list_vrfsA | Get all VRFs. |
| get_vrfC | Get one VRF. |
| get_routesA | Get the routing table for one VRF. |
| get_ip_neighborsC | Get IP neighbors for one interface. |
| get_lldp_neighborsC | Get LLDP neighbors for one interface. |
| get_bgp_globalA | Get global BGP information. |
| get_bgp_vrfC | Get BGP information for one VRF. |
| get_bgp_neighborsB | Get BGP neighbors for one VRF. |
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 18 tools
Most tools target distinct resources (e.g., BGP global vs VRF vs neighbors), but `nvue_get` introduces potential overlap as a generic path-reader that could replicate specific get_ tools. BGP-related tools are well-differentiated by scope and neighbors.
Tools predominantly use `get_<object>` for singular and `list_<object>` for plurals, but `nvue_get` breaks the pattern with reversed order. The verb mix between 'get' and 'list' is consistent with CRUD conventions, yet the outlier reduces overall consistency.
18 tools cover a broad but focused domain of Cumulus network state retrieval. The count is slightly on the higher side but still manageable and each tool serves a clear purpose, justifying its inclusion.
The tool set is read-only (get/list/nvue_get), which is complete for monitoring but lacks any create, update, or delete operations. Missing common read operations like per-prefix route details, but core resources (interfaces, BGP, bridges, system) are covered.