Skip to main content
Glama

Related Servers

Alternatives to robomcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables LLM agents to safely inspect, plan, preview, and execute motions on ROS 2 manipulators, with server-enforced safety envelopes covering joint limits, workspace constraints, force/torque thresholds, rate limits, e-stop, human approval, and audit logging.
      22
      47 PyPI
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLM coding agents to inspect, control, and verify remote ROS2 robotics applications without a local ROS2 installation, supporting topics, services, actions, parameters, TF transforms, and automated test suites.
      16
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables controlled AI-agent access to enterprise-shaped tools with a deny-by-default gated write path, human approval, dry-run execution, and append-only audit logging.
      1
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables controlling robots in ROS environments through natural language, supporting topics, services, actions, and GUI tools.
      24
      36
      MIT

    TDQS

    B3.4/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools map to a distinct resource+action: fleet listing vs single-robot state, plan_route (dry-run) vs navigate_to (execute), set_param vs get_params, emergency_stop vs clear_emergency_stop, and search_docs vs read_doc_section are all clearly separated by their descriptions. Minor overlap between get_robot_state ("state and parameters") and get_params, and between list_locations (which also reports zones) and the absent per-location getter, but boundaries remain workable.

    Naming Consistency4/5

    Predominantly consistent snake_case verb_noun pattern (list_robots, get_robot_state, set_param, restart_node, pick_item, drop_item, read_diagnostics, search_docs). A few deviations break the verb_noun form: emergency_stop is a bare noun phrase and dock/navigate_to use a verb with a preposition, but nothing is ambiguous or mixed-convention in casing.

    Tool Count4/5

    16 tools is just above the comfortable band but each earns its place across four coherent areas: fleet/state queries, movement and manipulation, parameters/diagnostics, and ROS 2 documentation lookup. No obvious redundant or filler tools, so the slightly high count reflects genuine domain breadth rather than padding.

    Completeness4/5

    Core robot lifecycle is well covered: observe state/params/diagnostics, plan and execute motion, dock and charge, pick/drop payloads, emergency stop with a paired clear, and node restart. Gaps are modest: there is no way to abort an in-flight navigation except emergency stop, and locations/zones are read-only (no create/edit of docks, shelves or keep-out zones).

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues