AbletonMCPGitHub
Menu

Your AI assistant. Connected to
Ableton Live.

Write MIDI, work with devices and explore your set through Claude, Cursor or Codex. 156 typed tools, connected to Live on your computer.

Install AbletonMCP What can I ask it to do?

“Sketch a bassline.”

Your assistant chooses the tools
AbletonMCPExecutes the tool calls in Live
Read the setCreate a clipEdit notes
Inside your Live set
156
Typed, validated tools
Live 11 + 12
Supported versions
Local bridge
No AbletonMCP cloud relay
Open source
Free · MIT licensed

Start with an idea.
Or a job you keep putting off.

These are example requests for your connected AI client. Follow the tool links to see exactly what each operation can do.

Session and transport

“Set the tempo to 124 BPM, then launch the next scene.”

See all tool categories

Connect it once.
Use it in your own set.

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.

Live 11 or 12macOS or WindowsPython 3.10+uv

Follow the four steps here. Commands, client configuration and connection help are included; there’s no need to switch to a separate guide.

Make the connection.

v1.8.1

Every step, right here. Open the part you need.

1Install the Remote Script

Have Live 11 or 12 on macOS or Windows, plus a local MCP client on the same computer. You’ll need uv and Python 3.10 or newer.

Run this in Terminal or PowerShell to copy the matching Remote Script into your Ableton User Library:

uvx mcp-server-ableton-live@1.8.1 install

If the installer finds existing files, review them before using --replace.

I don’t have uv or Python yet

Install uv with the command for your computer. The standalone installers download and run Astral’s installation script.

macOS with Homebrew

brew install uv

macOS without Homebrew

curl -LsSf https://astral.sh/uv/install.sh | sh

Windows · PowerShell

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Close and reopen your terminal after installation. uv can download a compatible Python automatically when needed; then run the Remote Script command above.

Reference: Astral’s uv installation instructions.

2Restart Live and activate

Restart Ableton Live. Open Settings → Tempo & MIDI → MIDI. In the Control Surface list, use an unused row:

Control Surface
AbletonMCP
Input
None
Output
None

Keep your hardware controller rows unchanged. Selecting AbletonMCP is required to start the bridge; installing the files alone is not enough.

In older Live versions, find MIDI under Link, Tempo & MIDI or Link/MIDI in Settings/Preferences. In current versions, Link is a separate page.

3Add your MCP client

Choose your local client. Keep existing MCP connections and use the same package version as the Remote Script.

Connect Codex

With the Codex CLI installed, run this in your terminal to add the local stdio server:

codex mcp add ableton -- uvx mcp-server-ableton-live@1.8.1

Start a new local Codex session.

Connect Claude Code

With Claude Code installed, run this in your terminal to add the local stdio server:

claude mcp add --scope user AbletonMCP -- uvx mcp-server-ableton-live@1.8.1

Run claude mcp list, then start a new Claude Code session.

Connect Claude Desktop

In Claude Desktop, open Settings → Developer → Edit Config to open claude_desktop_config.json.

Add the AbletonMCP entry inside your existing mcpServers object and keep other servers and settings. If the file is empty, paste the full configuration below.

{
  "mcpServers": {
    "AbletonMCP": {
      "command": "uvx",
      "args": [
        "mcp-server-ableton-live@1.8.1"
      ]
    }
  }
}

Save the file, fully quit Claude Desktop, then reopen it.

Connect Cursor

Open or create ~/.cursor/mcp.json for all projects, or .cursor/mcp.json in your project.

Add the AbletonMCP entry inside your existing mcpServers object and keep other servers and settings. If the file is empty, paste the full configuration below.

{
  "mcpServers": {
    "AbletonMCP": {
      "command": "uvx",
      "args": [
        "mcp-server-ableton-live@1.8.1"
      ]
    }
  }
}

Save the file, then restart Cursor.

Connect Other

In your client’s MCP settings, add a local server named AbletonMCP. Enter these fields; don’t add the install subcommand.

Command: uvx
Argument: mcp-server-ableton-live@1.8.1
Transport: stdio

Add a local MCP server named AbletonMCP, then restart your client.

4Verify without editing

With Live running and AbletonMCP selected as its Control Surface, run this in your terminal:

uvx mcp-server-ableton-live@1.8.1 doctor --json

Look for "ok": true in the output. It means the installed script matches this package and Live responded with the matching bridge. Then test your client’s connection with this read-only request:

Tell me the current tempo and track names in Ableton Live. Do not change the set or start playback.

Check that the returned tempo and track names match your open Live set. This page cannot confirm either check. Save your set before asking for edits.

Something doesn’t connect
“uvx” isn’t found
Open step 1 for uv installation. Reopen your terminal and restart your MCP client after installing it.
AbletonMCP is missing in Live
Rerun the install command, confirm it targets your User Library, and restart Live. For a custom location, append --user-library "/path/to/User Library". Review existing files before using --replace.
Doctor fails or Live doesn’t respond
Keep Live open, check the Control Surface row in step 2, dismiss any open Live dialog, then run doctor again.
Doctor passes, but your client has no tools
Recheck the command or configuration in step 3, preserve existing entries, then fully restart the client or start a new session.

Need a hand? Requirements and connection help open inside the steps above.

Work in Live.
Or open a saved project.

Build and perform in real time, or inspect saved projects without launching Ableton Live. Both workflows use the same local server.

Shape the set while it plays.

Create tracks and clips, write MIDI, load devices, control the mixer, arrange sections and record automation through Live's own API.

Explore live tools

Understand projects without opening Live.

Summarize, lint and diff saved .als files, extract MIDI, inspect mixer state and analyze .adg or .adv racks offline.

Explore the offline workflow

Before you connect.

Short answers about compatibility, privacy, clients, and offline project analysis.

Is AbletonMCP free?

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.

What is AbletonMCP?

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.

What can it control in Ableton Live?

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.

Does AbletonMCP upload my Live set?

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.

Which MCP clients work?

Any client that can launch a local stdio MCP server can use it, including Claude Desktop, Claude Code, Cursor, Codex, and compatible development tools.

Does it work while Ableton Live is closed?

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.

Connect AbletonMCP to Live.

Install the published package, add the bundled Remote Script, and verify the local connection.

Install AbletonMCP