AbletonMCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AbletonMCPCreate a new MIDI track with a piano."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AbletonMCP
Control Ableton Live from Claude Code via the Model Context Protocol (MCP). Create/edit tracks, control plugins (Waves, FabFilter, iZotope, any VST), fire clips, edit MIDI notes, capture audio — all through natural language.
Architecture
Claude Code
↓ MCP Protocol (stdio)
mcp_server/ ← Python MCP server (this project)
↓ HTTP JSON (localhost:9001)
AbletonMCP/ ← Ableton Remote Script (Python, runs inside Ableton)
↓ Live Python API
Ableton LiveRelated MCP server: AbletonMCP
Requirements
Ableton Live 10, 11, or 12 (any edition)
Python 3.11+ (for the MCP server)
Claude Code CLI
Installation
Step 1 — Install the Ableton Remote Script
Copy the AbletonMCP/ folder into Ableton's MIDI Remote Scripts directory:
OS | Path |
Windows |
|
macOS |
|
Result: Remote Scripts/AbletonMCP/__init__.py should exist.
Step 2 — Enable in Ableton
Open Ableton Live
Go to Preferences → Link, Tempo & MIDI
Under Control Surface, select
AbletonMCPin any available slotNo Input/Output device required — leave them as
NoneCheck Ableton's Log file (
Help → Show Log File) and confirm you see:[AbletonMCP] AbletonMCP started on port 9001
Step 3 — Install the MCP Server
cd ableton-mcp
pip install -e .For audio capture support (optional):
pip install -e ".[audio]"Step 4 — Configure Claude Code
Add to your Claude Code MCP config (~/.claude/claude_desktop_config.json or via claude mcp add):
{
"mcpServers": {
"ableton": {
"command": "python",
"args": ["-m", "mcp_server.main"],
"cwd": "/path/to/ableton-mcp"
}
}
}Or using the Claude Code CLI:
claude mcp add ableton python -m mcp_server.main --cwd /path/to/ableton-mcpStep 5 — Verify
In Claude Code, ask:
Get the current Ableton session stateIf Ableton is open with AbletonMCP loaded, you'll see tempo, tracks, etc.
Running Tests
Tests run without Ableton (using a mock bridge server):
pip install -e ".[dev]"
pytest tests/ -vAll 51 tests should pass.
Features & Tools
Session / Transport
Tool | Description |
| Tempo, time signature, playback state, loop settings, track/scene counts |
| Set BPM (60–200) |
| Set numerator and denominator (e.g. 3/4, 7/8) |
| Start playback |
| Stop playback and return to position 0 |
| Continue from current position |
| Toggle session record mode |
| Enable/disable loop with optional start and length in bars |
| Toggle click track |
Mixer (Master)
Tool | Description |
| Master volume, master pan, cue volume, crossfader |
| 0.0 (silent) → 1.0 (0dB) → 1.26 (+2dB) |
| -1.0 (A) → 0.0 (center) → 1.0 (B) |
Tracks
Tool | Description |
| All audio, MIDI, and return tracks |
| Full track details by index |
| Create audio, MIDI, or return track |
| Name, volume, pan, mute, solo, arm, color |
| Remove track permanently |
| Copy track to next position |
| All send levels for a track |
| Set send level to a return track |
Track colors accepted as name strings: red, orange, yellow, green, cyan, blue, purple, pink, white, gray — or as integer Ableton color ID.
Clips
Tool | Description |
| All clip slots for a track (empty and filled) |
| Clip details: name, length, loop points, warp mode |
| Create MIDI clip in a slot with given length |
| Name, loop start/end, looping, warp mode, gain |
| Remove clip from slot |
| Launch clip (equivalent to clicking launch button) |
| Stop playing clip on track |
| All MIDI notes: pitch, start, duration, velocity |
| Add MIDI notes to a clip |
| Remove all notes from a clip |
MIDI note format:
{"pitch": 60, "start": 0.0, "duration": 0.5, "velocity": 100, "mute": false}pitch: MIDI note number (0–127, middle C = 60)start: position in beats from clip startduration: note length in beatsvelocity: 0–127
Devices / Plugins
Works with Ableton native devices (Reverb, Compressor, Operator, Wavetable, etc.) and any installed VST/AU plugin (Waves, FabFilter, iZotope, Native Instruments, Serum, Vital, etc.).
Tool | Description |
| All devices in a track's device chain |
| Device info + all parameters with values and ranges |
| Add device by name (searches Ableton browser) |
| Bypass or enable a device |
| Remove device from chain |
| All parameters: name, value, min, max, display string |
| Set parameter by its index number |
| Set parameter by name (case-insensitive) |
| Load a preset by name from Ableton's browser |
Plugin examples:
add_device(track_index=0, device_name="FabFilter Pro-Q 3")
add_device(track_index=1, device_name="Wave s SSL E-Channel")
add_device(track_index=2, device_name="iZotope Ozone 10")
add_device(track_index=0, device_name="Serum")
add_device(track_index=0, device_name="Compressor") # Ableton nativeParameter editing examples:
set_parameter_by_name(track_index=0, device_index=0, param_name="Threshold", value=-18.0)
set_parameter_by_name(track_index=0, device_index=1, param_name="Band 1 Gain", value=3.0)Scenes
Tool | Description |
| All scenes with name and color |
| Scene details |
| Add new scene |
| Name, color, tempo (per-scene), time signature |
| Remove scene and all its clips |
| Launch all clips in scene row |
Audio
Tool | Description |
| List audio devices (find virtual routing device name) |
| Track signal info: volume, pan, device chain state |
| Export track to WAV (see note below) |
| Begin recording from virtual audio device |
| Stop capture and save WAV; returns RMS, peak, duration |
Audio capture setup (virtual routing):
Install a virtual audio device:
In Ableton, route your master output to the virtual device
Use
get_audio_devicesto find the exact device nameUse
start_audio_capture(device_name="CABLE Output (VB-Audio Virtual Cable)")Play in Ableton
Use
stop_audio_capture(output_path="~/my_recording.wav")to save + analyze
Note on export: Ableton's Python API does not expose the export/render dialog programmatically. The recommended workflow is virtual routing capture or using Ableton's built-in export (File → Export Audio/Video) for offline rendering.
Usage Examples
Natural language in Claude Code
Create a new MIDI track called "Bass" at index 2 with a FabFilter Pro-Q 3 plugin,
then add a 4-bar clip in slot 0 with a C major chord (C4, E4, G4) at beat 0 with duration 2 beats.Set the tempo to 128 BPM, enable the loop from bar 1 to bar 9, then fire scene "Chorus".List all parameters of the Compressor on track 0 and set the threshold to -12 dB and ratio to 6:1.Duplicate track 1, mute the original, and add a Waves SSL E-Channel to the duplicate.Project Structure
ableton-mcp/
├── AbletonMCP/ # Ableton Remote Script (install in Ableton)
│ ├── __init__.py # Entry point, create_instance()
│ ├── bridge_server.py # HTTP server thread (port 9001)
│ ├── api_handler.py # URL routing
│ └── live_api/
│ ├── session.py # Transport, tempo, loop, mixer
│ ├── tracks.py # Track CRUD, sends
│ ├── clips.py # Clip + MIDI note management
│ ├── devices.py # Plugin add/remove/parameter control
│ ├── scenes.py # Scene management
│ └── audio.py # Audio capture via virtual routing
├── mcp_server/ # MCP Server (Claude talks to this)
│ ├── main.py # Server entry point
│ ├── bridge_client.py # HTTP client to AbletonMCP
│ └── tools/
│ ├── session_tools.py
│ ├── track_tools.py
│ ├── clip_tools.py
│ ├── device_tools.py
│ ├── scene_tools.py
│ └── audio_tools.py
├── tests/
│ ├── mock_bridge/server.py # Simulates Ableton for offline testing
│ ├── conftest.py
│ ├── test_session.py
│ ├── test_tracks.py
│ ├── test_clips.py
│ ├── test_devices.py
│ └── test_scenes.py
└── pyproject.tomlTroubleshooting
"Cannot connect to Ableton bridge at localhost:9001"
Confirm AbletonMCP is selected in Ableton Preferences → Control Surfaces
Check Ableton's log file for
[AbletonMCP] started on port 9001Make sure no firewall blocks localhost:9001
Plugin not found when using add_device
Plugin must be installed and scanned by Ableton (Preferences → Plug-Ins)
Use the exact name as it appears in Ableton's browser
VST3 plugins are preferred over VST2 when both are installed
"Parameter X not found"
Use
get_deviceorlist_parametersfirst to see exact parameter namesParameter names are case-insensitive but must otherwise match exactly
Tests fail
Run
pip install -e ".[dev]"firstTests do not require Ableton — they use a mock bridge server
Ensure port 9002 is free (used by mock server during testing)
Known Limitations
Device reordering: Ableton's Python API does not support moving devices within a chain. Delete and re-add in desired order.
Direct WAV export: Ableton's API cannot trigger the export dialog programmatically. Use virtual routing capture or Ableton's built-in export.
Return track deletion: Not supported via API (Ableton limitation).
Audio clips: MIDI note editing only applies to MIDI clips. Audio clips support loop/warp settings only.
Plugin browser search: Uses Ableton's browser tree traversal. Very large plugin collections may be slow to search on first use.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/juampicosta/ableton-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server