Pure Data: OSC control from Claude, scripts and controllers¶
0 named commands to drive Pure Data over OSC — from Claude (MCP), live-coding environments or a MIDI controller.
| Device | Pure Data |
|---|---|
| Vendor | Pure Data |
| OSC prefix | /pd |
| Source | 📡 From the software's own OSC API |
| Firmware | Pure Data 0.55-x |
| Revision | Pd 0.55-x (passthrough) |
| Upstream | vendor-osc-api |
| Driver file | devices/pure-data/puredata.vendor-osc-api.fw-0.55.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 pd: ask “what can the Pure Data do?” and it reads this map with list_routes. See the MCP guide.
Limitations¶
Passthrough mode — Pure Data does not impose any OSC path layout. The bridge forwards under `/pd/...` to a [netreceive] object listening on UDP 9000 (configurable). You build the OSC parsing inside your patch via [oscparse] and route messages via [route]. Replies sent back via [netsend] / [oscformat] reach the bridge's reply_port and re-emit as `/pd/...` to clients.