Multi-robot TurtleBot3 Gazebo/Nav stack — device market

Install

Three ways to run this device. Each one serves its fake backend: no instrument, no simulator install and no upstream checkout.

OpenAI4S (one command)

shell

openai4s lab add robots/mortezaaliyari__multi-robot-gazebo-navistack

Installs the device into the OpenAI4S Lab on its fake backend and starts it. First time? See setup below.

Or, in the workbench, open the Lab tab → Market → Install.

Standalone MHS endpoint

shell

git clone --depth 1 https://github.com/PKU-YuanGroup/OpenMHS.git && cd OpenMHS
PYTHONPATH=MHS/sdk/src python3 -m mhs serve robots/mortezaaliyari__multi-robot-gazebo-navistack --port 7400
# in a second terminal, from the same directory:
PYTHONPATH=MHS/sdk/src python3 -m mhs describe --endpoint http://127.0.0.1:7400

Serves the device as an MHS endpoint on port 7400 from an OpenMHS clone (Python 3.10 or later, standard library only); describe prints what it offers.

Any MCP host (Claude Desktop, Cursor, …)

mcp configuration

{
  "mcpServers": {
    "multi-robot-gazebo-navistack": {
      "command": "python3",
      "args": [
        "-m",
        "mhs",
        "serve",
        "robots/mortezaaliyari__multi-robot-gazebo-navistack",
        "--mcp"
      ],
      "env": {
        "PYTHONPATH": "/path/to/OpenMHS/MHS/sdk/src"
      }
    }
  }
}

Add this server to the host's MCP configuration and replace /path/to/OpenMHS with the path of your OpenMHS clone. The host starts the server and talks to it on stdin and stdout.

What it does

Measures

read_tb3_0_odom
read_tb3_0_scan
read_tb3_1_odom
read_tb3_1_scan

Adjusts

Nothing declared.

Actions

publish_tb30_cmd_vel: Publish one geometry_msgs/Twist velocity setpoint to the tb3_0 Gazebo cmd_vel topic; the receipt confirms only that rosbridge accepted the publication, not motion, arrival or stopping
publish_tb31_cmd_vel: Publish one geometry_msgs/Twist velocity setpoint to the tb3_1 Gazebo cmd_vel topic; the receipt confirms only that rosbridge accepted the publication, not motion, arrival or stopping
resume_simulation: The declared re-enable after a safety reset: publish a zero Twist on /tb3_0/cmd_vel and /tb3_1/cmd_vel, then unpause the Gazebo world with /gazebo/unpause_physics. Each differential-drive plugin keeps the last cmd_vel it stored and applies it as soon as the world runs; the zeros replace them, but they are unacknowledged publications, so a stored command can still act for a few world steps, and a running move_base publishes new ones.

Names as the driver declares them. Units, limits and the safety declaration are in the package's REFERENCE.md.

First-time setup

The OpenAI4S workbench with the OpenMHS lab, from a source checkout:

shell

# OpenAI4S workbench with the OpenMHS lab (source checkout)
git clone --recursive https://github.com/PKU-YuanGroup/OpenAI4S.git
cd OpenAI4S && ./setup.sh && source .venv/bin/activate
openai4s lab add robots/mortezaaliyari__multi-robot-gazebo-navistack
openai4s serve        # open the Lab tab

The standalone endpoint and the MCP server need only an OpenMHS clone and Python 3.10 or later. More in the market's getting-started guide and on the OpenAI4S host page.

Source and evidence

Upstream: mortezaaliyari/multi-robot-gazebo-navistack
Pinned commit: afcc20c73158
Licence: MIT
Stars: 29
Evidence: contract_checked on the fake backend
Backends: fake

The driver package MHS/drivers/robots/mortezaaliyari__multi-robot-gazebo-navistack wraps the upstream code at the pinned commit. Its REFERENCE.md documents the full contract: every value, action, unit, limit and the safety declaration.