Skip to main content
Glama

Related Servers

Alternatives to ros2-doctor-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that enables LLMs to inspect and analyze ROS 2 systems through natural language, covering nodes, topics, parameters, actions, rates, QoS, and environment health. It can run without ROS 2 installed and safely surfaces runtime system state for diagnosis.
      13
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that lets an AI agent inspect a ROS2 graph, its underlying DDS participants, readers, writers and QoS mismatches, and recorded bag files, with twelve typed tools that behave the same against a live robot or built-in mock fixtures. It has no write path at all, so it can never publish to the bus or command a robot.
      18
      339 PyPI
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A read-only diagnostic server that inspects Linux PTP/Chrony status, PHC hardware-timestamping capabilities, and ROS 2 topic header timestamps to surface clock-domain mismatches, jitter, drift, and alignment problems in robotics systems. It exposes 15 tools and 4 prompts that generate traceable JSON or Markdown reports, running entirely locally over stdio without root access, cloud inference, or any clock modification.
      15
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only offline inspection of Planning and Control and LiDAR-SLAM recordings across MCAP, SQLite ROS 2 bags, and ROS 1 bags, including timing summaries and bounded mapped-signal samples. It exposes tools for bag summaries and standardized signal sampling without requiring a local ROS 2 installation.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only diagnosis of deployment failures across AWS, Vercel, Docker, CI/CD, and application stacks by correlating project files, logs, and provider evidence into ranked findings with safe recommendations and verification steps.
      2
      MIT

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation4/5

    The core families are clear: diagnose_* tools for deep read-only verdicts, *_ready for boolean pre-flight checks, analyze_*/check_*/score_map for offline post-hoc analysis, and ros_graph for graph introspection. The main soft spot is that diagnose_robot (aggregates all stacks) overlaps with the per-stack diagnose_nav2 / diagnose_arm / diagnose_slam / diagnose_perception, which could cause an agent to hesitate, though "Start here" and "merged verdict" mitigate this. diagnose_nav2 vs nav2_ready and diagnose_arm vs arm_ready are close in topic but differ clearly in output shape (findings vs boolean).

    Naming Consistency4/5

    All names use consistent snake_case and mostly follow verb_object (diagnose_*, analyze_*, check_reach, score_map), with a small coherent second family noun_ready (nav2_ready, arm_ready) and one noun_noun outlier (ros_graph). The _ready suffix family is internally predictable, so the deviation reads as intentional rather than sloppy. Minor inconsistency between verb-led and noun-led names keeps it from a 5.

    Tool Count5/5

    Twelve tools is squarely in the well-scoped range and each has a distinct job: five online stack diagnostics, two readiness checks, one graph lister, and four offline analyzers. Nothing appears redundant enough to cut, and no obvious category is missing a tool that would need to be bolted on later. The split between online and offline concerns is a sensible scoping of the server's purpose.

    Completeness4/5

    Coverage across the ROS2 debugging lifecycle is strong: graph/domain discovery (ros_graph), per-stack diagnostics (Nav2, arm, SLAM, perception), pre-flight readiness, and offline evaluation of force, reach, maps and trajectories. Gaps are minor but real: ready checks exist only for Nav2 and the arm (not SLAM/perception), and there is no dedicated TF-tree or log/dmesg inspection tool despite stale TF being a cited failure mode. These are workable around via the diagnose_* hints rather than hard dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues