Skip to main content
Glama
husain-zaidi

ros-mcp

by husain-zaidi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ros-mcp

No user-submitted related servers found.

    Related Servers

    • ros2-mcp

      ai2robot-network
      A
      license
      A
      quality
      C
      maintenance
      ROS2 MCP server that bridges AI agents (Claude Code, OpenClaw, Cursor) to ROS2, allowing them to read topics, call services, control robots, and wrap telemetry into verifiable hash-chained proof bundles.
      6
      MIT

    • ROS2 MCP Server

      kakimochi
      F
      license
      Not graded
      quality
      F
      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.
      83
      -

    • Rosbridge MCP Server

      TakanariShimbo
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides tools to publish messages to ROS topics via rosbridge WebSocket, enabling integration between language models and ROS-based robotics systems.
      MIT

    • BMAD MCP Server

      BinaryVortex
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that bridges BMAD agents with GitHub Copilot, enabling AI-assisted development workflows through specialized agent tools and prompts.
      79 npm
      1
      ISC
    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.7/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct ROS 2 entity (topic, node, service, parameter, tf2, launch). No two tools perform the same action on the same resource; monitor_topic and get_topic_info differ in whether they collect sample messages or describe topic metadata.

    Naming Consistency5/5

    All tool names use snake_case and follow a clear verb_noun pattern: list_*, get_*, set_*, run_*, monitor_*, publish_to_*, call_*, generate_*. There are no mixed conventions or ambiguous verbs like 'process' or 'do'.

    Tool Count5/5

    15 tools is within the sweet spot for a ROS 2 control surface. Each tool addresses a core need: introspection (list, get, monitor), control (run, publish, call), and configuration (set). The count feels appropriate without being bloated.

    Completeness4/5

    The set covers the main ROS 2 interaction modes: nodes, topics, services, parameters, TF frames, and launch files. A notable gap is the lack of action support or explicit node shutdown, but these are advanced use cases; the core workflows are well covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources