Guia de Setup Ableton MCP para Claude Code
rustinpartow/ableton-mcp-claude-code-setup
Controle Ableton Live conversando com Claude via MCP Server
Ver no GitHubInstruções completas para integrar o servidor MCP ableton-mcp ao Claude Code no macOS, permitindo controlar Ableton Live (criar tracks, clips, MIDI, ajustar tempo) via conversação. Inclui workaround via AppleScript para contornar restrições de gerenciamento de apps no macOS.
Instalação
npx convez-ai rustinpartow/ableton-mcp-claude-code-setup1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Composição e edição de MIDI orientada por IA
- Prototipagem rápida de arranjos e loops
- Automação de tarefas repetitivas em produção musical
Veredito

Setup técnico bem documentado para um caso niche (Ableton + Claude), mas com etapas críticas de permissões no macOS que exigem atenção. Útil apenas se você trabalha com Ableton Live e quer experimentar IA em composição.
README
A tradução para o português deste README ainda está na fila.
Driving Ableton Live from Claude Code via AbletonMCP
A handoff guide for setting up ahujasid/ableton-mcp as a Model Context Protocol (MCP) server inside Claude Code, so you can build/edit/jam on MIDI in Ableton Live by talking to Claude.
Tested on: macOS 15 (Sequoia), Apple Silicon, Ableton Live 12.1.5 Trial, Claude Code (Opus 4.7).
What you get
Once this is working, Claude Code can:
- Set tempo / time signature
- Create MIDI tracks and load any instrument/sound from Live's browser
- Create clips, write MIDI notes (pitch / start / duration / velocity), name them
- Fire clips, fire scenes, start/stop playback
- Inspect the browser to find specific preset URIs
What it can't do (current state of the tool):
- Set a clip's visual time signature (only
lengthin beats) - Delete notes from a clip or clear a clip (
add_notes_to_cliponly appends) - Add audio effects programmatically with rich configuration
- Save the Live project for you (
Cmd+Sis on you — see below)
Prerequisites
- macOS with Ableton Live 10+ installed (this guide assumes Live 12)
- Claude Code installed (
claudeon your PATH) - Homebrew
brew install uv
uvx is what Claude Code will use to spawn the MCP server on demand.
Step 1 — Install the Live Remote Script (the part that usually breaks)
The README for ableton-mcp lists two install locations. Only one of them works on Live 12. The User Remote Scripts directory (~/Library/Preferences/Ableton/Live X.X.X/User Remote Scripts/) is only for Instant Mappings — Live will silently not list a full Control Surface script placed there. See issue #85.
The script has to live inside the app bundle:
/Applications/Ableton Live <Version>.app/Contents/App-Resources/MIDI Remote Scripts/AbletonMCP/__init__.py
The gotcha: macOS App Management blocks Terminal from writing there
cp from Terminal returns "Operation not permitted" — even with sudo, even via osascript do shell script "..." with administrator privileges. This is the App Management TCC entitlement, not a unix-perms problem. Moving the .app out of /Applications first doesn't help. Stripping the com.apple.provenance xattr requires the same entitlement.
The workaround: use Finder via AppleScript
Finder has the App Management entitlement by default. So we drive Finder to do the copy.
First, download the script to a staging location:
mkdir -p /tmp/ableton-mcp-staging/AbletonMCP
curl -fsSL \
https://raw.githubusercontent.com/ahujasid/ableton-mcp/main/AbletonMCP_Remote_Script/__init__.py \
-o /tmp/ableton-mcp-staging/AbletonMCP/__init__.py
Then find your installed Live version:
defaults read "/Applications/Ableton Live 12 Trial.app/Contents/Info.plist" CFBundleShortVersionString
# → e.g. "12.1.5"
Replace the app name below with whatever you actually have (Ableton Live 12 Suite.app, Ableton Live 12 Standard.app, etc.):
osascript <<'EOF'
set src to POSIX file "/tmp/ableton-mcp-staging/AbletonMCP" as alias
set dst to POSIX file "/Applications/Ableton Live 12 Trial.app/Contents/App-Resources/MIDI Remote Scripts" as alias
tell application "Finder"
duplicate src to dst
end tell
EOF
macOS will prompt for your password the first time. Approve it.
Verify the file landed:
ls -la "/Applications/Ableton Live 12 Trial.app/Contents/App-Resources/MIDI Remote Scripts/AbletonMCP/"
# → should show __init__.py (~45KB)
Activate it in Live
- Fully quit Live (Cmd+Q — not just close the window). Live scans Remote Scripts only at startup.
- Launch Live, open Preferences → Link, Tempo & MIDI.
- Find any unused row in the MIDI section, set Control Surface = AbletonMCP, leave Input / Output = None.
If AbletonMCP doesn't appear in the dropdown, check ~/Library/Preferences/Ableton/Live <Version>/Log.txt for Python errors. If you see none and the file is in the right spot, you probably installed it into the wrong Live version's bundle.
Step 2 — Register the MCP server with Claude Code
claude mcp add AbletonMCP -s user -- uvx ableton-mcp
Verify:
claude mcp list | grep AbletonMCP
# → AbletonMCP: uvx ableton-mcp - ✓ Connected
If it shows "Failed to connect," confirm uvx is on your PATH and that Live is running with AbletonMCP selected as a Control Surface.
Step 3 — Permissions inside Claude Code
This bit will silently bite you if you don't know about it.
If your ~/.claude/settings.json has:
{ "permissions": { "defaultMode": "dontAsk" } }
…then every mcp__AbletonMCP__* tool call will be auto-denied without prompting, and Claude can't even edit settings.json to fix it. You have to allowlist the tools yourself.
In a Claude Code session, type /permissions, then add the rule:
mcp__AbletonMCP__*
Save. Done. You only need to do this once.
(If you're not in dontAsk mode, Claude Code will just prompt you the first time it tries to use each tool. Either way works.)
Step 4 — Restart Claude Code
MCP tools are only loaded at session start. After you've registered the server and granted permissions, /exit and relaunch claude. Then try:
"What tracks are in my Live session right now?"
If it answers with real track data, you're set.
Usage tips that will save you grief
1. Save the Live project immediately, then save again after every meaningful build
The MCP server occasionally drops its socket (Connection reset by peer) under heavy operations like big browser queries. When that happens, Live often snaps back to the last saved state on disk. If your project was unsaved when the drop happened, everything you built is gone — tracks, clips, notes, instrument loads.
Cmd+S in Live the moment you have anything you want to keep. Save again before each big addition. Treat it like committing to git.
2. Build in passes, not in one big plan
Add the bass, fire it, listen, then add the pad, then the texture, then the lead. The fast feedback loop is the whole point — write 4 notes, hear them, adjust. Don't spend a turn pre-designing 8 tracks of dense MIDI.
3. Use scenes for "switch sections"
Live's Session view scenes (clip rows) map perfectly to song sections. Build the main loop in clip-slot 0 of every track. For a breakdown / drop / lift, write alternate clips into slot 1 on only the tracks you want playing during that section — any track with no clip in that row will stop when you fire the scene. You get arrangement variation without writing one giant 4-minute clip.
To fire a whole scene: hit the small triangle at the right end of the scene name in Session view, or the scene Launch column in the master track.
4. add_notes_to_clip appends, doesn't replace
There's no "delete notes" or "clear clip" tool exposed. If you tell Claude "rewrite the bass," what it'll actually do (and what works fine) is write a new version into the next empty slot and fire that clip. Live auto-stops the old slot on the same track.
5. The browser API returns massive JSON
get_browser_items_at_path for sounds/Bass, sounds/Pad, or sounds/Synth Lead is 50–60KB+ per category and exceeds Claude's per-tool-result token cap. Claude Code auto-saves the result to a file under the session's tool-results/ directory and tells you the path. The schema is {"result": "<stringified JSON>"} — process it with jq -r '.result' <file> | python3 ... filtering by keyword (e.g. 'distort', 'punk', 'wave', 'glide'). Don't try to Read it line-by-line; the indentation is meaningless to that approach.
6. Pick presets by vibe in their name
Ableton's stock library has surprisingly evocative preset names. Search them by keyword:
| Vibe | Try keywords |
|---|---|
| Punk / noise rock bass | punk, distortion, dirt, grunge, fuzz, drive |
| Shoegaze pad | vhs, dream, shimmer, vapor, chorus, glass |
| Post-rock strings | slow, roll, cello, feedback bow, mellotron |
| STRFKR-y synth | square glide, vintage phat, sparkle, glide |
| Noise drone | drone, inclement, noise pad, dark |
Confirmed-good preset URIs we've used:
query:Sounds#Bass:FileId_6771— Machine Punk Bassquery:Sounds#Bass:FileId_5406— Basic Sub Sinequery:Sounds#Bass:FileId_6639— Saw Bassquery:Sounds#Pad:FileId_5179— Inclement Drone Padquery:Sounds#Pad:FileId_5216— VHS Dreamsquery:Sounds#Pad:FileId_6903— Vintage Sampler Noise Padquery:Sounds#Strings:FileId_7279— Slow Roll Stringsquery:Sounds#Piano%20&%20Keys:FileId_5117— Music Boxquery:Sounds#Piano%20&%20Keys:FileId_7242— Vibes Softquery:Sounds#Piano%20&%20Keys:FileId_7231— E-Piano MKI Dirtyquery:Sounds#Piano%20&%20Keys:FileId_6563— Clav Electricquery:Sounds#Synth%20Lead:FileId_6933— Square Glide Lead (STRFKR-y)query:Sounds#Synth%20Lead:FileId_6934— Sweep Rhythmic Lead (arp-y)query:Sounds#Synth%20Lead:FileId_4912— Sparkle Lead
(URLs use percent-encoded spaces: Piano%20&%20Keys, Synth%20Lead.)
7. No time-signature setter — fake it with length
create_clip takes length in beats. There's no exposed call to change the clip's displayed time signature. If you want an "8/4 feel," create a clip with length=8 and let the rhythmic phrasing carry the meter; Live's display will still say 4/4 unless you change it manually.
8. Leave space if there's a human player
This goes for any jam scaffold but especially relevant here: drummers will fill in everything you don't. Sparse pad, sparse chimes, sparse leads — let the loop be scaffolding. Post-rock progressions (I-V-vi-IV at 80 BPM, sustained pad + sub bass + a few chime notes per bar) are the easiest to play over.
Troubleshooting checklist
| Symptom | Most likely cause | Fix |
|---|---|---|
AbletonMCP not in Control Surface dropdown | Script in User Remote Scripts dir, not in app bundle | Re-install via the Finder/osascript method above |
| Script in the right place but still no dropdown entry | Live wasn't fully quit before being relaunched | Cmd+Q Live, relaunch |
claude mcp list shows Failed to connect for AbletonMCP | uvx not on PATH, OR Live isn't running with the Control Surface enabled | brew install uv + check Live preferences |
| Every MCP call silently fails with "permission denied in don't ask mode" | defaultMode: "dontAsk" in settings.json | /permissions → add mcp__AbletonMCP__* |
| MCP tools don't show up in a session | Server connected after session start | /exit and relaunch Claude Code |
| Session keeps reverting to a blank project | Connection drop + project was unsaved | Save in Live (Cmd+S) — save before AND after every meaningful step |
Operation not permitted writing into the app bundle | macOS App Management TCC | Use the Finder/osascript trick — don't waste time on sudo |
get_browser_items_at_path "exceeds maximum allowed tokens" | Big category folder | Output was auto-saved to a file — process with jq + python filter |
| Notes you wrote "got added on top of" the old ones | add_notes_to_clip appends | Write the new version into the next clip slot and fire that |
Quick reference: starting a fresh jam
You: set the tempo to 100, make me a punk bass loop in E with math-rock chromatic accents, 8 beats long
You: now add a drone pad in E with a tritone swell — Inclement Drone Pad
You: add a shoegaze chord wash on top, VHS Dreams, Em → G shift
You: now make me a Scene 2 breakdown — same bass but stripped down, kill everything else
Save (Cmd+S in Live) after each one. Fire scenes from Session view to switch sections.
Credits
- Original MCP server: ahujasid/ableton-mcp
- Claude Code: claude.com/claude-code
- Workaround for the bundle-write issue documented here after losing two full sessions to it.