ROS MCP Server

uvx ros-mcp --transport=stdio

{
  "mcpServers": {
    "ros-mcp": {
      "command": "uvx",
      "args": [
        "ros-mcp",
        "--transport=stdio"
      ]
    }
  }
}

The requirement that makes it usable on hardware someone already depends on is that the robot's source code does not change: a rosbridge node is added to the existing ROS setup and the MCP server connects to it over a WebSocket, typically from a different machine on the same network. Communication runs both directions, so the model publishes commands and subscribes to sensor topics and robot state instead of firing blind. The part that saves the most configuration is type discovery — the server guides the model through enumerating topics, services and actions along with their message types, including custom ones defined by the vendor, so correct message syntax is worked out at runtime rather than declared up front. Compatible with ROS 1 and ROS 2 distributions including Humble and Jazzy.