Open-source music production connector

Ableton Live MCP

Inspect, arrange, and produce inside Ableton Live from an MCP-compatible AI client, with local-only transport, explicit risk tiers, and evidence before broad changes.

Install 0.1.0 View source

A classical music arrangement with piano, violin, guitar, and flute tracks connected to a local production workflow — One local path from an MCP client to a reviewable Ableton Live session.

Release: 0.1.0
License: MIT
Transport: Local stdio + HTTP
Target: Ableton Live 11 / 12

System boundary

Local by design

The public MCP process never embeds itself in Live. A small Remote Script adapter translates local HTTP requests into Live API operations and keeps DAW-specific logic behind focused helpers.

MCP clientTool request
Node serverstdio + policy
HTTP bridge127.0.0.1:9789
Remote ScriptLive API adapter
Ableton LiveOpen set

Production surface

Tools for the full session

The connector exposes inspection and controlled writes across arrangement, MIDI, devices, routing, mixer state, snapshots, and production diagnostics.

Arrangement & MIDI

Create tracks and clips, import MIDI, edit notes, quantize, humanize, apply grooves, and add locators.

Mixer & routing

Inspect and change track, return, and master controls with explicit dB, pan, send, and routing contracts.

Devices & plugins

Search Live's indexed browser, load instruments and effects, inspect parameters, and automate exposed controls.

Safety & recovery

Classify action risk, create snapshots, verify writes, report unsupported operations, and roll back covered state.

Production analysis

Inspect the project and arrangement, diagnose playback and plugins, and analyze current rendered WAV files locally.

Observable workflows

Use production reports, endpoint support, bridge health, and workflow plans to decide what is safe before writing.

Quick start

Install the connector

Install the package, copy the bundled Remote Script, select it in Live, then add the stdio server to your MCP client.

Step 1

Check the package

npx -y @jterrats/ableton-live-mcp --help

Step 2

Install the Remote Script

npx -y @jterrats/ableton-live-mcp install-remote-script \
  --app-path "/Applications/Ableton Live 12.app"

Step 3

Configure your MCP client

{
  "mcpServers": {
    "ableton-live": {
      "command": "npx",
      "args": ["-y", "@jterrats/ableton-live-mcp"],
      "env": {
        "ABLETON_BRIDGE_URL": "http://127.0.0.1:9789"
      }
    }
  }
}

Restart Live and select AbletonMcpBridge under Settings → Link, Tempo & MIDI. The bridge listens on loopback only.

Operating model

Automation should remain reviewable

Read first. Snapshot before broad writes. Verify the value Live reports after each change. Stop when the active bridge marks a capability unreliable or unsupported.

ReadProject, arrangement, devices, routing, and diagnostics.
Safe writeScoped changes with observed post-write values.
DestructiveDelete, flatten, and rollback require explicit intent.
ExportSeparate approval and bridge capability checks.

Current boundaries

What 0.1.0 does not hide

Capabilities depend on what Ableton Live exposes to the active Remote Script and what the installed edition indexes.

Render and bounceThe Python Remote Script returns explicit unsupported responses; it does not simulate an audio export.
Live metersTelemetry is marked unreliable for mixing when Live returns zero-only values during audible playback.
Plugin discoveryResults come from Live's browser index, so system plugins must be enabled and scanned in Live first.
Snapshot coverageSnapshots document coverage and limitations; they are not a replacement for saving or duplicating the .als set.
macOS installationWriting inside the Live application may require App Management permission or an elevated installer command.

Build in the open

A production connector you can inspect.

Read the implementation, report a bridge mismatch, or help extend the Live adapter.

Explore the repository Open an issue