Sonic Pi: OSC control from Claude, scripts and controllers¶
0 named commands to drive Sonic Pi over OSC — from Claude (MCP), live-coding environments or a MIDI controller.
| Device | Sonic Pi |
|---|---|
| Vendor | Sonic Pi |
| OSC prefix | /sonicpi |
| Source | 📡 From the software's own OSC API |
| Firmware | Sonic Pi 4.5 |
| Revision | Sonic Pi 4.5 (passthrough) |
| Upstream | vendor-osc-api |
| Driver file | devices/sonic-pi/sonic-pi.vendor-osc-api.fw-4.5.json |
Not tested on the device yet
This driver comes from documentation or community data and has not been checked on real hardware. If you own one, a quick test and a pull request promoting it helps everyone — see CONTRIBUTING.
How do you control it?¶
Start the bridge with this driver; it forwards named OSC commands to the software:
From Claude or any MCP client, the osc-bridge mcp server exposes this driver as sonicpi: ask “what can the Sonic Pi do?” and it reads this map with list_routes. See the MCP guide.
Limitations¶
Passthrough mode — the bridge does not interpret Sonic Pi paths. Whatever you send under `/sonicpi/...` is forwarded verbatim (with `/sonicpi` stripped) to Sonic Pi. Your Sonic Pi code matches the resulting path via `sync :osc:/...` or `live_loop` patterns. Replies (any OSC reaching the bridge's reply_port) are re-emitted with `/sonicpi/` prefix to the bridge's clients.