SuperCollider (sclang): OSC control from Claude, scripts and controllers¶
0 named commands to drive SuperCollider (sclang) over OSC — from Claude (MCP), live-coding environments or a MIDI controller.
| Device | SuperCollider (sclang) |
|---|---|
| Vendor | SuperCollider |
| OSC prefix | /sclang |
| Source | 📡 From the software's own OSC API |
| Firmware | SuperCollider 3.13 (sclang) |
| Revision | SC 3.13 sclang (passthrough) |
| Upstream | vendor-osc-api |
| Driver file | devices/supercollider/sclang.vendor-osc-api.fw-3.13.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 sclang: ask “what can the SuperCollider (sclang) do?” and it reads this map with list_routes. See the MCP guide.
Limitations¶
Passthrough mode — targets sclang on port 57120 (default). Each OSC path you send under `/sclang/...` is forwarded to sclang verbatim (with `/sclang` stripped). You declare matching OSCdef inside SC. For direct scsynth control (port 57110), copy this driver and change `port` + `osc_prefix`.