The bumi-mcp server is a control and information hub for the Noetix Bumi humanoid robot, offering two main tools:
bumi_tool — Core information and status retrieval:
info (default): Tagline, vendor details, and key specs
specs: Full structured technical specifications (height, weight, DOF, compute, sensors, battery, etc.)
sdk_links: GitHub repositories and open-source landing page links
robot_status: Pings a live robot's health endpoint if BUMI_ROBOT_URL is configured; otherwise returns connected=false
virtual_twin: Guidance on simulating a virtual Bumi via resonite-mcp, robotics-mcp, or worldlabs-mcp integrations
fleet_peers: Narrative context on how Bumi fits into the RoboFang fleet alongside yahboom-mcp, dreame-mcp, and robotics-mcp
market: Market context on Noetix's story, the China humanoid robot wave, and distribution channels
bumi_agentic_workflow — LLM-powered orchestration:
Accepts natural language goals (e.g., "Summarize Bumi specs and how to show a virtual twin in Resonite")
Uses the host LLM to coordinate calls to bumi_tool and sibling MCPs, returning a coherent summary
Supports goals around specs lookup, SDK setup, virtual twin configuration, and fleet composition
Additionally, the server supports a mock bridge mode for development/testing without physical hardware, and integrates with rosbridge via roslibpy for telemetry and gated movement commands (walk, estop) — with full motion control pending hardware integration.
Enables LLM-based mission planning on device using Ollama models (e.g., Gemma3:1b) for autonomous behavior and task execution.
Provides ROS 2 integration for controlling the Bumi humanoid robot, including mission execution, vision detection, and sensor data via rosbridge.
Allows secure remote control of the Bumi robot over Tailscale VPN, enabling remote operation and demos such as the coffee shop demo.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@bumi-mcp tell Bumi to wave and say hello"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
📖 Installation Guide — quick start, manual setup, and troubleshooting
MCP server + REST bridge scaffold for the Noetix Bumi humanoid.
v0.2 adds
/api/v1/*(health, telemetry, gated control) and mock bridge for CI/teleoperator prep. Full physical motion awaits EDU hardware + Noetix SDK topic mapping — see STATUS.md and INTEGRATION.md.
Spec | Value |
Manufacturer | Noetix Robotics (Beijing) — 北京松延动力科技集团股份有限公司 |
Website | |
Models | Lite · Air · Pro · Max · EDU-Air · EDU-Pro · EDU-Max |
Price | From |
Height/Weight | 98cm / ~17kg |
DOF | 21 (6 per leg, 4 per arm, 1 lumbar, hands) |
Compute (base) | 6 TOPS |
Compute (EDU) | NVIDIA Jetson Orin Nano Super / Orin NX |
Sensors | RGB camera, IMU |
Battery | 48V 3.5Ah, 2-3h runtime, quick-swap |
Connectivity | WiFi + Bluetooth, optional 4G/5G |
Knee torque | 70 N·m |
Status | Shipping — thousands of orders placed (Dec 2025 news) |
"Bumi Bumi" voice wake word + interaction
Object recognition (RGB camera)
One-click auto-standing on startup
Mobile app control + visual programming
Smart OTA updates
Autonomous lying down / standing up
Open Source SDK & development tools
No direct e-commerce (no JD.com, Amazon, etc.). Noetix sells B2B through their sales team:
Contact | Details |
Sales email | |
Hotline | 400-096-9300 (Mon-Fri 10:00-19:00 Beijing) |
Scan QR code on noetixrobotics.com/en/contact-us | |
Inquiry form | |
Partner inquiry |
Pricing from 10,000 CNY (€1,300) for Lite model. Models: Lite · Air · Pro · Max · EDU-Air · EDU-Pro · EDU-Max. Price depends on model and quantity — contact sales for quote.
Related MCP server: robot-mcp-server
PC (Goliath) ──Tailscale── Bumi (Jetson Orin)
│
rosbridge :9090
│
bumi-mcp :10774 (/api/v1)
│
Noetix SDK (walk, joints, estop)Mock mode: BUMI_USE_MOCK_BRIDGE=1 — no hardware (default in .env.example)
Physical: BUMI_IP=<tailnet> + uv sync --extra robot
Yahboom copies in ros2/, minimal_mission_executor.py — reference only, not biped-safe
File | Purpose |
| roslibpy telemetry + gated walk/estop |
| CI / dev stand-in |
| teleoperator-facing REST |
| Readiness + bring-up |
File | Origin | Purpose |
| yahboom-mcp | Holonomic missions — not for Bumi |
| yahboom-mcp | COCO detection bridge |
| yahboom-mcp | Deprecated Pi deploy |
| boomy fork | Wheeled mission package |
git clone https://github.com/sandraschi/bumi-mcp
cd bumi-mcp
justThis opens an interactive dashboard showing all available commands. Run just serve with .env from .env.example (mock bridge by default).
Copy-Item .env.example .env
just serve
Invoke-RestMethod http://127.0.0.1:10774/api/v1/health
just test
just ciSee INTEGRATION.md — BUMI_IP, uv sync --extra robot, telemetry first, then gated motion.
MIT
BUMI_AGENTIC_WORKFLOW — High-level goals: specs, SDK setup, virtual twin, fleet composition.
Uses ctx.sample() so the host LLM can call bumi_tool and sibling MCPs (resonite, robotics).
Args: goal: Natural language, e.g. "Summarize Bumi specs and how to show a virtual twin in Resonite"
Returns: LLM summary string.
Inputs: goal (required). Returns: result
BUMI — Noetix Bumi humanoid: hero product info, OSS links, fleet virtual-twin map.
PORTMANTEAU RATIONALE: Single entry for discovery and setup; hardware control arrives when a documented local API or ROS bridge is wired (set BUMI_ROBOT_URL for optional ping).
Operations: info — tagline + vendor + key specs (default) specs — full structured hero dict sdk_links — GitHub repos + opensource landing page robot_status — if BUMI_ROBOT_URL set, GET {url}/health or /api/health; else connected=false virtual_twin — how to drive virtual Bumi via resonite-mcp / robotics-mcp / worldlabs-mcp fleet_peers — yahboom-mcp / dreame-mcp / robotics-mcp narrative for RoboFang fleet market — Noetix story, China humbot wave, JD.com + tier-1 offline context (not legal advice)
Returns: success, message, and operation-specific data.
Inputs: operation. Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 2 tools
The two tools have clearly distinct purposes: 'bumi_agentic_workflow' handles high-level orchestration by delegating to other tools, while 'bumi_tool' provides direct operations on the Bumi robot. There is no ambiguity or overlap.
Both tool names share the 'bumi_' prefix, but one uses a descriptive 'agentic_workflow' while the other uses the generic 'tool', lacking a consistent pattern. The naming is passable but not uniform.
With only 2 tools, the surface is thin but arguably appropriate for an early-stage MCP server that bundles many operations into a single 'bumi_tool' and provides an orchestration layer. It does not feel excessive, but more tools might be expected for a robot server.
The tool set covers information retrieval (specs, SDK, status) and conceptual guidance (virtual twin, fleet), but lacks actual robot control or modification operations. The server's stated scope is discovery and setup, which is partially met, but interactive features are missing.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server for Gainium — manage trading bots, deals, and balances via AI assistants
