Cisco SD-WAN MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VMANAGE_URL | Yes | URL of the vManage server | |
| VMANAGE_PASS | Yes | Password for vManage | |
| VMANAGE_USER | Yes | Username for vManage |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| call_sdwan_toolC | Universal tool caller for SD-WAN operations. Args: tool_name: Name of the tool to call (e.g., 'sdwan_get_devices') arguments: Dictionary of arguments for the tool Returns: Tool execution result as a dictionary |
| list_all_toolsB | List all available SD-WAN tools |
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 are clearly distinct: list_all_tools is for discovery and call_sdwan_tool is for invoking a named operation. There is no overlap in purpose.
Both names follow an imperative verb_object pattern with snake_case, but 'all_tools' and 'sdwan_tool' are not perfectly parallel. Minor inconsistency only.
Cisco SD-WAN is a broad domain, yet only two meta-tools are exposed. The actual operations are hidden behind a generic dispatcher, making the count feel too thin for the apparent scope.
The tool surface contains no concrete SD-WAN operations; it only offers a listing helper and a universal caller. This leaves a significant gap in direct, typed tool coverage and requires agents to rely on an untyped dynamic dispatch mechanism.