MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

ROS 2 MCP Server

Spec Support Unverified Community Confidence: Good (0.85)

ROS 2 MCP Server is an MCP server published by WiseVision; its MCP spec-revision support has not been verified yet. It is a community implementation. Last verified 2026-09-03.

Does ROS 2 MCP Server support the current MCP specification (2026-07-28)?

Undetermined. We have not verified which MCP specification revision ROS 2 MCP Server supports (as of 2026-09-03).

Is ROS 2 MCP Server a first-party (official) MCP server?

No. ROS 2 MCP Server is a community-published MCP server from WiseVision, not a first-party vendor server (last verified 2026-09-03).

How do I connect to ROS 2 MCP Server?

ROS 2 MCP Server is available via the package oci:docker.io/mcp/ros2, the official MCP Registry under io.github.wise-vision/mcp_server_ros_2, the source repository at https://github.com/wise-vision/ros2_mcp. Authentication: none. Transports: stdio.

What tools does ROS 2 MCP Server expose?

ROS 2 MCP Server exposes 13 tools, including ros2_topic_list, ros2_topic_subscribe, ros2_topic_publish, ros2_service_list, ros2_service_call, ros2_list_actions (last verified 2026-09-03).

When were ROS 2 MCP Server's facts last verified?

2026-09-03. Each fact on this page links to the sources used to verify it.

Which tools does ROS 2 MCP Server expose?

13 tools verified.

  • ros2_topic_list
  • ros2_topic_subscribe
  • ros2_topic_publish
  • ros2_service_list
  • ros2_service_call
  • ros2_list_actions
  • ros2_send_action_goal
  • ros2_cancel_action_goal

A Python MCP server that bridges MCP clients into ROS 2, the robotics middleware. It runs over stdio, ships as the Docker image mcp/ros2, and exposes ROS 2 introspection and control as tools: listing and subscribing to topics, publishing messages, listing and calling services, and sending, cancelling and monitoring action goals. No authentication mechanism is documented, and no remote endpoint is offered.

Its publisher, WiseVision, builds an open-source ROS 2 and LoRaWAN stack. ROS 2 itself is maintained by Open Robotics and the Open Source Robotics Alliance, so this is a community implementation against ROS 2 rather than a first-party server for it.

Two identity facts are worth recording. The repository was renamed from mcp_server_ros_2 to ros2_mcp, and the repository's own server.json now declares io.github.wise-vision/ros2_mcp, but the published registry record still carries the old name at version 1.0.0 from 2025-11-26. The catalog keeps the registry name as the identity key and points repo_url at the current location. Separately, the repository's documentation refers to three different Docker image names across its install instructions, while the registered and published artifact is docker.io/mcp/ros2.

Spec-revision support is unverified. The README links the 2025-06-18 prompts section of the specification to explain what prompts are, which points at the spec without claiming support for that revision, and the mcp[cli]>=1.23.0 dependency floor establishes an SDK version rather than a protocol revision.

How was this verified, and what are the sources?

Verified · method: registry-record · confidence 0.85 (Good).

  1. Official MCP Registry record for io.github.wise-vision/mcp_server_ros_2, fetched 2026-09-03 - version 1.0.0, published 2025-11-26, package oci docker.io/mcp/ros2:latest with stdio transport, repository https://github.com/wise-vision/mcp_server_ros_2 - accessed
  2. GitHub repository, fetched 2026-09-03 - the registered path wise-vision/mcp_server_ros_2 now returns HTTP 301 to wise-vision/ros2_mcp; description "Advanced MCP Server ROS 2 bridging AI agents straight into robotics", MPL-2.0, 86 stars, 14 forks, last push 2026-08-19, not archived - accessed
  3. The repository's own server.json on the default branch, fetched 2026-09-03 - declares name io.github.wise-vision/ros2_mcp and repository https://github.com/wise-vision/ros2_mcp, which is the rename the published registry record does not yet reflect - accessed
  4. Repository README, fetched 2026-09-03 - "This server enables AI tooling to connect with ROS 2 nodes, topics, and services using the MCP standard over stdio"; documents stdio only, no remote endpoint and no auth mechanism, and lists the ros2_* tool set - accessed
  5. Docker Hub repository mcp/ros2, fetched 2026-09-03 - 12,867 pulls, registered 2025-09-15, and the image description states it is built by Docker Inc., confirming that presence in the mcp/ namespace is a Docker curation decision - accessed