Ableton MCP Server: Complete Guide (2026)

TL;DR + what you actually need

Ableton MCP is two programs that talk over a socket, not one. Get both running and Claude can control Live; miss either and nothing happens. The fast path:

• Register the MCP server. In Claude Desktop or Cursor, the command is uvx ableton-mcp. You need the uv package manager and Python 3.8+ first.
• Install the Remote Script in Live. Copy the project’s __init__.py into a folder named AbletonMCP inside Ableton’s MIDI Remote Scripts directory, then pick “AbletonMCP” as a Control Surface in Live’s MIDI settings.
• Run only one client. Claude Desktop or Cursor, not both — two MCP servers fighting over the same socket is the README’s explicit warning.

Three facts to set expectations:

• It’s free and MIT-licensed. Maintained by Siddharth Ahuja at ahujasid/ableton-mcp. You still need a paid copy of Ableton Live (10 or newer).
• It’s desktop-only. The server reaches Live over a local socket, so a desktop client is required. The Claude.ai website can’t do it.
• It controls Live; it doesn’t render audio. Think “an assistant clicking around your session,” not “a model that generates a finished WAV.”

The rest of this guide explains the socket architecture, walks the full install including the Remote Script step that trips most people, shows real prompts, and ends with the troubleshooting that bites first.

What Ableton MCP actually does

Ableton Live is a digital audio workstation (DAW) — the software producers use to record, sequence, and mix music. Ableton MCP gives an AI agent a set of verbs for driving it: make a MIDI track, drop a synth on it, write a four-bar bassline, load a reverb, set the tempo, hit play. MCP (Model Context Protocol — the open standard that lets an AI client call external tools) is the wire that carries those verbs from Claude into Live.

Concretely, you type a request in Claude — “make an 80s synthwave track” — and the agent issues a sequence of tool calls that create tracks, pick instruments from Live’s own browser, add MIDI notes, and apply effects. The maintainer’s launch demo built exactly that “lush 80s synthwave track in just two prompts,” and the README ships a list of one-line commands like “Create a Metro Boomin style hip-hop beat” and “Load a 808 drum rack into the selected track.”

The honest framing: this is a control layer, not a generative audio model. Claude isn’t synthesising sound — it’s deciding which of Live’s existing instruments and patterns to assemble, then operating Live to do it. The musicality comes from Live’s devices plus the model’s sense of arrangement, not from any audio generation. That distinction matters when you judge the output.

How it works: two halves and a socket

This is the part most guides gloss, and it explains every quirk you’ll hit. Ableton MCP is two separate components that communicate over a TCP socket on your local machine:

The protocol between them is deliberately simple: commands go out as JSON objects with a type and optional params; responses come back as JSON with a status and a result or message, all over plain TCP. That two-way, socket-based design is what lets a request flow Claude → MCP server → socket → Live, and the answer flow back.

One consequence worth holding in your head: because the link is a localhost socket, both ends must be on the same computer, and a desktop app has to own the connection. That single fact is why the Claude.ai website can’t drive Live and why “is the Remote Script actually running?” is the first question to ask whenever it goes quiet.

Install (both halves)

Prerequisites first: Ableton Live 10 or newer, Python 3.8 or newer, and the uv package manager. On macOS, install uv with:

brew install uv

On other platforms, grab it from uv’s installation page. The README is blunt about this: do not proceed before installing uv, because uvx is what runs the server.

Claude Desktop

Open Claude → Settings → Developer → Edit Config and add the server to claude_desktop_config.json:

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

Cursor

Open Cursor Settings → MCP and paste this as the command — uvx runs it without a permanent install:

uvx ableton-mcp

Whichever you pick, run only one instance — Claude Desktop or Cursor, not both at once. Two MCP servers contending for Live’s socket is the README’s explicit caution. If you want to disable the anonymous telemetry while you’re here, add an env block:

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

The catalog entry and one-click panel for this server live on its detail page. The embed below pulls install configs straight from our catalog when they’re available; if a client row is empty, the uvx ableton-mcp command above is the canonical path from the maintainer’s README. For each client’s exact config-file location, see Claude Desktop and Cursor on mcp.directory.

One-line install · Ableton Live

Open server page

Install

Cursor

One-click install

1-Click

VS Code

One-click install

1-Click

Claude Desktop

Copy configuration

Claude Code

Copy CLI command

CLI

Gemini

Copy CLI command

CLI

Codex

Copy CLI command

CLI

Windsurf

Copy configuration

ChatGPT

Add via Settings → Connectors

M

Manual

Copy configuration

The Remote Script step (where everyone trips)

Registering the MCP server is only half the job. Live won’t accept commands until its Remote Script is installed and selected. This is the step that generates the most “it doesn’t work” threads, so do it carefully.

1. Download AbletonMCP_Remote_Script/__init__.py from the repo.
2. Find Live’s MIDI Remote Scripts directory. The location differs by OS and Live version — on macOS it’s often inside the app bundle (Show Package Contents → Contents/App-Resources/MIDI Remote Scripts/) or under ~/Library/Preferences/Ableton/Live XX/User Remote Scripts; on Windows it’s typically under \AppData\Roaming\Ableton\Live x.x.x\Preferences\User Remote Scripts. Replace XX with your version (10, 11, 12).
3. Create a folder named exactly AbletonMCP in that directory and place the downloaded __init__.py inside it.
4. Launch (or fully restart) Ableton Live — it only scans Remote Scripts at startup.
5. Go to Settings/Preferences → Link, Tempo & MIDI, and in the Control Surface dropdown select “AbletonMCP”. Set its Input and Output to None.

When both halves are live, a hammer/tools icon for the Ableton MCP shows up in your client and the agent can start issuing commands. The two failure modes here are the folder being in the wrong Remote Scripts path (so “AbletonMCP” never appears in the dropdown) and forgetting to restart Live after copying. Both are covered in troubleshooting below.

What it can build

From the README’s capability list, the verbs the agent actually has:

• Read session and track info, and change session parameters like tempo.
• Create and modify MIDI and audio tracks; create, edit, and trigger clips; add notes to MIDI clips.
• Load instruments and effects from Ableton’s browser onto a track.
• Control playback — start, stop, fire clips — across both Session and Arrangement View.
• Build full song arrangements end to end in Arrangement View, with sections like intro, buildup, drop, breakdown, and outro.

That last one is the headline capability and the one that surprised people: the agent doesn’t just sketch a loop, it can lay out a whole song structure autonomously in the Arrangement View. The opinionated read: it’s strongest as a fast scaffolder — it gets a track skeleton and instrument choices on screen in seconds, and then you, the producer, take over for the parts that are actually art.

Recipes

Four prompts that show the range, drawn from the README’s own examples and how producers describe using it. Each assumes both halves are running and a Live set is open.

Recipe 1 — Genre starter in two prompts

Open an empty set and ask: “Create an 80s synthwave track.” The agent makes the tracks, loads synths and a drum rack from Live’s browser, writes melodic and bass MIDI, and adds reverb and distortion. Follow with “Add a wider pad in the chorus and bump the tempo to 118.” You’ve gone from blank session to a sketch you can produce against, without touching the mouse.

Recipe 2 — Beat in a named style

“Create a Metro Boomin style hip-hop beat, then add a jazz chord progression to the clip in track 1.” The agent loads an 808 drum rack, programs the pattern, and writes chords into the named clip. Style prompts work because the model maps the reference to instrument and pattern choices — the output is a starting point in that idiom, not a clone of any specific song.

Recipe 3 — Full arrangement scaffold

“Create a full arrangement with an intro, buildup, drop, breakdown, and outro.” This drives the Arrangement View end to end. It’s also the prompt most likely to hit a timeout on a complex set — if it stalls, ask for one section at a time (“now build the breakdown”) instead of the whole song in one shot.

Recipe 4 — Targeted edits while you work

Keep it open as a hands-free assistant during a session: “Add reverb to my drums,” “Load a 808 drum rack into the selected track,” “Set the tempo to 120 BPM,” “Play the clip in track 2.” The small, specific commands are where it’s most reliable — the bigger and vaguer the ask, the more likely it needs breaking down.

What we got wrong the first time

Two assumptions cost time, and both come from treating this like a normal cloud MCP server instead of the two-process socket bridge it is.

We registered the MCP server and expected it to just work. Adding uvx ableton-mcp to the client and seeing no errors felt like success — but nothing happened, because the Remote Script wasn’t installed yet. The server had no socket to talk to. The fix is obvious in hindsight: both halves are mandatory, and the client side gives you no warning that the Live side is missing. Install the Remote Script first, confirm “AbletonMCP” is selected as a Control Surface, then test.

We asked for an entire song in one prompt and got a timeout. A “build me a full 3-minute track with five sections” request packs a huge number of socket round-trips into one turn, and on a busy set it stalls. The README says it plainly — complex arrangements may need to be broken into smaller steps. Prompting section by section turned a flaky experience into a dependable one. Treat it like pair-producing, not one-shot generation.

What it can’t do (read before you rely on it)

The boundaries are real and worth knowing up front, so you point it at the right jobs:

• Third-party devices are hit or miss. It’s designed around Ableton’s default devices and browser items. Loading specific VST3 presets or unusual racks can fail — a real, reported issue, not a theoretical one.
• No audio export. There’s no render-to-WAV tool. It builds and controls the set; you export from Live yourself.
• Reading MIDI back out is weak. Pulling the notes out of an existing clip is a requested-but-missing capability, so don’t build a workflow that depends on the agent inspecting what’s already there.
• Complex asks need chunking. Big arrangements time out; break them into steps.
• It’s third-party. Not made by Ableton, and it tracks Live’s scripting surface on a best-effort basis — a new Live version can shift Remote Script paths or behaviour.

Troubleshooting

Who it’s for, and who it isn’t

Use it if: you already produce in Ableton Live, you want a hands-free assistant to scaffold sketches and run small edits by voice or prompt, and you’re comfortable with a one-time Remote Script install and the fact that it’s a desktop-only, two-process setup. It’s a genuinely fun, fast way to get a session started and to learn what an agent can do inside a DAW.

Skip it if: you expected a model that generates finished, mastered audio (this controls Live, it doesn’t render sound), you work primarily with third-party VST chains it can’t reliably load, or you can’t run Claude Desktop / Cursor on the same machine as Live. And if you object on principle to giving an agent control of your DAW and files, that’s a fair line — see the community section.

Community signal

The launch landed loudly. The maintainer’s own demo of building an 80s synthwave track “in just two prompts” (embedded near the top of this post) drew thousands of likes, and producers showed up fast to push it. In r/ClaudeAI, one of the most-shared experiments was simply handing it a brief and letting it run:

In r/ableton, the maintainer’s announcement thread drew the usual mix of “super cool, been playing with it” enthusiasm and concrete friction — the most common reply being some version of “I added the script to my MIDI remote scripts directory but can’t see it,” which is exactly the Control Surface path issue covered above. The pattern across threads is consistent: people love what it does once it’s connected, and the hard part is always the two-part connection, never the music commands.

The contrarian voice is worth taking seriously, because it’s not really about the tool working. In r/beatmakers, a thread titled “Claude AI can control Ableton through MCP (is this the end?)” drew both a security objection and a values one:

Both points are fair and worth holding. The security one is real: this gives an agent control of your DAW, so run it on a project you’d be fine resetting, and save before extensive experimentation (the README’s own advice). The “AI can’t art” point is a taste call, and it lines up with where the tool is actually strong — as a scaffolder and assistant for the mechanical parts (track setup, gain staging, renaming, sketching), leaving the creative decisions to you. Even the skeptic in that thread landed on roughly that: useful for “making things easier,” not for making the art.

The verdict

FAQ

Sources

• Repository & README: github.com/ahujasid/ableton-mcp (MIT-licensed, by Siddharth Ahuja; install, components, capabilities, troubleshooting, telemetry)
• Maintainer launch post: @sidahuj — “Built an MCP that lets Claude talk directly to Ableton”
• Official setup video: “Ableton MCP: Setup instructions” — ahujasid
• Launch demo video: “Ableton MCP Demo: Creating a lush 80s synthwave track”
• Community thread (enthusiast): “Ableton MCP Server” (r/ableton)
• Community thread (skeptical): “Claude AI can control Ableton through MCP (is this the end?)” (r/beatmakers)
• Server detail page on this site: mcp.directory/servers/ableton-live