Skip to content

Ableton Live: OSC control from Claude, scripts and controllers

8 named commands to drive Ableton Live over OSC — from Claude (MCP), live-coding environments or a MIDI controller.

Device Ableton Live
Vendor Ableton
OSC prefix /ableton
Source 📡 From a third-party OSC API
Firmware Ableton Live 12.2.7
Revision Ableton Live 12.2.7 + AbletonOSC 0ca6821
Upstream third-party-osc
Driver file devices/ableton/live.third-party-osc.fw-12.2.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:

osc-bridge run --device devices/ableton/live.third-party-osc.fw-12.2.json

Then send OSC to 127.0.0.1:7777, for example:

osc-bridge osc-send /ableton/transport/play

From Claude or any MCP client, the osc-bridge mcp server exposes this driver as ableton: ask “what can the Ableton Live do?” and it reads this map with list_routes. See the MCP guide.

OSC commands (8)

OSC address Arguments
/ableton/transport/play
/ableton/transport/stop
/ableton/transport/tempo bpm: float
/ableton/track/{n}/volume n: int, v: float
/ableton/track/{n}/arm n: int, on: bool
/ableton/track/{n}/listen/volume n: int
/ableton/scene/{n}/fire n: int
/ableton/scene/fire_selected

Limitations

v1 covers transport (play / stop / tempo), per-track volume + arm with their subscribe/listen counterparts, and scene firing. Clip slot control, device parameters, browser navigation, undo and many other AbletonOSC endpoints are intentionally out of scope until a real user need surfaces. AbletonOSC is a community Remote Script — its stability and version compatibility with Live track its own GitHub releases, not Ableton's. Verified against Live 12.2.7 specifically; earlier 12.x minor versions are unconfirmed.