winbox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROS_HOST | No | RouterOS host for configuring a single router instead of using ~/.config/winbox-mcp/routers.json. | |
| ROS_USER | No | RouterOS username for configuring a single router instead of using ~/.config/winbox-mcp/routers.json. | |
| ROS_PASSWORD | No | RouterOS password for configuring a single router instead of using ~/.config/winbox-mcp/routers.json. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Control MikroTik RouterOS routers like WinBox does. Start with list_routers (or discover_neighbors then add_router). Menus use API paths: '/ip/address', '/interface/bridge/port', '/routing/ospf/instance'. Read with ros_print, change with ros_add / ros_set / ros_remove / ros_enable / ros_disable, run any API command with ros_command (e.g. '/system/reboot', '/tool/ping'), and use ros_cli for plain terminal commands (SSH) such as '/export' or scripts. Items can be referenced by .id ('*1') or by name.
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 |
|---|---|
| list_routersA | List the routers this server knows (passwords hidden) and which one is the default. |
| add_routerB | Add (or replace) a router. transport: 'api' (8728), 'api-ssl' (8729), 'rest' (v7 REST over http/www, e.g. a WebFig port) or 'rest-ssl'. port: the API/REST port if not standard. ssh_port: used by ros_cli / ros_export / file tools. save: persist to the config file (password stored there with 0600 permissions). |
| remove_routerA | Forget a router (does not touch the device). |
| discover_neighborsB | Find MikroTik devices on the local networks via MNDP (like WinBox's Neighbors tab). |
| ros_printB | Read a menu (like opening a WinBox window). path e.g. '/ip/address', '/interface', '/ip/firewall/filter', '/routing/ospf/neighbor', '/system/resource', '/log'. where: equality filters {'interface': 'ether1', 'disabled': False}. proplist: only these fields. query: raw API query words, e.g. ['?>bytes=1000', '?#|']. |
| ros_addA | Add an item, e.g. path='/ip/address', properties={'address': '10.0.0.1/24', 'interface': 'ether2'}. Returns the new .id. |
| ros_setC | Change an item. item: '.id' like '*3', a name, or 'key=value'. Omit item for single-value menus such as '/system/identity', '/ip/dns', '/system/clock'. |
| ros_removeC | Remove an item by .id, name, or 'key=value' (e.g. path='/ip/address', item='address=10.0.0.1/24'). |
| ros_enableC | Enable an item (interface, rule, route ...). |
| ros_disableC | Disable an item (interface, rule, route ...). |
| ros_commandB | Run ANY RouterOS API command: full path including the verb. Examples: '/system/reboot', '/tool/ping' {'address': '8.8.8.8', 'count': 3}, '/ip/firewall/filter/move' {'numbers': '*5', 'destination': '*2'}, '/system/package/update/check-for-updates', '/interface/monitor-traffic' {'interface': 'ether1', 'once': ''}, '/tool/traceroute' {'address':'1.1.1.1','count':1}. Long-running commands need 'count' / 'once' / 'duration' so they end. |
| ros_cliC | Run plain terminal commands over SSH and return the text output, exactly as typed in the WinBox 'New Terminal'. Multiple commands can be separated by ';' or newlines. E.g. '/ip route print detail', '/export hide-sensitive', ':put [/system resource get cpu-load]'. |
| ros_exportC | Export the configuration as a .rsc script (whole config, or one menu like '/ip firewall'). |
| system_overviewC | Identity, RouterOS version, board, CPU/RAM/uptime, interfaces, IP addresses and routes summary. |
| ros_pingC | Ping from the router. |
| ros_backupB | Create a binary backup (/system backup save) on the router; download it with ros_file_download. |
| ros_file_downloadC | Download a file from the router (SFTP), e.g. a .backup or .rsc. |
| ros_file_uploadC | Upload a file to the router (SFTP), e.g. an .npk package, a .rsc to /import, or a certificate. |
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 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.