mcp-server-vyos

MCP server for VyOS router management via the HTTPS REST API. Provides both router management tools and live VyOS documentation lookup.

Installation

Install with uv:

uv tool install mcp-server-vyos

Upgrade to the latest release:

uv tool upgrade mcp-server-vyos

Alternatively, skip the install and let uvx fetch the server on demand -- see Claude Code below.

Configuration

Set environment variables:

• VYOS_URL — Router API endpoint (e.g., https://vyos.example.com)
• VYOS_API_KEY — API key for authentication
• VYOS_READ_ONLY — Set to true to disable all mutating tools (config changes, reboot, poweroff, etc.)

VyOS Router Setup

Enable the HTTPS API on your VyOS router:

configure
set service https api keys id my-mcp-key key <your-api-key>
set service https api rest
commit
save

Claude Code

Add to your MCP client configuration:

{
  "mcpServers": {
    "vyos": {
      "command": "mcp-server-vyos",
      "env": {
        "VYOS_URL": "https://vyos.example.com",
        "VYOS_API_KEY": "your-api-key"
      }
    }
  }
}

Without installing first, run it through uvx instead -- replace the command line above with:

      "command": "uvx",
      "args": ["mcp-server-vyos"],

Read-Only Mode

For safe, query-only access (monitoring, investigation, documentation lookup), enable read-only mode:

{
  "mcpServers": {
    "vyos": {
      "command": "mcp-server-vyos",
      "env": {
        "VYOS_URL": "https://vyos.example.com",
        "VYOS_API_KEY": "your-api-key",
        "VYOS_READ_ONLY": "true"
      }
    }
  }
}

This registers only non-mutating tools: vyos_info, vyos_retrieve, vyos_return_values, vyos_exists, vyos_config_diff, vyos_config_history, vyos_show, vyos_traceroute, vyos_interface_stats, vyos_system_resources, vyos_route_table, vyos_firewall_stats, vyos_bgp_summary, vyos_docs_search, and vyos_docs_read.

Tools

Router Management

Diagnostics

Documentation

Documentation is fetched live from the vyos-documentation repository, so it stays in sync with the latest VyOS releases. Results are cached for 1 hour.

Safety

• Configuration changes use commit-confirm by default -- changes auto-revert after 5 minutes unless confirmed with vyos_confirm
• vyos_configure accepts a list of operations applied atomically in one commit-confirm -- batch related changes into a single call so they commit or roll back together
• If the router commits without arming a rollback (a VyOS version without API commit-confirm, or another commit-confirm still pending), the tool raises an error saying the changes were committed -- confirm or let a pending window expire before the next change
• Destructive operations (vyos_reboot, vyos_poweroff, vyos_image_delete) include warning descriptions
• API keys are never logged or included in tool outputs
• Self-signed TLS certificates are accepted by default (common on VyOS)

Development

uv sync --extra dev
uv run pytest
uv run ruff check .

Dependencies are pinned in the committed uv.lock. Add --locked to uv sync to fail rather than re-resolve when the lock is out of date with pyproject.toml, which is how CI installs.

License

MIT