Skip to main content
Glama
drohi-r

MikroTik RouterOS MCP

by drohi-r
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MikroTik RouterOS MCP

No user-submitted related servers found.

    Related Servers

    • mikrotik-mcp

      nickcheban
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only (with limited address-list management) access to MikroTik RouterOS routers, enabling monitoring of system info, interfaces, DHCP leases, firewall rules, and more via natural language.
      1
      MIT

    • io.github.jeff

      halid9
      A
      license
      Not graded
      quality
      B
      maintenance
      Bridges AI assistants with MikroTik RouterOS devices, enabling natural language management of network configurations, firewall, VLANs, VPNs, and diagnostics via ~300 tools.
      1
      MIT

    • mtik-mcp

      ardianryan
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to audit, inspect, and safely configure MikroTik RouterOS v7 routers through tools for connection testing, system status, security audits, firewall mangle management, routing, DHCP leases, sanitized exports, containers, and adlist queries.
      26 npm
      1
      GPL 3.0

    • MikroTik MCP

      tarcisiodier
      A
      license
      Not graded
      quality
      D
      maintenance
      A bridge between AI assistants and MikroTik RouterOS devices, allowing natural language interaction to manage network configurations including VLANs, firewalls, DNS settings, and more.
      1
      MIT

    • NetPulseX

      MeAkash77
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI-assisted management of multi-vendor network devices (Cisco, Juniper, Nokia, Arista, Linux) through natural language, supporting health checks, configuration changes, routing analysis, and automation workflows.
      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

    D1.7/5.0

    Scored across 26 tools

    Disambiguation3/5

    Most tools target a distinct RouterOS resource, but `run_api_print` overlaps broadly with the per-resource getters, and `describe_device` vs `system_info` could be confused for device-level metadata. Overall, boundaries are mostly clear but not completely unambiguous.

    Naming Consistency3/5

    Names use lower_snake_case, but the pattern varies: `list_devices`, `describe_device`, and `get_server_config` are verb_noun, while `interfaces`, `routes`, and `nat_rules` are bare plural nouns. `run_api_print` and `diff_snapshots` further mix action styles, making the convention inconsistent yet still readable.

    Tool Count2/5

    With 26 tools, the set is over the comfortable range and many look like 1-1 maps to read a single recurring resource. The count adds clutter for an agent, and `run_api_print` already covers a more generic route. Some overlapping read tools could be consolidated.

    Completeness4/5

    The set covers device discovery, system info, networking health endpoints, dynamic tables, WireGuard, logs, ping, config export, and a safe-mode script-change workflow with snapshots. It lacks explicit per-resource CRUD and a rollback-restore from snapshots, but `apply_script_change` is a reasonable generic mechanism for management.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources