Interface
The Robot Operating System 2, where agents write nodes, launch files and tests, or drive robots through topics and services.
The most active tools first.
2 mo ago
quackd registers robots by name and has an LLM work toward a typed goal by calling one named skill per turn. Goals come from a terminal or from Claude over MCP, within step and time budgets, confirm gates and dry runs. The README lists eight robot bodies. Only a LeRobot SO-101 arm has run on hardware.
5 mo ago
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.
Ranked by points weighed against age. New entries with early votes rise.
21 d ago
Celal Türkmen's ETH Zurich semester project has a language model convert a therapist's plain-language request into an MCP tool call for a rehabilitation robot. A validator built from each device's YAML file of parameters, units and bounds decides whether the call reaches the hardware. The README reports runs on a Novint Falcon haptic device under ROS 2 Jazzy.
3 mo ago
Researchers had coding agents write robot behavior trees from a contract served by a robot-side MCP server. The contract lists the robot's skills, allowed operators and optional templates, and a gate validates each tree before it runs. The paper reports tests of Sonnet 4.6 and Gemma4:31b on 110 simulated tasks and 14 on a Husarion Panther running Nav2.
6 mo ago
Seif Salama built an Ackermann-steered robot that runs one ROS 2 Humble stack in Gazebo Harmonic and on a Raspberry Pi car. A custom ros2_control interface drives the motors over UART and the steering servo over I2C. A Gemini or Ollama agent takes spoken commands. We could not tell whether the README video shows the physical robot.
