Skip to main content
Glama
jeff-nasseri

MikroTik MCP

by jeff-nasseri
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
      A
      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
      A
      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

    • 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 185 tools

    Disambiguation3/5

    Most tools follow clear per-resource CRUD patterns, but overlapping log tools (get_logs, get_logs_by_topic, search_logs, get_system_events) and similar route/DHCP-pool conveniences create real selection ambiguity. The legacy wireless tools, several explicitly unsupported, further blur the intended surface, though descriptions often help disambiguate.

    Naming Consistency3/5

    The set mostly uses verb_noun naming, but verbs are mixed across domains: add_ip_address versus create_ip_pool, set_dns_servers versus update_dns_static, and backup_info versus create_backup. Atypical names like list_wireless_access_list and remove_user_ssh_key also break the pattern, making the convention readable but inconsistent.

    Tool Count1/5

    With 185 tools, this is far beyond the practical size for an agent to reliably navigate, even for a broad network-device management domain. The count is extreme and includes multiple legacy, unsupported, and convenience-wrapper tools that inflate the surface.

    Completeness3/5

    Many subsystems have solid CRUD/lifecycle coverage, including firewall rules, NAT, queues, users, WireGuard, and VLANs. However, there are notable gaps such as no list/get for DHCP networks, only add for DNS regexp entries, no update for IP addresses, and legacy wireless security profile tools that are unsupported on current RouterOS versions.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources