vyos-mcp
Related Servers
Alternatives to vyos-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for VyOS routers via VyManager, enabling AI agents to read and manage router configurations with RBAC, audit, and commit-confirm safety.9GPL 3.0
- AlicenseBqualityAmaintenanceAn MCP server for managing VyOS routers via the HTTPS REST API, enabling configuration changes, operational commands, and system maintenance tasks. It also provides tools to search and read live VyOS documentation directly from official sources to assist with command syntax and router features.275MIT
- AlicenseCqualityBmaintenanceMCP server for managing OpenWISP network infrastructure, enabling AI assistants to control devices, templates, topologies, and RADIUS sessions via the OpenWISP REST API.9226 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn 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 npmMIT
- AlicenseBqualityAmaintenanceMCP server for managing MikroTik RouterOS devices, enabling reading device state and performing guarded write operations such as setting identity via natural language.114GPL 3.0
- AlicenseNot gradedqualityBmaintenanceMCP server for UniFi Network Controller enabling AI assistants to manage UniFi infrastructure via natural language. It supports firewall rules, IPv6, and uses lazy/eager tool modes to minimize context usage.6Mozilla Public 2.0
TDQS
Scored across 17 tools
Each tool targets a distinct operation: set, delete, comment, batch configure, check existence, generate keys, manage images, get system info, load/merge/save config, reset sessions, read multi-valued nodes, run show commands, retrieve config subtrees, and system control. No two tools overlap in purpose.
All tools follow the vyos_<verb>_<noun> pattern (e.g., vyos_configure_batch, vyos_save_config) with a few noun-only names like vyos_info and vyos_image. The naming is largely consistent and intuitive, with minor exceptions.
With 17 tools, the set is well-scoped for VyOS router management. It covers configuration operations, system control, monitoring, and diagnostics without being excessive or sparse.
The tool surface provides comprehensive lifecycle coverage: create, read, update, delete, commit confirm, save, load, merge, existence check, multi-value retrieval, operational show commands, image management, and system reboot/poweroff. No obvious gaps.