winbox-mcp
Related Servers
Alternatives to winbox-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables management of MikroTik routers running RouterOS 6 and 7 via SSH, Telnet, or API with automatic command adaptation. Provides over 46 MCP tools for device management, firewall, DHCP, VPN, configuration profiles, and more.3MIT
- AlicenseAqualityBmaintenanceEnables MCP agents to run RouterOS commands on MikroTik routers over SSH, with configurable profiles, secure authentication, and a read-only safety guard.316 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for managing MikroTik RouterOS fleets, exposing 65+ tools for system administration, interfaces, firewall, DHCP/DNS, PPP, diagnostics, and SSH command execution with KeePass-backed credentials.22 npm2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that sends CLI commands to MikroTik RouterOS via SSH. It allows executing any RouterOS CLI command and getting text output back.1-
- AlicenseAqualityAmaintenanceProduction-grade MCP server for MikroTik RouterOS with secure AI-native network automation.133278 npm106MIT
- AlicenseBqualityBmaintenanceMCP server for managing MikroTik RouterOS devices, enabling reading device state and performing guarded write operations such as setting identity via natural language.1142GPL 3.0
TDQS
Scored across 18 tools
The core RouterOS menu CRUD (ros_print/add/set/remove/enable/disable) is reasonably distinct, and router management (list/add/remove/discover) is clearly separate from device operations. However, ros_command ('run ANY command') and ros_cli ('run plain terminal commands') are supersets that overlap with nearly every other tool, leaving fuzzy boundaries for an agent deciding between ros_set, ros_command, and ros_cli for the same mutation/read.
A deliberate ros_ namespace covers most device operations with consistent verb style (ros_print, ros_add, ros_set, ros_remove, ros_enable, ros_disable). But the server-level tools (list_routers, add_router, remove_router, discover_neighbors, system_overview) drop the prefix and follow a separate verb_noun convention, so two conventions coexist in one set.
18 tools is slightly on the heavy side but each maps to a real RouterOS workflow (discovery, generic CRUD, toggles, CLI escape hatches, file transfer, backup, export). The count is well-justified by the broad domain rather than being redundant padding.
Coverage is strong: router registry management, generic menu CRUD, enable/disable, arbitrary API commands, SSH CLI, config export, binary backup, and SFTP file up/download. Minor gaps exist (no dedicated file list/delete or reboot tool), but these are reachable via ros_print, ros_remove, or ros_command, so few dead ends remain.