Derivative TouchDesigner: OSC control from Claude, scripts and controllers¶
0 named commands to drive Derivative TouchDesigner over OSC — from Claude (MCP), live-coding environments or a MIDI controller.
| Device | Derivative TouchDesigner |
|---|---|
| Vendor | Derivative |
| OSC prefix | /td |
| Source | 📡 From the software's own OSC API |
| Firmware | TouchDesigner 2023.x |
| Revision | TouchDesigner 2023 (passthrough) |
| Upstream | vendor-osc-api |
| Driver file | devices/touchdesigner/touchdesigner.vendor-osc-api.fw-2023.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 td: ask “what can the Derivative TouchDesigner do?” and it reads this map with list_routes. See the MCP guide.
Limitations¶
Passthrough mode — TouchDesigner's OSC surface is whatever the OSC In CHOP / DAT / OSC In DAT operators in the project decide to receive. The bridge forwards `/td/...` (with `/td` stripped) to UDP 7000. Replies from TouchDesigner via OSC Out CHOP / DAT pointed at port 7001 re-emit as `/td/...` to clients.