Yahboom Mcp

io.github.sandraschiPublished by GitHub account sandraschiv2.5.0b1Updated Oct 27, 2026

SOTA 2026 Yahboom Raspbot v2 ROS 2 MCP Server

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper ToolsAI & ML

Overview

AI-generated overview

MCP server that lets an AI assistant drive a Yahboom Raspbot v2 (Boomy) robot car over ROS 2, including missions, telemetry and diagnostics.

What you can do
  • Control the robot: drive the mecanum chassis, lights, OLED and other peripherals through MCP tools and a generic tool operation.
  • Run agent missions: turn natural-language goals into plans executed on the robot, with vision detection and ultrasonic obstacle avoidance.
  • Inspect the stack: explore ROS topics and nodes, check stack health, read logs and run SSH-based diagnostics.
  • Use the companion web dashboard for manual telemetry and peripheral control alongside the machine interface.
When to use it
Worth adding if you own a Yahboom Raspbot v2 and want an AI agent to drive it, run planned missions, or inspect its ROS 2 stack and health from a desktop MCP client.
Requirements
Runs locally over stdio; the README shows a uvx install from the Git repository or an MCPB bundle for Claude Desktop, plus a Windows installer. Needs network access to the robot, configured with the YAHBOOM_IP environment variable, and a reachable ROS 2 / rosbridge or ESP32 link. Optional LLM planning uses Ollama, LM Studio or Gemini.
Before you install
The Windows installer is unsigned, so SmartScreen will warn. The server can move a physical robot and run autonomous missions, so plan for safe surroundings and supervision. It can open SSH sessions and read container logs, and it contacts the robot and any configured LLM providers over the network.

Installation

In SourceWeft

  1. Open Yahboom Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Yahboom Raspbot v2 (Boomy) — MCP Server, Webapp & Documentation

[Just] [Ruff] [Python] [Biome] [FastMCP]

📖 Installation Guide — quick start, manual setup, and troubleshooting

[CI] [FastMCP 3.4] [Python 3.12+] [ROS 2 Humble] [Ruff] [Biome] [License] [Stars] [Last commit] [Ollama] [LM Studio] [Topics]

[Boomy Hero Shot]

Download for Windows: yahboom-mcp-2.5.0-setup.exe — installer with webapp + embedded backend, one shortcut. The installer is unsigned: SmartScreen will warn — click More info > Run anyway. Claude Desktop users can instead install the MCP bundle (one-liner below).

Quick Start

Claude Desktop only (MCPB bundle):

powershell
irm https://github.com/sandraschi/yahboom-mcp/releases/latest/download/install.ps1 | iex

Every other client (Cursor, Windsurf, OpenCode, Claude Code) — stdio via uvx:

json
{  "mcpServers": {    "yahboom-mcp": {      "command": "uvx",      "args": ["--from", "git+https://github.com/sandraschi/yahboom-mcp", "yahboom-mcp", "--mode", "stdio"],      "env": { "YAHBOOM_IP": "192.168.1.11" }    }  }}

Developers from source:

powershell
git clone https://github.com/sandraschi/yahboom-mcpcd yahboom-mcpjust

This opens an interactive dashboard showing all available commands. Run just bootstrap to install dependencies, then just serve or just dev to start.

Manual Setup

If you don't have just installed:

Overview

Boomy is a Yahboom Raspbot v2 (Mecanum Version) robot car. Weighing in at approximately 1.0 kg and costing roughly $300 (fully loaded with a Raspberry Pi 5 16GB), it provides a unified platform for testing sensor integration, ROS 2 orchestration, and agentic (AI-driven) robotics. It's also great fun for kids of all ages.

The Manufacturer: Yahboom

Yahboom is a prominent player in the Chinese robotics and STEM education industry. They offer a diverse range of hardware platforms:

  • Market Range: From entry-level $50 DIY kits to advanced $2,000+ STEM robots with precision mechanical arms.
  • Industry Position: They specialize in accessible hardware for education and prototyping, positioned below enterprise-grade platforms such as Unitree or Noetix.
  • Developer Ecosystem: Yahboom maintains a strong commitment to a FOSS (Free and Open Source Software) stack and provides active GitHub support for developers.

🏗️ Hardware Architecture

Boomy utilizes a "Double-Stack" controller model to bridge real-time physical reliability with high-level cognitive tasks:

  1. Rosmaster (ESP32 / Micro-ROS): Small-form-factor hardware controller for low-latency motor control, ultrasonic pinging, and line-sensor processing.
  2. Raspberry Pi 5 (Optional / Gateway): The main brain for standalone operation.

🚀 The "Zero-Host" Swarm Config

For scaled deployments, Boomy can operate in a Pi-less Swarm mode:

  • Setup: Remove the Raspberry Pi; replace with a WiFi-to-Ethernet/UART bridge ($15).
  • Control: Centralized orchestration via a remote Mothership (PC with RTX 4090).
  • Scaling: Deploy 3+ units for the price of a single Pi-hosted robot.

🕹️ Interface Separation

This project clearly distinguishes between human-operable controls and machine-optimized interfaces:

  • Human Interface: A browser-based Web Dashboard (React/Vite) designed for manual telemetry observation, peripheral control (lights, OLED), and human-robot interaction.
  • Machine Interface: A standards-compliant MCP Server (Model Context Protocol) designed for AI agents and MCP clients to programmatic control Boomy as a tool within a larger fleet.

Fleet Crossconnects (Companions)

yahboom-mcp works completely standalone. You can optionally connect it with companion servers in the sandraschi fleet to unlock extended features:

Companion ServerFeature UnlockedStatusSetup
speech-mcpspoken-feedback, voice-synthesisOptionalInstall Guide
reaper-mcpaudio-playback, soundboard-fxOptionalInstall Guide
virtualdj-mcpdeck-control, music-playbackOptionalInstall Guide

Self-Contained Companions: Fleet companions operate independently. Installing companions does not trigger transitive dependency chains.

📂 Documentation Pillars

PillarFocusKey Topics
Autonomous Missionsv2.4.0 — Ollama → ROSNatural-language goals → LLM planning → ROS execution; vision detection (SSD MobileNet v2); ultrasonic obstacle avoidance; "find our dog" walkthrough.
Startup & bringupStart here (robot + Goliath)ROS 2 vs rosbridge_suite (software) vs USB controller tier under the Pi; boot order; Docker/systemd on the Pi; what the webapp can restart; dashboard vs diagnostics.
Agent missions & MCPLLM → Pi missionsyahboom_agent_mission (MCP) and POST /api/v1/agent/mission (HTTP); MissionPlanV1; env vars; boomy_mission_executor; Nav2 and /boomy/detections_json; troubleshooting vs yahboom_agentic_workflow.
Rosmaster ArchitectureDual-bus analysisI2C (0x2b) for motors/sensors, UART for IMU/battery; register map; container layout; micro-ROS analysis.
Stack health probehealth.stackTTL SSH/TCP probes, YAHBOOM_ROS2_CONTAINER, lifecycle (never started vs exited vs restart loop), optional docker logs preview (redacted).
Setup & InstallationDev installuv, modes, baseline env vars.
Software & LogicArchitectureSystem design, ROS 2 node graphs, and state management.
Hardware & PinoutsPhysical LayerWiring diagrams, I2C addresses, and sensor technical specs.
Raspbot v2 hardware stackBoomy chassisChassis, mecanum, motors, lightstrip, PTZ, camera, IMU, ultrasonic, line/cliff, expansion board vs rosbridge software, Pi ports, I2C, battery, switch.
ROS 2 BridgeConnectivityBridge architecture, topic map, state cache, env vars, known bugs.
Voice & AudioSound SystemCSK4002 module protocol, espeak-ng TTS, chatrobot architecture, audio soundboard with 17 built-in effects.
Multi-Robot IntegrationEcosystemFederated fleet standards and cross-robot communication protocols.
ConfigurationReferenceEnv vars, ports, transport modes, LLM providers.
DevelopmentReferenceDev setup, layout, test commands, five-gate.
ToolsReferenceMCP tools, yahboom_tool operations, REST endpoints.
TroubleshootingReferenceCommon issues and fixes.
OnboardingFirst-time setupHardware bring-up for Boomy (robot power, IP, sanity checks).

Webapp status surfaces

  • Dashboard (/dashboard) — First page: basic robot link (gateway, target IP, ROS · SSH · video) and operator hints when the Raspbot is off or Goliath has no AP/Ethernet path.
  • Diagnostic Hub (/diagnostics) — Detail: ROS topic explorer, node list, resync / hard reset, SSH shell, stack health table (same stack payload as the dashboard when available).
  • Server logs (/logs) — Live yahboom-mcp log stream (SSE) on Goliath.

Historical status logs and legacy research are preserved in the docs/archive/ directory.

Stack

LayerTech
MCPFastMCP 3.4 (Unified Gateway: stdio + HTTP/SSE)
BackendFastAPI + uvicorn, Pydantic v2, structlog
Robot linkroslibpy (rosbridge) / direct ESP32 TCP / mock bridge, paramiko SSH
Vision/audioOpenCV, faster-whisper, edge-tts, pytapo
FrontendReact 19 + Vite 5 + TailwindCSS 3 + Lucide + Framer Motion + Zustand + Three.js
Package managersuv (Python), bun (webapp)
DesktopTauri 2 + NSIS (PyInstaller sidecar backend)
Qualityruff + pyright + pytest (+coverage) / tsc + Biome / Playwright
LLMOllama (:11434) + LM Studio (:1234) auto-discovery, Gemini mission planning

🛡️ Industrial Quality Stack

This project adheres to SOTA 2026 industrial standards for high-fidelity agentic orchestration:

  • Python (Core): Ruff for linting and formatting. Zero-tolerance for print statements in core handlers (T201).
  • Webapp (UI): Biome for sub-millisecond linting.
  • MCP: FastMCP 3.4 with Unified Gateway, portmanteau tools, skills, and agentic sampling.
  • LLM Providers: Auto-discovery of Ollama (:11434) and LM Studio (:1234). GPU metrics via nvidia-smi.
  • Automation: Justfile recipes for all fleet operations (just lint, just fix, just dev).

Source: README.md at commit 58378e3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.5.0b1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts