Ableton Live 12 MCP Server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Ableton Live 12 MCP Server
Let Claude (or any MCP client) produce music in Ableton Live 12: write drums, basslines, chords and melodies; build song sections and full arrangements; edit clips; mix; master; analyse audio; and make sample packs.
It has two parts:
Claude ⇄ (MCP, stdio) ⇄ ableton-live-mcp (Python) ⇄ (JSON over TCP 127.0.0.1:9877) ⇄ AbletonMCP Remote Script (inside Live)What it can do (≈110 tools)
Area | Tools |
Session & transport |
|
Tracks & routing |
|
Clips & MIDI |
|
Composition |
|
Arrangement |
|
Devices & browser |
|
Mixing |
|
Mastering |
|
Analysis |
|
Sample packs |
|
Escape hatch |
|
Related MCP server: ableton-mcp
Install
1. Remote Script (inside Live)
Run python install_remote_script.py, or copy the folder remote_script/AbletonMCP to your User Library's Remote Scripts folder (create the folder if it does not exist):
macOS:
~/Music/Ableton/User Library/Remote Scripts/AbletonMCPWindows:
%USERPROFILE%\Documents\Ableton\User Library\Remote Scripts\AbletonMCP
Restart Live, then go to Settings → Link, Tempo & MIDI → Control Surface and choose AbletonMCP (leave Input/Output as None). Live's status bar shows "AbletonMCP: listening on port 9877".
2. MCP server (Python 3.10+)
cd ableton-live-mcp
pip install -e ".[analysis]" # core + audio analysis
pip install -e ".[analysis,stems]" # + Demucs stem separation (large, pulls PyTorch)Or with uv: uv pip install -e ".[analysis]".
3. Connect your MCP client
Claude Desktop — add this to claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"ableton-live": {
"command": "/full/path/to/python",
"args": ["-m", "ableton_mcp"]
}
}
}Use the Python that you installed the package into (which python / where python). With uv you can instead use "command": "uv", "args": ["--directory", "/path/to/ableton-live-mcp", "run", "ableton-live-mcp"].
Claude Code: claude mcp add ableton-live -- python -m ableton_mcp
Restart the client and ask: "Check the Ableton connection."
Example prompts
"Make a 124 BPM deep house idea in F minor: drums, a syncopated bass, Rhodes-style chords and a sparse lead."
"Build a full techno track in A minor and lay it out in the arrangement with locators."
"Humanize the hats by 6 ms and ±12 velocity, then quantize the chords to 1/16 at 70% with a bit of swing."
"Create a breakdown and a build with a filter sweep, then try two different arrangement structures."
"Sidechain the bass and pads to the kick, high-pass everything except kick and bass at 150 Hz, and set up reverb and delay sends."
"Put a loud master chain on. I exported the mix to ~/Desktop/mix.wav — get it to −8 LUFS and compare it to ~/Music/ref.wav."
"Scan ~/Samples for loops in A minor or compatible keys between 120–128 BPM and find the ones that fit my current mix best."
"Show me the spectrogram of the vocal clip on track 3."
"Make a sample pack from ~/Music/my_song.wav."
Notes and limits
Live versions: built for Live 12.
insert_deviceuses Live 12.3+'sinsert_device, falling back to the browser on older 12.x. Arrangement MIDI clips need 12.1.10+. Everything else works on any Live 12 (most of it also on Live 11).Audio export: Live's API cannot render audio. Loudness, reference and stem tools work on files you export (File → Export Audio/Video).
Meters:
measure_levels/balance_levelsuse Live's meter scale (not exact dB), so treat them as relative balancing.Sidechain: routing is set automatically where Live exposes Compressor sidechain routing; otherwise the tool tells you which source to pick.
Plugins: third-party plugin parameters are visible once Live exposes them (click "Configure" on the plugin for more).
Pack maker: use it only on audio you have the rights to. Without Demucs, loops are cut from the full mix.
Port: set
ABLETON_MCP_PORT(in the environment Live and the server see) to change it from 9877.Logs: Live's
Log.txt(Preferences folder) contains Remote Script errors.
Development
pip install -e ".[analysis,dev]"
pytest tests # runs the full stack against a fake Live object modelTool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Create, co-edit, analyze, publish, and export collaborative step-sequencer sessions through MCP.
MCP server for Producer/Riffusion AI music generation
Compose, mix, master and export in Logic Pro, REAPER or Ableton Live by talking to an AI engineer.
Remote MCP server for audio stem separation, denoise, reverb, and MIDI export.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to programmatically edit, analyze, and export audio projects through MCP tools, including multi-track editing, effects, transcription, and semantic search.1-
- AlicenseBqualityCmaintenanceEnables AI assistants to control Ableton Live through MCP, allowing MIDI writing, audio import, device parameter adjustment, clip arrangement, and playback control over a localhost-only connection.37MIT
- AlicenseBqualityBmaintenanceEnables Claude or any MCP client to produce full tracks in Ableton Live from chat: building tracks, writing MIDI notes, loading and tweaking device parameters, arranging sections, and drawing real clip and Arrangement automation. It also exposes mixer state snapshots and clip editing so a live set can be inspected and reshaped end to end.43MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform deterministic, sample-accurate music production, DJ mixing, audio editing, stem separation, and loudness mastering through non-destructive timeline operations and structured MCP tools.Mozilla Public 2.0