Skip to main content
Glama
ros2-mcp

ros2-mcp

Related Servers

Alternatives to ros2-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for ROS 2 that enables GitHub Copilot and other AI agents to interact with ROS 2 systems. This server provides tools for monitoring, debugging, and managing ROS 2 nodes, topics, services, and TF2 frames.
      15
      34 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and MCP clients to programmatically control a ROS 2-based robot car, execute autonomous missions, inspect telemetry, manage peripherals such as lights and OLED, and integrate with fleets.
      4
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Python-based server that enables AI assistants to control robots by integrating the Model Context Protocol (MCP) with ROS 2, allowing for natural language commands that translate into robot movement via the /cmd\_vel topic.
      84
      -
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Exposes a zero-dependency MCP server that ingests depth-sensor, joint-encoder, and tactile-array telemetry to deliver real-time spatial intelligence, trajectory generation, and safety-guarded control vectors for autonomous robots. It tracks shear-to-normal force ratios, detects micro-vibration slip onset, and adapts grasp force dynamically so agents can prevent object slip during manipulation.
      MIT

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the robot: listing topics, reading from a topic, invoking a service, aggregated status, proof bundle creation, and fingerprint hashing. There is no meaningful overlap that would cause misselection.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (list_topics, read_topic, call_service, wrap_proof), but robot_status and chain_fingerprint are noun phrases, creating a minor deviation. The pattern is still readable and mostly predictable.

    Tool Count5/5

    Six tools is well-scoped for a ROS2 interface that covers topic access, service calls, telemetry aggregation, and proof generation. The count feels appropriate for the apparent purpose without bloat or thinness.

    Completeness3/5

    Core functionality like reading topics and calling services is present, but there are notable gaps: no way to publish to topics, no service discovery or type introspection, and no node listing. The proof tools are an extra feature but do not compensate for missing standard ROS2 operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues