Back to Browse

Yahboom MCP Server

Developer ToolsModerate5.7MCP RegistryLocal
Free

Server data from the Official MCP Registry

SOTA 2026 Yahboom Raspbot v2 ROS 2 MCP Server

About

SOTA 2026 Yahboom Raspbot v2 ROS 2 MCP Server

Security Report

5.7
Moderate5.7Moderate Risk

The Yahboom MCP server is a well-structured robotics control platform with solid authentication and reasonable permissions alignment. It uses environment variables for configuration and implements proper lifecycle management for hardware resources. However, there are moderate concerns around credential handling in SSH operations, unvalidated command construction in shell execution, and insufficient input validation on some user-controlled parameters. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 1 high severity).

4 files analyzed ยท 12 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

Shell Command Execution

Runs commands on your machine. Be cautious โ€” only use if you trust this plugin.

process_spawn

Check that this permission is expected for this type of plugin.

system_info

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-sandraschi-yahboom-mcp": {
      "args": [
        "yahboom-mcp"
      ],
      "command": "uvx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Yahboom Raspbot v2 (Boomy) โ€” MCP Server, Webapp & Documentation

๐Ÿ“– 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

Quick Start

git clone https://github.com/sandraschi/yahboom-mcp
cd yahboom-mcp
just

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.

๐Ÿ“‚ 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.

๐Ÿ›ก๏ธ 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).

Reviews

No reviews yet

Be the first to review this server!