Cockos Reaper: OSC control from Claude, scripts and controllers¶
8 named commands to drive Cockos Reaper over OSC — from Claude (MCP), live-coding environments or a MIDI controller.
| Device | Cockos Reaper |
|---|---|
| Vendor | Cockos |
| OSC prefix | /reaper |
| Source | 📡 From the software's own OSC API |
| Firmware | Reaper 7 |
| Revision | Reaper 7 (Default.ReaperOSC) |
| Upstream | vendor-osc-api |
| Driver file | devices/cockos/reaper.vendor-osc-api.fw-7.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:
Then send OSC to 127.0.0.1:7777, for example:
From Claude or any MCP client, the osc-bridge mcp server exposes this driver as reaper: ask “what can the Cockos Reaper do?” and it reads this map with list_routes. See the MCP guide.
OSC commands (8)¶
| OSC address | Arguments |
|---|---|
/reaper/transport/play |
|
/reaper/transport/stop |
|
/reaper/transport/record |
|
/reaper/transport/tempo |
bpm: float |
/reaper/track/{n}/volume |
n: int, v: float |
/reaper/track/{n}/mute |
n: int, on: bool |
/reaper/track/{n}/solo |
n: int, on: bool |
/reaper/track/{n}/arm |
n: int, on: bool |
Limitations¶
v1 covers transport (play / stop / record / tempo), per-track volume / mute / solo / arm for the first 8 tracks. Reaper's OSC pattern file is highly customizable; this driver matches the default mapping. If you've customized Default.ReaperOSC, adapt the driver paths accordingly. Track indices are 1-based.