Session and transport
Control playback, tempo, scale, loops, scenes, locators, recording and Ableton Link.
get_session_infoset_tempofire_scene
Open source · Local bridge · Live 11/12
AbletonMCP gives Claude, Cursor, Codex, and compatible clients 154 typed, validated tools to build tracks, edit MIDI, load devices, arrange, mix, and inspect saved Live projects.
154 tools. One local server.
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.
get_session_infoset_tempofire_sceneCreate, route and balance MIDI, audio and return tracks with live meter feedback.
create_midi_trackset_sendget_track_metersWrite notes, edit probability, quantize, set loops, apply groove and control audio clips.
create_clipedit_notesquantize_clipFind instruments and effects, load presets and control native device parameters.
search_browserload_instrument_or_effectset_device_parameterPlace material on the timeline, inspect arrangement clips and write automation envelopes.
duplicate_to_arrangementwrite_automationcreate_locatorGenerate drums, chords, basslines, melodies, motifs and complete genre starter sessions.
generate_drum_patterngenerate_chord_progressionsetup_sessionLocal connection
Your MCP client launches the server through uvx. A bundled Remote Script runs inside Ableton Live and connects over localhost—no AbletonMCP cloud relay and no repository to clone.
uvx mcp-server-ableton-liveUse this command in Claude, Cursor, Codex, or another stdio-compatible client.
uvx mcp-server-ableton-live installRestart Live and select AbletonMCP as the Control Surface.
uvx mcp-server-ableton-live doctorWith Live open, confirm the script and local socket are ready.
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.
Create tracks and clips, write MIDI, load devices, control the mixer, arrange sections and record automation through Live's own API.
Summarize, lint and diff saved .als files, extract MIDI, inspect mixer state and analyze .adg or .adv racks offline.
Common questions
Short answers about compatibility, privacy, clients, and offline project analysis.
AbletonMCP is an independent, open-source MCP server that lets compatible clients inspect and control Ableton Live 11 and 12 through 154 typed operations.
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.