Skip to main content
Glama
Sign In
wiresage

MikroTik MCP

by wiresage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MikroTik MCP

No user-submitted related servers found.

    Related Servers

    • 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

    • io.github.jeff

      halid9
      A
      license
      Not graded
      quality
      C
      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

    • mikrotik-mcp

      nickcheban
      A
      license
      Not graded
      quality
      C
      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.
      2
      MIT

    • RouterOS MCP Server

      sevaepsteyn
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with MikroTik RouterOS devices through API and SSH connections, supporting network monitoring, configuration management, and diagnostics across multiple routers with automatic connection fallback.
      3
      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

    C2.4/5.0

    Scored across 212 tools

    Disambiguation2/5

    Several tools have unclear boundaries: create_ip_pool and create_dhcp_pool have nearly identical descriptions, and many log tools overlap (get_logs, search_logs, get_logs_by_topic, get_logs_by_severity, get_system_events, get_security_logs). The presence of multiple legacy wireless tools explicitly marked 'not supported in RouterOS v7.x' makes selection harder, and route/IP pool tools have overlapping variants.

    Naming Consistency4/5

    Almost all tools use snake_case with a verb_noun pattern, which is predictable across the huge surface. Minor deviations exist: create vs add, update vs set, and a few non-verb names such as safe_mode_status and backup_info, but these do not prevent understanding.

    Tool Count1/5

    212 tools is far beyond a manageable set for an agent, even for a broad platform like RouterOS. The count is inflated by many legacy or unsupported wireless tools and many narrowly scoped operations that could have been consolidated.

    Completeness3/5

    The surface covers many important RouterOS areas (interfaces, addressing, routes, firewall/NAT, DHCP/DNS, queues, WireGuard, logs, backups), but significant gaps remain: IPsec configuration is read-only, and netwatch, schedulers, and scripts have list-only surfaces. Entire common areas such as bridging, PPP, routing protocols (BGP/OSPF), hotspot, and certificates are absent, while some wireless tools are dead legacy stubs.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources