Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
View ROS 2 nodes and topics, and call services and actions via MCP
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
MCP_CUSTOM_PROMPTS, MCP_PROMPTS_LOCAL, MCP_PROMPTS_PATH, MCP_PROMPTS_MODULENecesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en 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"
}
}
}
}Ejecuta esto en tu 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:latestCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
MCP_CUSTOM_PROMPTS envMCP_PROMPTS_LOCAL envMCP_PROMPTS_PATH envMCP_PROMPTS_MODULE envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub wise-vision, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (1.0.0) llegó al registro hace 12 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Docker en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Master CSS
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Inspect Master CSS classes, generated CSS, and project stylesheets from your AI client.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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:
Solo se muestra el principio; lee el resto en el repo