Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
SOTA 2026 Yahboom Raspbot v2 ROS 2 MCP Server
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account sandraschi, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (2.5.0b1) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Tethered Trust
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCP server and web dashboard for the Yahboom Raspbot v2 (Boomy) ROS 2 robot - lidar mapping, navigation, camera missions and voice control.
📖 [Installation Guide](INSTALL.md) — quick start, manual setup, and troubleshooting
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).
Claude Desktop only (MCPB bundle):
irm https://github.com/sandraschi/yahboom-mcp/releases/latest/download/install.ps1 | iex
Every other client (Cursor, Windsurf, OpenCode, Claude Code) — stdio via uvx:
{
"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:
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.
If you don't have just installed:
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.
Yahboom is a prominent player in the Chinese robotics and STEM education industry. They offer a diverse range of hardware platforms:
Boomy utilizes a "Double-Stack" controller model to bridge real-time physical reliability with high-level cognitive tasks:
For scaled deployments, Boomy can operate in a Pi-less Swarm mode:
This project clearly distinguishes between human-operable controls and machine-optimized interfaces:
yahboom-mcp works completely standalone. You can optionally connect it with companion servers in the sandraschi fleet to unlock extended features:
| Companion Server | Feature Unlocked | Status | Setup |
|---|---|---|---|
speech-mcp | spoken-feedback, voice-synthesis | Optional | Install Guide |
reaper-mcp | audio-playback, soundboard-fx | Optional | Install Guide |
virtualdj-mcp | deck-control, music-playback | Optional | Install Guide |
Self-Contained Companions: Fleet companions operate independently. Installing companions does not trigger transitive dependency chains.
| Pillar | Focus | Key Topics |
|---|---|---|
| [Autonomous Missions](docs/ops/AUTONOMOUS_MISSIONS.md) | v2.4.0 — Ollama → ROS | Natural-language goals → LLM planning → ROS execution; vision detection (SSD MobileNet v2); ultrasonic obstacle avoidance; "find our dog" walkthrough. |
| [Startup & bringup](docs/ops/STARTUP_AND_BRINGUP.md) | Start 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 & MCP](docs/ops/AGENT_MISSION_AND_MCP.md) | LLM → Pi missions | `yahboom_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 Architecture](docs/hardware/ROSMASTER_ARCHITECTURE.md) | Dual-bus analysis | I2C (0x2b) for motors/sensors, UART for IMU/battery; register map; container layout; micro-ROS analysis. |
| [Stack health probe](docs/ops/STACK_HEALTH_PROBE.md) | `health.stack` | TTL SSH/TCP probes, `YAHBOOM_ROS2_CONTAINER`, lifecycle (never started vs exited vs restart loop), optional `docker logs` preview (redacted). |
| [Setup & Installation](docs/ops/installation.md) | Dev install | uv, modes, baseline env vars. |
| [Software & Logic](docs/core/) | Architecture | System design, ROS 2 node graphs, and state management. |
| [Hardware & Pinouts](docs/hardware/) | Physical Layer | Wiring diagrams, I2C addresses, and sensor technical specs. |
| [Raspbot v2 hardware stack](docs/hardware/RASPBOT_V2_HARDWARE_STACK.md) | Boomy chassis | Chassis, mecanum, motors, lightstrip, PTZ, camera, IMU, ultrasonic, line/cliff, expansion board vs rosbridge software, Pi ports, I2C, battery, switch. |
| [ROS 2 Bridge](docs/hardware/ROSBRIDGE.md) | Connectivity | Bridge architecture, topic map, state cache, env vars, known bugs. |
| [Voice & Audio](docs/hardware/VOICE_AUDIO.md) | Sound System | CSK4002 module protocol, espeak-ng TTS, chatrobot architecture, audio soundboard with 17 built-in effects. |
| [Multi-Robot Integration](docs/fleet/) | Ecosystem | Federated fleet standards and cross-robot communication protocols. |
| [Configuration](docs/CONFIGURATION.md) | Reference | Env vars, ports, transport modes, LLM providers. |
| [Development](docs/DEVELOPMENT.md) | Reference | Dev setup, layout, test commands, five-gate. |
| [Tools](docs/TOOLS.md) | Reference | MCP tools, yahboom_tool operations, REST endpoints. |
| [Troubleshooting](docs/TROUBLESHOOTING.md) | Reference | Common issues and fixes. |
| [Onboarding](docs/ONBOARDING.md) | First-time setup | Hardware bring-up for Boomy (robot power, IP, sanity checks). |
*Historical status logs and legacy research are preserved in the docs/archive/ directory.*
| Layer | Tech |
|---|---|
| MCP | FastMCP 3.4 (Unified Gateway: stdio + HTTP/SSE) |
| Backend | FastAPI + uvicorn, Pydantic v2, structlog |
| Robot link | roslibpy (rosbridge) / direct ESP32 TCP / mock bridge, paramiko SSH |
| Vision/audio | OpenCV, faster-whisper, edge-tts, pytapo |
| Frontend | React 19 + Vite 5 + TailwindCSS 3 + Lucide + Framer Motion + Zustand + Three.js |
| Package managers | uv (Python), bun (webapp) |
| Desktop | Tauri 2 + NSIS (PyInstaller sidecar backend) |
| Quality | ruff + pyright + pytest (+coverage) / tsc + Biome / Playwright |
| LLM | Ollama (:11434) + LM Studio (:1234) auto-discovery, Gemini mission planning |
This project adheres to SOTA 2026 industrial standards for high-fidelity agentic orchestration:
print statements in core handlers (T201).Only the beginning is shown; read the rest in the repo