Skip to main content
Glama
robotmcp

ROS MCP Server

by robotmcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ROS MCP Server

No user-submitted related servers found.

    Related Servers

    • ROS MCP

      Yutarop
      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

    • ROS MCP Server

      moneypiaorui
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables control of ROS/ROS2 robots through natural language commands by translating LLM instructions into ROS topics and services. Supports cross-platform WebSocket-based communication with existing robot systems without requiring code modifications.
      MIT

    • KentraBOT MCP Server

      kentra
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to control a two-track robot through movement commands, providing independent track control, high-level directional driving (forward, backward, left, right), and emergency stop functionality.
      -

    • Robot Navigation MCP Server

      827346462
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables robot navigation control and monitoring through natural language. Provides tools for robot positioning, navigation to coordinates, device status monitoring, task management, and emergency controls.
      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
      -
    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

    B3.2/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have distinct purposes focused on different ROS operations like service calls, topic management, and network configuration. However, there is some overlap between get_services and inspect_all_services, as well as between subscribe_once and subscribe_for_duration, which could cause minor confusion in tool selection.

    Naming Consistency4/5

    The naming follows a consistent snake_case pattern with clear verb_noun structures like get_topics, call_service, and publish_once. Minor deviations exist, such as ping_robot (which is more specific) and set_websocket_ip (which uses 'set' instead of a more common verb like 'configure'), but overall the conventions are readable and predictable.

    Tool Count4/5

    With 17 tools, the count is slightly high but reasonable for a ROS server that needs to cover services, topics, messages, and network operations. It provides comprehensive functionality without being overwhelmingly large, though it borders on the upper limit of a well-scoped set.

    Completeness5/5

    The tool set offers complete coverage for ROS operations, including CRUD-like actions for services and topics (e.g., call, get, publish, subscribe), message and service details retrieval, and network configuration tools. There are no obvious gaps, and agents can handle core workflows like monitoring, publishing, and service interaction effectively.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources