Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
View ROS 2 nodes and topics, and call services and actions via MCP
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
MCP_CUSTOM_PROMPTS, MCP_PROMPTS_LOCAL, MCP_PROMPTS_PATH, MCP_PROMPTS_MODULEYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"ros-2": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_CUSTOM_PROMPTS",
"-e",
"MCP_PROMPTS_LOCAL",
"-e",
"MCP_PROMPTS_PATH",
"-e",
"MCP_PROMPTS_MODULE",
"docker.io/mcp/ros2:latest"
],
"env": {
"MCP_CUSTOM_PROMPTS": "your-value",
"MCP_PROMPTS_LOCAL": "your-value",
"MCP_PROMPTS_PATH": "your-value",
"MCP_PROMPTS_MODULE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add ros-2 --env MCP_CUSTOM_PROMPTS=your-value --env MCP_PROMPTS_LOCAL=your-value --env MCP_PROMPTS_PATH=your-value --env MCP_PROMPTS_MODULE=your-value -- docker run -i --rm -e MCP_CUSTOM_PROMPTS -e MCP_PROMPTS_LOCAL -e MCP_PROMPTS_PATH -e MCP_PROMPTS_MODULE docker.io/mcp/ros2:latestFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ros-2": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_CUSTOM_PROMPTS",
"-e",
"MCP_PROMPTS_LOCAL",
"-e",
"MCP_PROMPTS_PATH",
"-e",
"MCP_PROMPTS_MODULE",
"docker.io/mcp/ros2:latest"
],
"env": {
"MCP_CUSTOM_PROMPTS": "your-value",
"MCP_PROMPTS_LOCAL": "your-value",
"MCP_PROMPTS_PATH": "your-value",
"MCP_PROMPTS_MODULE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"ros-2": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_CUSTOM_PROMPTS",
"-e",
"MCP_PROMPTS_LOCAL",
"-e",
"MCP_PROMPTS_PATH",
"-e",
"MCP_PROMPTS_MODULE",
"docker.io/mcp/ros2:latest"
],
"env": {
"MCP_CUSTOM_PROMPTS": "your-value",
"MCP_PROMPTS_LOCAL": "your-value",
"MCP_PROMPTS_PATH": "your-value",
"MCP_PROMPTS_MODULE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
MCP_CUSTOM_PROMPTS envMCP_PROMPTS_LOCAL envMCP_PROMPTS_PATH envMCP_PROMPTS_MODULE envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account wise-vision, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 12 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Aiterm MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Persistent terminals and one launcher for Claude, Codex, Grok, Cursor, and Antigravity harnesses.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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/ros2in 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_mcpis built and pushed by this repository's CI and is the one the commands above use.
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).
| Area | Tools |
|---|---|
| Discover | ros2_topic_list, ros2_service_list, ros2_list_actions, ros2_interface_list, ros2_get_message_fields (field names and types of a message type) |
| Topics | ros2_topic_subscribe, ros2_subscribe_multiple_topics (images come back as PNG), ⚠ ros2_topic_publish, ⚠ ros2_publish_multiple_topics (set frequency and duration) |
| Services | ⚠ ros2_service_call |
| Actions | ⚠ ros2_send_action_goal (optionally waits for the result), ros2_action_request_result, ros2_action_subscribe_feedback, ros2_action_subscribe_status, ⚠ ros2_cancel_action_goal |
| Perception | ros2_get_map_as_image (nav_msgs/OccupancyGrid to PNG), ros2_get_pointcloud_as_bev (sensor_msgs/PointCloud2 to bird's-eye-view PNG) |
| History | ros2_get_messages_stored_in_influx_data_base (past messages from the WiseVision Data Black Box, an InfluxDB-based alternative to Rosbag2) |
| Viewer app | ros2_viewer_app, ros2_viewer_config, ros2_stream_start, ros2_stream_next, ros2_stream_next_image, ros2_stream_stop (interactive image / point cloud / plot viewer for MCP clients that support Apps; the stream tools also serve clients that cannot render it) |
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).
| Distro | Status |
|---|---|
| Jazzy Jalisco (Ubuntu 24.04, Python 3.12) | Supported. Tests run in CI on ros:jazzy-ros-base; Docker image wisevision/ros2_mcp:jazzy. |
| Humble Hawksbill (Ubuntu 22.04, Python 3.10) | Supported. Tests run in CI on ros:humble-ros-base; Docker image wisevision/ros2_mcp:humble. |
| Iron, Kilted, Rolling | Not tested and not shipped. It may work from source; we make no promise. Open an issue if you need one. |
ROS 1 is not supported (the server uses rclpy). Python 3.10 or newer.
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.
| ROS2 MCP (this repo) | robotmcp/ros-mcp-server | LCAS/ros2_mcp | |
|---|---|---|---|
| How it reaches ROS | rclpy, directly on the ROS 2 graph (runs where ROS 2 is sourced, or in the Docker image) | rosbridge WebSocket; the MCP server can run on a different machine from the robot | ROS 2 package built in your colcon workspace |
| ROS versions | ROS 2 Humble, Jazzy | ROS 1 and ROS 2 | ROS 2 Humble, Iron, Jazzy (per its README) |
| Install | Docker image wisevision/ros2_mcp, or uvx/uv from git | uvx ros-mcp (on PyPI) | git clone, rosdep, colcon build; Docker Compose with an SSE endpoint |
| Transports | stdio, Streamable HTTP, SSE | stdio, http, streamable-http (--transport) | SSE endpoint documented |
| Read-only mode | Yes: mutating tools are not registered, and a test enforces the classification | No such switch found in its code; tools carry the MCP readOnlyHint annotation | Its README lists observation features only |
| Publish / services / actions | Yes, including goal, result, feedback, status and cancel | Yes (topics, services and actions tools) | Not listed in its README |
| Nodes and parameters | No dedicated tools yet | Yes (node and parameter tools) | Node listing |
| Images and maps | Image topics as PNG, occupancy-grid map, point-cloud bird's-eye view | Image tool | Image retrieval for VLM analysis |
| License | MPL-2.0 | Apache-2.0 | Apache-2.0 |
| GitHub stars | 90 | 1,493 | 9 |
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.
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.
If you are an agent (or building one) using this server:
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.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.ros2_cancel_action_goal in mind.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.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:
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.
Follow the installation guide for step-by-step instructions:
Only the beginning is shown; read the rest in the repo