Ableton MCP: every way to let an AI edit your Live set

The short answer. There's no official way for Claude to edit a running Live set. There are five kinds of open-source bridge: a Python Remote Script with a socket (ahujasid/ableton-mcp and projects built on it), an OSC bridge (AbletonOSC), a JavaScript bridge (ableton-js), a Max for Live device (Producer Pal), and servers that run inside Live through the Extensions SDK (beta, Suite only). They need a desktop MCP client, not the Claude website. Save a copy of your set first: undo behaves differently in each.

"Ableton MCP" isn't one product. It's a set of community projects that all solve the same problem: Live has no public API for outside apps, so each one needs a way in. That way in decides what it can do, what you install, and how its edits land in Live's undo history.

All of this is as of 1 October 2026. Projects in this space change weekly; check each README before you install.

How an MCP bridge to Live works

Every setup has three parts:

1. An MCP client. The AI app you talk to: Claude Desktop, Claude Code, Cursor, or another client that supports MCP servers on your machine.
2. An MCP server. A small program the client starts or connects to. It turns tool calls ("add a MIDI clip with these notes") into instructions for Live.
3. A way into Live. Something running inside Live that carries out those instructions: a Remote Script, an OSC listener, a Max for Live device or an Extension.

The first two are standard. The third is where the projects differ.

The Remote Script bridges

ahujasid/ableton-mcp

The original and the most starred, at 3.1k stars on GitHub when we checked on 1 October 2026. MIT licensed.

• How it connects: a Python Remote Script in Live opens a socket server. The MCP server talks to it over that socket with a JSON protocol.
• Requirements: "Ableton Live 10 or newer", plus the uv Python tool.
• Setup: install uv. Add a server that runs uvx ableton-mcp to Claude Desktop's config (or paste uvx ableton-mcp into Cursor's MCP settings). Install the Remote Script with uvx --from ableton-mcp ableton-mcp-install-script. In Live, open Settings → Link, Tempo & MIDI, choose AbletonMCP as a Control Surface and set its Input and Output to None.
• What it can do: create and change MIDI and audio tracks, write MIDI clips and notes, load instruments and effects from Live's browser, control the transport and build arrangements.
• Limits it states: complex arrangements "might need to be broken down into smaller steps", and it's "designed to work with Ableton's default devices and browser items". Run it in one client only: "Only run one instance of the MCP server (either on Cursor or Claude Desktop), not both."
• Telemetry: anonymous usage telemetry is on by default (an install ID, a session ID, which tools ran, whether they worked and how long they took; no content). Turn it off with ABLETON_MCP_DISABLE_TELEMETRY=true. Separately, on the first tool call it asks once whether to record your work (prompts, MIDI notes, track and clip names, device settings) for an open dataset that may be used to train music models. That stays off unless you say yes.
• Undo: the README doesn't say how its edits land in Live's undo history.

uisato/ableton-mcp-extended

A larger project inspired by the original. MIT, 273 stars on 1 October 2026.

• How it connects: its own Remote Script, over TCP, with an optional UDP mode for low-latency parameter changes.
• Requirements: "Ableton Live 11+ (any edition)" and Python 3.10 or higher.
• Extras: device parameter control, automation, a framework for custom controllers, and text-to-speech through ElevenLabs.
• Limits it states: automation point placement has known bugs ("This feature isn't working perfectly yet").

The OSC and JavaScript bridges

Simon-Kansara/ableton-live-mcp-server (AbletonOSC)

MIT, 395 stars on 1 October 2026.

• How it connects: through AbletonOSC, a Remote Script that gives Live an Open Sound Control interface (it listens on port 11000 and replies on 11001). The MCP server translates tool calls into OSC messages.
• Requirements: Python 3.8+, uv, and AbletonOSC installed separately. AbletonOSC itself "requires Ableton Live 11 or above".
• Limits: it can only do what AbletonOSC exposes.

xiaolaa2/ableton-copilot-mcp (ableton-js)

MIT, 94 stars on 1 October 2026.

• How it connects: through ableton-js and its AbletonJS MIDI Remote Script.
• Requirements: Node.js 20 or later. Tested on Live 12.1.10; Live 11 and 10 are "not tested yet".
• Setup: npx @xiaolaa2/ableton-copilot-mcp --install-scripts installs the Remote Script; the client runs the server with npx -y @xiaolaa2/ableton-copilot-mcp.
• Undo: its README is blunt: "Direct manipulation of MIDI clips by AI may result in the loss of original notes and cannot be undone with Ctrl + Z. Please operate with caution." It keeps its own operation history and snapshots, so you can ask it to roll back note operations.

The Max for Live device: Producer Pal

Producer Pal packages an MCP server as a Max for Live device. Free and open source under GPL-3.0.

• How it connects: you drop Producer_Pal.amxd on a MIDI track. The device serves MCP over HTTP on a local port.
• Requirements: "Ableton Live 12.3+ with Max for Live"; Live 12.4 or later is recommended.
• Clients: Claude (with a Claude Desktop extension), Gemini, ChatGPT, Mistral, and local models through Ollama or LM Studio. There's also an npm package for other MCP clients.
• Why people pick it: no Remote Script and no Control Surface setup.

Inside Live: Extensions SDK servers (beta)

On 2 June 2026 Ableton released the Extensions SDK as a free public beta: "An open JavaScript toolkit allowing anyone to create custom tools that expand the possibilities inside Live 12 Suite." It needs Live 12 Suite beta 12.4.5 or later, and it isn't available in Standard, Intro or Lite. Ableton doesn't mention MCP, but developers have used it to run MCP servers inside Live.

One example is next-live-mcp, an unofficial MIT project (brand new, with no stars yet on 1 October 2026):

• How it connects: the server runs inside Live as an Extension, over streamable HTTP at http://127.0.0.1:20808/mcp, with a bearer token per install.
• Setup: enable Extensions in Live's settings and drag its .ablx file onto the install zone.
• Undo: "Every write is one named undo step", so one Cmd/Ctrl-Z reverts a whole tool call, and batches are all or nothing.
• Limits it states: no transport or playback control, clip launching, track routing, third-party plugins or automation envelopes yet.

Because it runs inside Live's own extension system, this route is the most likely future for AI tools in Live. Today it's beta software on a beta Live.

Setting up any of them: what a client config looks like

Claude Desktop starts local servers from a JSON file: ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows (Settings → Developer → Edit Config opens it). An entry looks like this:

{
  "mcpServers": {
    "AbletonMCP": {
      "command": "uvx",
      "args": ["ableton-mcp"]
    }
  }
}

Quit and restart Claude Desktop after editing it. The MCP docs explain where to find its logs if the server doesn't connect.

Claude Code adds servers from the command line (docs):

# a server the client starts itself (stdio)
claude mcp add ableton -- uvx ableton-mcp

# a server that is already running (HTTP), with a token
claude mcp add --transport http live http://127.0.0.1:20808/mcp \
  --header "Authorization: Bearer <token>"

Whatever you choose:

• Use a desktop client. The server runs on your computer next to Live, so the client has to run there too. The Claude website can't reach it.
• Save a copy of your set first. Undo behaviour differs, as above.
• Approve tool calls while you learn what each one does. Claude Desktop asks for your approval before each tool call by default.

Which one fits

For the wider picture (Live's own stem separation, its MIDI tools, the connector and third-party assistants) see AI in Ableton Live.

A different route: a DAW that is its own MCP server

monody, the DAW we make, takes the other approach. It isn't a bridge into Live and it doesn't control Live. It's a separate desktop DAW for macOS, and the MCP server is part of the app. There's no Remote Script and no control surface: Settings → Account → Use monody from Claude shows the claude mcp add line with your port and key. Each run_commands call is one labeled, undoable transaction, and if any command in it fails, nothing is applied. MCP access comes with the Pro and Studio plans. Details are on the MCP page.

It meets Live through the file format instead: monody opens Live 12 sets (.als) and exports a Live project folder with stems. See the Ableton Live page.

Sources

• GitHub: ahujasid/ableton-mcp, uisato/ableton-mcp-extended, Simon-Kansara/ableton-live-mcp-server, ideoforms/AbletonOSC, xiaolaa2/ableton-copilot-mcp, t1merickson/next-live-mcp
• Producer Pal: home and installation
• Ableton: Introducing the Extensions SDK and Extensions
• Anthropic: Claude for creative work (28 April 2026)
• Model Context Protocol: Connect to local MCP servers; Claude Code: MCP

Checked on 1 October 2026. Ableton and Live are trademarks of Ableton AG; monody is not affiliated with or endorsed by Ableton, and neither are the projects above unless they say so.