Skip to main content
Glama
denver6000

mikrotik-mcp

by denver6000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mikrotik-mcp

No user-submitted related servers found.

    Related Servers

    • MikroTik MCP Server

      stormbliss
      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

    • Network Operator MCP

      ZJUSCT
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to access network device management interfaces via SSH, keeping credentials on the server side. Supports both interactive terminal sessions and command execution on devices like Huawei VRP, MikroTik, and OpenWrt.
      1
      -

    • mikrotik-cli-mcp

      Kamilake
      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
      -

    • mikrotik-mcp

      vesact
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for managing MikroTik RouterOS fleets, exposing 65+ tools for system administration, interfaces, firewall, DHCP/DNS, PPP, diagnostics, and SSH command execution with KeePass-backed credentials.
      14 npm
      2
      Apache 2.0

    • keenetic-mcp

      salatmaster
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP agents to control Keenetic routers via plain language, providing network monitoring, device management, and safe configuration changes with backup and read-only options.
      18
      289 npm
      27
      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

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: mikrotik_exec runs commands against the router, mikrotik_search_docs searches offline documentation, and mikrotik_list_profiles discovers configured profiles. There is no overlap in purpose and the descriptions reinforce the intended call order (list_profiles → search_docs → exec).

    Naming Consistency4/5

    All names share the mikrotik_ prefix and are snake_case, with search_docs and list_profiles following a clean verb_noun pattern. mikrotik_exec deviates slightly by using a bare verb with no noun object, but the convention is otherwise predictable.

    Tool Count4/5

    Three tools is on the lean side, but this is intentional and well-scoped: a single generic exec tool subsumes arbitrary RouterOS commands, so no per-command tools are needed. Anything less (e.g. dropping the docs or profile helper) would hurt usability, so the count is justified.

    Completeness4/5

    The lifecycle is covered end to end: discover profiles, look up syntax, then execute (read or write) with read-only safety enforced. Minor gaps exist, such as no batch/multi-command execution or profile management, but agents can work around these using the generic exec tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources