ToolBB-0045

TopicForge: a read-only MCP server for inspecting ROS 2 and DDS

TopicForge gives an agent 15 read-only MCP tools for a ROS 2 graph, rosbag files and DDS discovery traffic. The code has no write path to the robot. In the README's example it finds a best-effort publisher facing a reliable subscriber. CI runs it against a ROS 2 Humble and Jazzy test bench; no physical robot is shown.

Open original source github.com · yaniswav

Claimed
Why this evidence label?

CI against a simulated ROS 2 test bench; no run on a physical robot shown.

How we check entries
Preview image for TopicForge: a read-only MCP server for inspecting ROS 2 and DDS
The source's own preview image, from github.com.

Briefing

The ROS 2 tools shell out to the ros2 CLI, so rclpy need not be installed. For DDS, TopicForge joins the domain as a read-only CycloneDDS participant and reads the standard discovery topics: participants, readers, writers and their QoS. Every tool marks itself read-only in the MCP protocol, and a test fails if one does not. Without ROS or a DDS backend it falls back to mock fixtures and reports the mode in every response.

The README lists its limits. It reads discovery, not data, so user-topic payloads are not decoded and a hung writer whose lease is still renewed looks healthy. The Fast DDS adapter has never run against a bus, and no RTI, OpenDDS or CoreDX participant has been observed. DDS Security is not handled.

From the GitHub API

Repository facts

Repository facts for yaniswav/topicforge, from the GitHub API
Repositoryyaniswav/topicforge
Stars3
LicenseMIT Permissive
LanguagePython
Last push14 Oct 2026 16 d ago

Tags

Report a problem with this entry