Analyze music into dance timelines, preview an eight-servo Kame32, and record reusable moves. Control the app through its browser UI or MCP. Hardware playback supports stock joystick/button commands and exact servo poses with the optional firmware update.
docker compose up --build -dOpen the app on your Docker host at http://127.0.0.1:5000. Streamable HTTP MCP is available at http://127.0.0.1:8000/mcp. For a managed environment with a TLS-inspecting proxy, use the cloud build override.
Docker runs the app and MCP as non-root users with persistent move storage. Keep one app container and one Gunicorn worker; dispatch coordination is process-local. Docker deployment covers configuration, updates, audio, and health checks. For a source checkout, see development setup.
- DanceMode: upload audio, inspect its generated events, preview, and optionally send a timeline.
- TeachMoves: select Move1–Move6, record manual controls, then save, replay, or transfer a move to DanceMode.
- MCP: analyze audio, manage recordings, control connected browser tabs, or explicitly request robot dispatch.
| Hardware mode | Requirement |
|---|---|
| Auto | Prefers updated pose firmware; otherwise uses a saved stock command track |
| Stock compatibility | Recording made entirely with supported joystick/button controls and default gait/speed settings |
| Exact servo poses | Upgraded pose/watchdog firmware |
Manual servo poses cannot be converted into stock commands. Recording and browser playback do not move hardware; Send and MCP dispatch tools do. Stock firmware has no disconnect watchdog, and its routines can delay cancellation. Firmware instructions explain the optional update and physical acceptance checks.
Start with the documentation index:
- User guide
- Docker deployment and source development
- HTTP API and limits
- MCP client setup and tools
- Firmware and watchdog
- Architecture and audit / remaining work
The latest recorded Docker validation passed all 55 tests. Physical robot acceptance, authenticated remote access, and independent backups remain outstanding. Ports bind to host loopback by default; keep access restricted to trusted users. Docker volume persistence is not an independent backup.
