Skip to main content
Glama
cacack

vyos-mcp

by cacack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to vyos-mcp

No user-submitted related servers found.

    Related Servers

    • OPNsense MCP Server

      smaniktahla
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for comprehensive OPNsense firewall management, enabling AI assistants to manage firewall rules, NAT, VLANs, and network diagnostics, plus execute SSH/CLI commands. Supports safety modes like read-only and dry-run for safe operation.
      122 npm
      MIT

    • Device MCP Server

      rajib884
      A
      license
      A
      quality
      D
      maintenance
      A comprehensive MCP server for network device management via SSH/Telnet. Supports multiple vendors such as Cisco IOS and BDCOM, enabling AI assistants to execute commands and manage routers, switches, and firewalls.
      4
      MIT

    • OPNsense MCP Server

      lucamarien
      A
      license
      A
      quality
      B
      maintenance
      A secure MCP server for managing OPNsense firewalls through AI assistants. Provides 81 tools across system, firewall, network, DNS, DHCP, VPN, HAProxy, services, diagnostics, and security domains.
      81
      125 PyPI
      21
      MIT

    • vyos-mcp

      Galvill
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables managing VyOS appliances through their HTTP API, providing tools for configuration, operational commands, and interactive troubleshooting.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 27 tools

    Disambiguation3/5

    Most tools are distinct, but there are ambiguous boundaries: vyos_retrieve vs vyos_return_values vs vyos_exists all read config with different return shapes, and vyos_merge/vyos_load/vyos_configure/vyos_validate all apply config in overlapping ways. Descriptions help, but an agent could easily call the wrong one without prior domain knowledge.

    Naming Consistency3/5

    All tools share the vyos_ prefix and snake_case, but the action/noun ordering is mixed: some are verb-only (vyos_retrieve, vyos_configure), some are noun-first (vyos_config_diff, vyos_route_table), and some are noun+verb (vyos_docs_search, vyos_image_add). The pattern is readable but not predictable enough to infer tool behavior from the name.

    Tool Count2/5

    At 27 tools, the surface exceeds the comfortable range and feels heavy. Many specialized operational wrappers (vyos_interface_stats, vyos_route_table, vyos_firewall_stats, vyos_bgp_summary, vyos_traceroute) could reasonably be consolidated around the generic vyos_show command.

    Completeness4/5

    The tool set covers the VyOS lifecycle well: config read/validate/apply/confirm/save/diff/history, operational show commands, reset/generate operations, image management, and even documentation lookup. The main gaps are inherent API limitations like rollback, and image listing/logs are still reachable via vyos_show.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources