Ros Mcp Server

io.github.robotmcpPublished by GitHub account robotmcpv3.1.2Updated Oct 24, 2026

Connect AI models like Claude & ChatGPT with ROS robots using MCP

VerifiedSTDIODesktop onlyDeveloper ToolsAI & ML

Overview

AI-generated overview

Connects LLM assistants to ROS robots over rosbridge, letting them publish and subscribe to topics, call services and actions, and read robot state.

What you can do
  • Publish and subscribe to ROS topics to send commands and observe robot data
  • Call ROS services and actions, and set parameters
  • Read sensor data and monitor robot state in real time
  • Discover available topics, services, actions and their types, including custom ones, so the assistant can use the right syntax
When to use it
Use it when you want an assistant to control or diagnose a ROS 1 or ROS 2 robot, for example natural-language navigation, manipulator commands, or troubleshooting hardware from manuals and live data.
Requirements
Runs as a local process installed from the PyPI package ros-mcp over stdio. Needs a reachable ROS setup with the rosbridge node added; no source code changes to the robot are required. No authentication or environment variables are declared.
Before you install
The assistant can send commands that move or operate physical robots, so unsupervised use on real hardware is risky. It also requires adding a rosbridge node to the robot, which exposes ROS topics and services over the network.

Installation

In SourceWeft

  1. Open Ros Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ROS MCP Server 🧠⇄🤖

[Static Badge] [Static Badge] [Static Badge] [Python] [pip] [Dev Container] [GitHub Repo stars] [GitHub last commit]

[Image]

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.

Why ROS-MCP?

  • No robot source code changes → just add the rosbridge node to your existing ROS setup.
  • True two-way communication → LLMs can both control robots and observe everything happening on the Robot.
  • Full context → publish & subscribe to topics, call services & actions, set parameters, read sensor data, and monitor robot state in real time.
  • Deep ROS understanding → guides the LLM to discover available topics, services, actions, and their types (including custom ones) — enabling it to use them with the right syntax without manual configuration.
  • Works with any MCP client → built on the open MCP standard, supporting Claude Code, Codex CLI, Gemini CLI, Claude Desktop, ChatGPT, Cursor, and more.
  • Works across ROS versions → compatible across ROS 2 (Jazzy, Humble, and others) and ROS 1 distros.

🎥 Examples in Action

[ROS MCP demos]

🏭 Example - AI Agent diagnosis of Industrial Robot End Effector (Video)

  • The MCP server connects Claude to a production industrial robot, with only the technician manuals as reference.
  • Claude discovers the robot's custom topic and service types and their syntax on its own.
  • From a single prompt to test the gripper, it reads the manuals, runs its own tests, finds an anomaly, and reports the root cause.

[Testing and debugging an industrial robot]

🤖 Example - Controlling "Wilson" with natural language (video)
From a single prompt — "Grab a Coke from the fridge & go to the living room." — Google Gemini uses the MCP server to navigate and manipulate autonomously. Built on ROS 2 with Nav2 (SLAM) for mapping and navigation, and MoveIt to command the manipulator.

[Wilson robot controlled with natural language]

🐕 Example - Controlling Unitree Go2 in NVIDIA Isaac Sim (video)
The MCP server connects Claude to a simulated Unitree Go2 quadruped in NVIDIA Isaac Sim, interpreting natural language commands to navigate and control the robot.

[Controlling Unitree Go2 in NVIDIA Isaac Sim]

🛠 Getting Started

Follow the installation guide to get started.

ROS-MCP works with Claude Code, Codex CLI, Gemini CLI, Claude Desktop, ChatGPT, Cursor, or any MCP-compatible client.

[Image]

📚 More Examples & Tutorials

Browse our examples to see the server in action.
We welcome community PRs with new examples and integrations!

🤝 Contributing

We love contributions of all kinds:

  • Bug fixes and documentation updates
  • New features (e.g., Action support, permissions)
  • Additional examples and tutorials

Check out the contributing guidelines and see issues tagged good first issue to get started.

📜 License

This project is licensed under the Apache License 2.0.

Source: README.md at commit 476591a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v3.1.2LatestSep 23, 2026
  2. v3.1.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts