Skip to main content
Glama

winbox-mcp

An MCP server that lets Claude (or any MCP client) control MikroTik RouterOS routers (v6/v7) — everything WinBox can do.

Install

git clone https://github.com/mohammed-w-mosabeh/winbox-mcp.git
claude mcp add -s user winbox -- uv run --directory /path/to/winbox-mcp winbox-mcp

Related MCP server: MikroTik MCP Server

Transports

api (8728), api-ssl (8729), rest / rest-ssl (v7 REST on the www port), plus SSH for ros_cli, ros_export and SFTP file transfer.

Routers live in ~/.config/winbox-mcp/routers.json (created by add_router, stored with 0600 permissions), or set ROS_HOST / ROS_USER / ROS_PASSWORD for a single router.

On the router, the api service (or www for REST) and ssh must be enabled: /ip service print.

Tools

list_routers, add_router, remove_router, discover_neighbors (MNDP), ros_print, ros_add, ros_set, ros_remove, ros_enable, ros_disable, ros_command (any API command), ros_cli (SSH terminal), ros_export, system_overview, ros_ping, ros_backup, ros_file_download, ros_file_upload.

Menus use API paths such as /ip/address, /interface/bridge/port, /routing/ospf/instance.

See also: silab-mcp — control SILAB MikroTik labs, and push lab routers into this server with silab_routers_to_winbox.

License

MIT

Available Tools

18 tools
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).

Inputs: host (required), name (required), port, save, +5 more.

discover_neighborsB

Find MikroTik devices on the local networks via MNDP (like WinBox's Neighbors tab).

Inputs: seconds. Returns: result

list_routersA

List the routers this server knows (passwords hidden) and which one is the default.

Inputs: no named parameters.

remove_routerA

Forget a router (does not touch the device).

Inputs: name (required). Returns: result

ros_addA

Add an item, e.g. path='/ip/address', properties={'address': '10.0.0.1/24', 'interface': 'ether2'}. Returns the new .id.

Inputs: path (required), properties (required), router.

ros_backupB

Create a binary backup (/system backup save) on the router; download it with ros_file_download.

Inputs: name, router, password.

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]'.

Inputs: command (required), router, timeout. Returns: result

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.

Inputs: command (required), query, params, router, +1 more. Returns: result

ros_disableC

Disable an item (interface, rule, route ...).

Inputs: item (required), path (required), router.

ros_enableC

Enable an item (interface, rule, route ...).

Inputs: item (required), path (required), router.

ros_exportC

Export the configuration as a .rsc script (whole config, or one menu like '/ip firewall').

Inputs: path, terse, router, show_sensitive. Returns: result

ros_file_downloadC

Download a file from the router (SFTP), e.g. a .backup or .rsc.

Inputs: local_path (required), remote_name (required), router. Returns: result

ros_file_uploadC

Upload a file to the router (SFTP), e.g. an .npk package, a .rsc to /import, or a certificate.

Inputs: local_path (required), router, remote_name. Returns: result

ros_pingC

Ping from the router.

Inputs: address (required), count, router, interface, +2 more. Returns: result

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', '?#|'].

Inputs: path (required), query, where, detail, +2 more. Returns: result

ros_removeC

Remove an item by .id, name, or 'key=value' (e.g. path='/ip/address', item='address=10.0.0.1/24').

Inputs: item (required), path (required), router.

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'.

Inputs: path (required), properties (required), item, router.

system_overviewC

Identity, RouterOS version, board, CPU/RAM/uptime, interfaces, IP addresses and routes summary.

Inputs: router.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 18 tools

    Disambiguation3/5

    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.

    Naming Consistency3/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that sends CLI commands to MikroTik RouterOS via SSH. It allows executing any RouterOS CLI command and getting text output back.
      1
      -