legacy-switch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SWITCH_MCP_TOOLSETS | No | Comma-separated list of toolsets to register: read, files, usr, dlink, maintenance, or all. A typo is an error, not a silent fallback. | |
| SWITCH_MCP_PASSWORD_<NAME> | No | Password for the switch named <NAME> (name upper-cased, '-' becomes '_'). Alternatively provide passwords in ~/.config/switch-mcp/passwords.json. | |
| SWITCH_MCP_ENABLE_MAINTENANCE | No | Set to 1 to register and allow maintenance plan tools (password, IP, reboot, factory reset, config restore). Maintenance is off by default. | 0 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_switchesA | Configured switches (name, address, vendor); edit ~/.config/switch-mcp/switches.json to add more. |
| list_interfacesB | IPv4 interfaces on this host that discovery can use. |
| discoverB | Broadcast/multicast discovery on one interface (e.g. vmbr0). Sends requests only; changes nothing. |
| probeA | Ask one switch by IP (works across subnets); returns its discovery reply or {"error": ...}. |
| read_pageB | One raw page of a switch's web UI. USRobotics: status, port, vlan, trunk, mirror, statistics, system, trap. D-Link: system, vlan, port, mirror, pvlan, mgmt_vlan, trunk. Read-only. |
| overviewC | Everything useful in one login (USRobotics: its main pages; D-Link: the parsed state). |
| get_stateB | Parsed state: VLANs/groups, ports, mirror, trunks, system. Read-only. |
| backup_stateB | Save the parsed state to a JSON file under ~/.local/state/switch-mcp/backups. Read-only on the switch. |
| list_snapshotsB | Saved state files (backups and the snapshot before every apply), newest first. |
| describe_switchC | Markdown description of a switch's configuration for a wiki. Read-only. |
| backup_configA | Download the configuration file to the state directory (mode 0600; it is a secret). Returns only id, size, checksum. Read-only. |
| backup_firmwareB | Download the D-Link's running firmware image (~740 KB) to the state directory. Read-only; the USRobotics has none. |
| list_filesB | Saved configuration/firmware files (id, size, time; never content), newest first. |
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 13 tools
discover vs probe are clearly distinct (broadcast on an interface vs targeted IP query), but overview and get_state overlap significantly—overview for D-Link returns 'the parsed state' which is also get_state's stated purpose. Similarly list_snapshots and list_files both enumerate saved files, requiring careful reading to distinguish.
Most tools follow a verb_noun pattern (list_switches, get_state, backup_config, describe_switch), but discover, probe, and overview are bare verbs/nouns, creating minor inconsistency. The convention is still readable and predictable overall.
13 tools is well-scoped for a switch management server covering discovery, inspection, and backup. Each tool appears to earn its place in the workflow without excessive granularity.
The surface is rich for read-only inspection and backup (discovery, state parsing, config/firmware backup, snapshots, wiki descriptions), but lacks any mutation or apply operations despite list_snapshots referencing 'the snapshot before every apply.' Agents cannot change switch configuration, a notable gap for a management server.