Installation guide

Connect your MCP client to Ableton Live.

The Ableton bridge runs locally with no project-operated cloud service. Your MCP client's own data policy still applies. Follow the steps below for Ableton Live 11 or 12.

macOSWindowsPython 3.10+uv

Requirements

You need Ableton Live 11 or 12, Python 3.10 or newer, and uv.

Install uv on macOS

brew install uv

On Windows or for alternative installers, follow the official uv installation guide. You do not need to clone the repository or create a virtual environment.

Compatibility note

Most tools support Live 11 and 12. Creating audio clips through the Live API requires Ableton Live 12.0.5 or newer.

Register the MCP server

Claude Code

Terminal
claude mcp add AbletonMCP -s user -- uvx mcp-server-ableton-live

Claude Desktop, Cursor and compatible clients

Add this entry inside the client's mcpServers configuration object:

{
  "mcpServers": {
    "AbletonMCP": {
      "command": "uvx",
      "args": ["mcp-server-ableton-live"]
    }
  }
}
Do not add install to the MCP configuration.

The install subcommand copies the Remote Script and exits. The client must run uvx mcp-server-ableton-live without a subcommand.

Install the Remote Script

The package contains the matching Live-side script. Run the installer during initial setup, and again after upgrading the package so the Remote Script stays version-matched:

Terminal
uvx mcp-server-ableton-live install
  1. Restart Ableton Live after the command completes.
  2. Open Settings → Link, Tempo & MIDI.
  3. Choose AbletonMCP under Control Surface.
  4. Leave Input and Output set to None.

Live scans Remote Scripts at startup, so a restart is required after installing or updating the script.

Verify the setup

With Ableton Live running and AbletonMCP selected as the Control Surface, run:

Terminal
uvx mcp-server-ableton-live doctor

The doctor checks that the Remote Script is present in the default User Library path and that Ableton Live answers over the local socket.

[ok] Remote Script installed in the User Library
[ok] Remote Script reachable on 127.0.0.1:9877

All good.

Then ask your MCP client something small, such as:

Tell me the current tempo and list the tracks in my Live set.

Troubleshooting

AbletonMCP is missing from Control Surface

The folder must be named exactly AbletonMCP. Restart Live after installation because scripts are only scanned during startup.

Every command times out

Dismiss any open modal dialog in Live. Startup, trial and save dialogs can block the Remote Script until they are closed.

Port 9877 is not listening

Confirm Live is running and AbletonMCP is selected. If the port is already occupied, configure matching ABLETON_MCP_PORT and ABLETON_PORT values.

Export and freeze are unavailable

Live's control-surface API does not expose render or freeze operations. Use Live's normal export workflow for final renders.

Security

The Remote Script listens on 127.0.0.1:9877 without authentication. Loopback binding means only local processes can connect by default. Do not expose or forward this port to a public network.

AbletonMCP does not operate a cloud relay. Your MCP client or model provider may still process tool requests and results under its own configuration and privacy terms.

For implementation details and reporting instructions, see the project's security policy.