Session and transport
Control playback, tempo, scale, loops, scenes, locators, recording and Ableton Link.
The open-source Ableton Live MCP server
Turn ideas into tracks with Claude, Cursor or Codex. AbletonMCP connects your AI assistant to Live with 156 typed tools for MIDI, devices, arrangement and mixing. All through a local bridge.
“Build an 8-bar house groove at 124 BPM.”
set_tempogenerate_drum_patterncreate_clipA prompt becomes specific actions in your Live set.
From the first note to the final arrangement
Every operation has a documented schema and validated arguments, with read-only and destructive hints that help clients act predictably. There is no arbitrary-code execution path.
Control playback, tempo, scale, loops, scenes, locators, recording and Ableton Link.
Create, route and balance MIDI, audio and return tracks with live meter feedback.
Write notes, edit probability, quantize, set loops, apply groove and control audio clips.
Find instruments and effects, load presets and control native device parameters.
Place material on the timeline, inspect arrangement clips and write automation envelopes.
Generate drums, chords, basslines, melodies, motifs and complete genre starter sessions.
Local connection
Your MCP client launches the server through uvx. A bundled Remote Script runs inside Ableton Live and connects over localhost. There is no AbletonMCP cloud relay and no repository to clone.
uvx [email protected] installRestart Live. Open Settings → Tempo & MIDI → MIDI, select AbletonMCP in an unused Control Surface row, and set Input and Output to None.
uvx [email protected]Use this command in Claude, Cursor, Codex, or another stdio-compatible client.
uvx [email protected] doctor --jsonWith Live open, look for "ok": true, then ask your client to read the tempo and track names.
MCP client → local server → localhost → Ableton Live
Live and offline workflows
Build and perform in real time, or inspect saved projects without launching Ableton Live. Both workflows use the same local server.
01 / Live control
Create tracks and clips, write MIDI, load devices, control the mixer, arrange sections and record automation through Live's own API.
Explore live tools02 / Offline analysis
Summarize, lint and diff saved .als files, extract MIDI, inspect mixer state and analyze .adg or .adv racks offline.
Explore the offline workflowCommon questions
Short answers about compatibility, privacy, clients, and offline project analysis.
Yes. AbletonMCP is open source under the MIT license. You need your own Ableton Live license for live control, and your chosen AI client or model provider may charge separately.
AbletonMCP is an independent, open-source MCP server that lets compatible clients inspect and control Ableton Live 11 and 12 through typed, validated operations. MCP stands for Model Context Protocol: a standard that lets AI assistants use external tools.
It can create and edit tracks, MIDI notes, clips, scenes, devices, routing, mixer settings, Arrangement View content, automation, and generated musical material. It can also inspect saved .als, .adg, and .adv files while Live is closed.
AbletonMCP itself runs locally and communicates with Live over a loopback socket. Your chosen MCP client or model may process tool requests and results according to its own privacy settings and terms.
Any client that can launch a local stdio MCP server can use it, including Claude Desktop, Claude Code, Cursor, Codex, and compatible development tools.
Real-time control requires Live and the bundled Remote Script to be running. Offline project tools can summarize, lint, compare, and extract information from saved Ableton files without launching Live.
Install the published package, add the bundled Remote Script, and verify the local connection.