DrayTek Vigor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIGOR_HOST | No | Hostname or IP of the modem (default 192.168.167.1) | 192.168.167.1 |
| VIGOR_PORT | No | SSH port (default 22) | 22 |
| VIGOR_PROMPT | No | Prompt regex pattern (default 'vigor>\\s*$') | vigor>\s*$ |
| VIGOR_IDLE_SEC | No | Idle time in seconds to wait for command output (default 0.8) | 0.8 |
| VIGOR_PASSWORD | Yes | CLI password for the DrayTek Vigor modem | |
| VIGOR_USERNAME | Yes | CLI username for the DrayTek Vigor modem |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_commandsB | Discover CLI commands via '?' on the device. Results are cached on disk. |
| run_commandC | Run an arbitrary DrayTek CLI command over SSH. |
| run_commandsC | Run multiple CLI commands in one SSH session. |
| get_dsl_infoB | DSL sync status via verified command 'exec dslinfo'. |
| get_system_infoA | Firmware and device info via verified command 'exec sysinfo'. |
| get_device_timeA | Device clock via verified command 'exec date'. |
| get_servicesA | Open CPE services via verified command 'exec services'. |
| get_config_statusA | Config profile status via verified command 'exec cfg status'. |
| get_command_tree_summaryA | Return cached discovery tree or refresh if missing. |
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 9 tools
Each tool has a clearly distinct purpose. For example, discover_commands and get_command_tree_summary are related but serve different stages (discovery vs. cached retrieval), while run_command and run_commands differ in the number of commands executed. No two tools could be easily confused.
All tools use snake_case with a consistent pattern: get_ prefix for status retrieval, discover_ for discovery, and run_ for command execution. The naming is uniform and predictable.
9 tools is well-scoped for a network device management server. It covers discovery, common status queries, and arbitrary CLI execution without being too many or too few.
The tool set covers discovery, status checks, and command execution. While it lacks dedicated tools for some operations (e.g., interface stats, reboot), these can be achieved via run_command. Minor gaps exist but do not severely hinder common use cases.