Skip to main content
Glama
asharca

ROS-MCP

by asharca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ROS-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

    • 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

    • 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.
      10 npm
      2
      Apache 2.0

    • Netmiko MCP Server

      ntunes
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables management of network devices via SSH using Netmiko, supporting command execution, configuration management, and concurrent operations across multiple vendors.
      5
      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

    A3.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: device_list is a read-only discovery operation and command_execute performs actions on a device. There is no realistic way to confuse them.

    Naming Consistency5/5

    Both names follow a clean, consistent noun_verb pattern (device_list, command_execute). The convention is uniform across the entire surface.

    Tool Count3/5

    Two tools is on the thin side for a RouterOS management server, even though a generic command gateway offsets some of that. It sits at the borderline the rubric flags as 1-2 tools feeling sparse.

    Completeness4/5

    The generic command_execute provides broad coverage of RouterOS operations, but there is no way to add, remove, or configure a device despite device_list referencing 'configured' devices, leaving a lifecycle gap.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources