ROS2 MCP

ROS2 MCP is an open-source (MPL-2.0) Model Context Protocol server that lets AI agents (Claude, Cursor, Codex and any other MCP client) list, subscribe to, publish on and call ROS 2 topics, services and actions on a live robot. It talks to ROS 2 directly through rclpy: no rosbridge, no changes to your robots. Transports: stdio (default), Streamable HTTP and SSE (deprecated by the MCP spec).

Every tool is free and open source. Commercial support is available if you want help putting it on a real machine.

⚡ Quickstart (30 seconds, Docker)

You need Docker and an MCP client. ROS 2 itself does not have to be installed: the image contains it.

# Claude Code (use :humble for a ROS 2 Humble system). Read-only: the agent can look, not act.
claude mcp add ros2 -- docker run -i --rm -e ROS2_MCP_READONLY=1 wisevision/ros2_mcp:jazzy

Any other MCP client: run docker run -i --rm -e ROS2_MCP_READONLY=1 wisevision/ros2_mcp:jazzy as its stdio command. Then ask: "List the ROS 2 topics" and "Read three messages from /chatter".

No robot at hand? Start a demo publisher first:

docker run -d --name demo-robot ros:jazzy-ros-base bash -c \
  'source /opt/ros/jazzy/setup.bash && ros2 topic pub -r 2 /chatter std_msgs/msg/String "{data: hello from the robot}"'

Prefer uv? On a machine with ROS 2 installed and sourced (the server needs rclpy; use the Python that matches your distro, e.g. 3.12 on Jazzy):

source /opt/ros/jazzy/setup.bash
uvx --python /usr/bin/python3 --from git+https://github.com/wise-vision/ros2_mcp mcp_ros_2_server

Remove -e ROS2_MCP_READONLY=1 (or the --read-only flag) only when you want the agent to be able to move things; see Security. Client-specific setup (VS Code Copilot, Claude Desktop, Warp, Codex CLI, custom messages): installation guide. Docs: wisevision.tech/docs.

mcp/ros2 in Docker's official MCP catalog (13,750 pulls at the time of writing) is built by Docker and lags our releases: it was last updated on 2026-02-04 and predates read-only mode. wisevision/ros2_mcp is built and pushed by this repository's CI and is the one the commands above use.

🧰 Tools

24 tools. ⚠ marks tools that can change robot state; read-only mode removes them. The complete, generated reference with input schemas is docs/generated/tools.md (a CI check keeps it in sync with the code).

Also included: four built-in prompts, automatic QoS selection for topics, nested message fields, and custom message types (source your package before starting; see the installation guide).

🧭 Supported ROS 2 distributions

ROS 1 is not supported (the server uses rclpy). Python 3.10 or newer.

🆚 How it compares

Other open-source ROS MCP servers exist. They make different trade-offs; pick by what you need. Facts below were read from each project's README, pyproject.toml and GitHub page on 2026-10-14.

When to pick another one: you need ROS 1, node or parameter tools, or you want the MCP server off the robot with only rosbridge exposed there: use robotmcp/ros-mcp-server. We do not claim to be better on every axis. What we offer: native rclpy access (no bridge process between the agent and DDS), a read-only mode that fails closed (a tool is registered in that mode only if it was explicitly reviewed as read-only, and a test fails when a new tool is unclassified), images, maps and point clouds returned as PNGs, the complete action lifecycle (goal, result, feedback, status, cancel), and commercial support if you need it. Something here is wrong or out of date? Open an issue and we will fix it.

🗺️ Roadmap (proposed, not committed)

What users ask for that is not in ROS2 MCP today. No dates; open an issue or a Discussion to vote or to pay for one.

• Parameter tools: get / set / list node parameters.
• TF tools: transform lookup and frame tree.
• Authentication for Streamable HTTP (bearer token or a documented reverse-proxy recipe). The transport itself is in #55; until auth exists, keep it on loopback or a private network.
• Node tools (list nodes, node info), Nav2-specific helpers, a PyPI package, ROS 1 (not planned).

🤖 For AI agents

If you are an agent (or building one) using this server:

• Discover before you act. Call ros2_topic_list, ros2_service_list, ros2_list_actions and ros2_interface_list, then ros2_get_message_fields for the exact message type, before any publish, service call or action goal. Do not guess field names.
• Prefer read-only. If ros2_topic_publish, ros2_service_call, ros2_send_action_goal are absent from list_tools, the operator started the server in read-only mode; do not try to work around it.
• Mutating tools move real machines. Confirm intent with the human before calling a ⚠ tool, start with small values and a short duration, and keep ros2_cancel_action_goal in mind.
• Right after container start the graph may be incomplete (DDS discovery). If a topic you expect is missing, retry once before concluding it does not exist; see DDS discovery warm-up.
• Machine-readable references: docs/generated/tools.json (every tool and its input schema), server.json (MCP registry manifest), AGENTS.md (repo layout, how to build, test and add a tool), wisevision.tech/llms.txt.

🏢 Commercial support & integration

ROS2 MCP is free software under the MPL-2.0: you can use it in a commercial product without asking us. Nothing in this section changes that.

If you are putting it on a real robot or fleet and want more than the public issue tracker, WiseVision (the maintainers) can help with:

• Integration support: getting the server running against your stack, your message types and your QoS constraints.
• Custom tools and prompts: handlers for your own interfaces, beyond the built-in topic, service and action set.
• Priority fixes: a defect that blocks your deployment, handled on a schedule instead of a backlog.

How to reach us: use the form at wisevision.tech/contact (choose ROS2 MCP on a real fleet) or write to hello@wisevision.tech. Tell us the problem first: what robot, what stack, what is blocking you. We scope and quote per project; there is no price list, so please contact us. Questions that other users could learn from belong in Discussions or issues.

Want to see it on real data first? The forklift rosbag demo replays a warehouse forklift recording and walks through three MCP calls in about ten minutes.

⚙️ Installation

Follow the installation guide for step-by-step instructions:

• 🧩 Install in Visual Studio Code Copilot
• 🤖 Install in Claude Desktop
• 💻 Install in Warp
• 🐳 Build Docker Image locally

🔒 Security: read-only mode

An agent connected to a real robot can move it. Start the server in read-only mode to let the agent observe but not act:

ROS2_MCP_READONLY=1 uv run mcp_ros_2_server      # env var
uv run mcp_ros_2_server --read-only              # or CLI flag
docker run -i --rm -e ROS2_MCP_READONLY=1 mcp/ros2

In read-only mode the tools that change robot state are not registered at all: they do not appear in list_tools, and calling one returns an Unknown tool error. The hidden tools are: ros2_topic_publish, ros2_publish_multiple_topics, ros2_service_call, ros2_send_action_goal, ros2_cancel_action_goal. Read-only mode fails closed: only tools that were explicitly reviewed as read-only (listed in server/tool_safety.py) are registered, and a test fails if a new tool is added without being classified. ros2_service_call is hidden because the server cannot know whether an arbitrary service has side effects.

🌐 Streamable HTTP (remote / multi-client)

stdio is the default and needs no network. To serve several clients, or a client on another machine, use Streamable HTTP, the transport the current MCP specification defines (the older sse transport is deprecated by the spec and kept only for existing clients).

uv run mcp_ros_2_server --transport streamable-http          # http://127.0.0.1:8123/mcp
claude mcp add --transport http ros2 http://127.0.0.1:8123/mcp   # Claude Code; other clients: use the URL

Docker (publish the port on loopback only):

docker run --rm -p 127.0.0.1:8123:8123 \
  -e ROS2_MCP_TRANSPORT=streamable-http -e ROS2_MCP_HOST=0.0.0.0 -e ROS2_MCP_READONLY=1 \
  wisevision/ros2_mcp:jazzy                                 # http://127.0.0.1:8123/mcp

ROS2_MCP_HOST=0.0.0.0 is needed inside the container (a loopback bind is unreachable through -p); the 127.0.0.1: in -p keeps it off your network. If the first tool call lists no topics, DDS discovery is not crossing the container boundary; on Linux --network host (then drop -p and ROS2_MCP_HOST) is the usual fix, but that depends on your DDS and network setup.

⚠️ There is no authentication. Anyone who can reach the port can use every tool, including publishing to topics. Keep it on loopback or a private network, put an authenticating reverse proxy in front of anything wider, and consider read-only mode. The server prints a warning when it binds to a non-loopback address.

🧭 DDS discovery warm-up (Docker)

If the first tool call returns an incomplete list of topics/services right after container start, DDS discovery may still be in progress. The server performs a one-time warm-up on the first tool call in container environments; tune it via:

• MCP_ROS_DISCOVERY_STABLE_SEC (default: 1.0)
• MCP_ROS_DISCOVERY_TIMEOUT_SEC (default: 5.0)
• MCP_ROS_DISCOVERY_WARMUP=false to disable

🤖 Prompts

📘 Want to create a custom prompt? Check the guide here

📊 base.ros2-topic-echo-and-analyze

Subscribe to a ROS2 topic, collect messages for a specified duration, and provide statistical analysis of the collected data.

➡️ Can auto-detect topic if only one is available. Analyzes message rates, counts, and statistics on numeric fields.

🔄 base.ros2-topic-relay

Subscribe to one ROS2 topic and republish messages to another topic with optional transformations.

➡️ Supports identity relay, rate limiting, and change-based filtering.

🏥 base.ros2-node-health-check

Check if expected ROS2 topics and services are available and functioning correctly with optional publication rate monitoring.

➡️ Provides comprehensive health report with status indicators and recommendations.

🔍 base.ros2-topic-diff-monitor

Compare two ROS2 topics and report differences in their messages with detailed field-by-field analysis.

➡️ Useful for comparing raw sensor data with filtered/processed versions or verifying topic synchronization.

ROS2 MCP also has a prompts extension with additional prompts: see here

💡 Don’t know what prompts are? See the MCP spec here.

Note: To call a service with a custom (non-default) type, source the package that defines it before starting the server.

🎬 Demos

🚀 Drone mission using prompts

🌍 Real-world example

Want to try it in simulation? See the Gazebo drone demo.

🐞 Debugging

Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.

You can launch the MCP Inspector via npm with this command:

npx @modelcontextprotocol/inspector uv --directory /path/to/ros2_mcp run mcp_ros_2_server

Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.

🤝 Contributing

Contributions are welcome. Check the open issues, open a pull request, or drop by our Discord to discuss ideas first. See AGENTS.md for dev setup and tests. By participating you agree to our Code of Conduct.

📚 Origins

We built this server to make AI‑assisted ROS 2 development fast and reliable. Internally, we needed a simple way for agents to discover message types, publish/subscribe to topics, and call services—without boilerplate or flaky networking. That led to a few core design goals:

• Handle all ROS 2 message types (including nested fields) so agents can write and test any code
• Integrate topic pub/sub and service calls to validate behavior end‑to‑end
• Work seamlessly with GitHub Copilot in VS Code and other MCP clients
• Use a simple stdio transport to avoid network complexity

After dogfooding it, we open‑sourced the project (MPL-2.0) to help the broader ROS 2 community build faster with AI. It’s now useful not only for development, but also for controlling robots, running QoS experiments, and analyzing live data and robot/swarm state. The project is actively maintained—features and improvements ship regularly based on user feedback. If this project helps you, share your use case in Discussions!