ROS-MCP-Server connects large language models (such as Claude, GPT, and Gemini) to robots, enabling bidirectional communication with no changes to existing robot source code.
MCP.Pizza Chef: robotmcp
Robots built on ROS or ROS 2 can be driven and watched by Claude, ChatGPT, or Gemini without changing a line of the robot's own code ā you add one bridging node to the setup you already have. The assistant can send movement commands, call the robot's services, read sensor values, and check its state as it goes, and it works out what a given robot offers on its own. Demonstrations include a quadruped in simulation and a factory arm being diagnosed.
Data
Other
Use This MCP server To
Tell a robot where to go in plain English Read live sensor values while the robot is running Ask what a robot can do before I command it Diagnose a robot that is behaving oddly Test a robot arm or gripper from a single instruction Try commands on a simulated robot before the real one
README
ros-mcp-server FAQ
Do I have to change my robot's code?
No. You add a rosbridge node to your existing setup and leave the robot's own code alone.
Which robot systems work?
ROS 1 and ROS 2, including the Jazzy and Humble releases.
Which assistants can drive it?
Claude Desktop, Claude Code, ChatGPT, Cursor, Codex CLI, Gemini CLI, and any other MCP client.
Do I need a paid key?
The server itself does not list one. You still need whichever assistant you plan to drive it with.
Can I use this to control a robot just by talking to it?
Yes ā the project's demos include telling a robot to fetch a drink from the fridge and walk to another room.
Can the assistant see what the robot sees?
Yes, it can read sensor data and monitor the robot's state in real time, not just send commands.