console-switch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_portsA | 列出计算机上所有可用的串口（COM口）。用于查找通过Console线连接的交换机所在的端口号。 |
| connectA | 通过Console口连接到网络设备（如华为/H3C/思科交换机）。连接后可以发送命令进行配置和调试。 常用波特率：华为/H3C 默认 9600，部分设备 115200。 Windows 端口示例: COM1, COM3 Linux 端口示例: /dev/ttyUSB0, /dev/ttyS0 macOS 端口示例: /dev/cu.usbserial-xxxx |
| send_commandA | 向已连接的交换机发送一条命令，并获取返回结果。 华为交换机常用命令示例：
注意：进入 system-view 后提示符会从 变为 [Huawei]，此时可执行配置命令。 |
| send_configA | 批量发送配置命令给交换机。自动逐条执行，适合批量配置场景。 使用前请确保已进入 system-view（系统视图）。 示例命令：
每行一条命令，按顺序执行。 |
| disconnectA | 断开与交换机的Console口连接。 |
| get_statusA | 获取当前连接状态，包括是否已连接、端口、波特率、检测到的设备类型等信息。 |
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 6 tools
Each tool has a clearly distinct role: listing ports, connecting/disconnecting, checking status, and sending commands (single vs. batch). The overlap between send_command and send_config is clarified by their descriptions, making misselection unlikely.
Most tools follow a verb_noun pattern (list_ports, get_status, send_command, send_config), while connect and disconnect are standalone verbs. This is a minor deviation but remains predictable and readable.
With 6 tools, the set is well-scoped for a console management server, covering the essential operations without redundancy or bloat.
The server covers the full lifecycle: discovering ports, connecting, checking status, sending individual commands, and batch configuration. No obvious gaps for typical console-based switch management.