Claude becomes an Ableton Live remote script

What it does

AbletonMCP is a two-part bridge: a Python MCP server talks to Claude Desktop or Cursor, while a MIDI Remote Script inside Ableton listens on a TCP socket. Together they turn natural-language requests into Live API calls—creating MIDI clips, loading drum racks, adding reverb, or hitting play. It is explicitly a third-party project, not built by Ableton.

The interesting bit

The clever hack is repurposing Ableton’s MIDI Remote Script system—normally meant for hardware controllers—as a generic JSON-over-TCP command server. That lets an LLM manipulate the DAW through a protocol usually reserved for physical knobs and pads.

Key highlights

• Claude can create and edit MIDI clips, add notes, and build chord progressions directly in Ableton’s session.
• Loads instruments and effects from Ableton’s built-in browser, including drum racks and synths.
• Controls transport: start/stop playback, fire clips, and tweak tempo.
• Works with both Claude Desktop and Cursor via the same MCP server.
• Uses a simple JSON protocol over TCP sockets between the remote script and the MCP server.

Caveats

• Complex arrangements may need to be broken into smaller steps; the README warns that big requests can time out or fail.
• Designed around Ableton’s default devices and browser items, so custom third-party plugin workflows may be out of reach.
• Save your work before letting an LLM experiment on your session, as the README explicitly warns.

Verdict

Try it if you want to prototype beats or sketch arrangements by describing them in chat. Skip it if you live inside automation lanes and prefer every edit under your own cursor.