A high-density, low-latency MCP server that exposes active Ableton Live 12 Sets to AI agents and Python scripts. Query live LOM parameters, drive transport, automate clips, analyze audio in non-realtime, and execute atomic transactions.
`ableton-mcp-server` runs locally over stdio IPC. It exposes 65 typed tool contracts directly to LLM agent runtimes with write verification, transaction rollbacks, and explicit error taxonomies.
Every parameter mutation (`set_parameter_value`, `set_track_property`) executes a write-then-verify loop inside Live's main thread tick before confirming completion to the agent.
Agents bundle multi-step operations into atomic `run_batch` payloads. Partial failures trigger explicit rollback reporting.
Four standalone mix analysis tools process audio files offline (LUFS-I, True Peak, spectral collisions) without requiring active playback.
Inject this system prompt fragment into your agent runtime to enforce deterministic interaction patterns against `ableton-mcp-server`:
You are connected to an active Ableton Live 12 Set via ableton-mcp-server (65 tools).
Operational rules:
1. Always inspect live set topology first via `get_session_overview()` or `get_track_list()`.
2. Resolve target tracks by index or via fuzzy name matching (`live_find_track`).
3. Query device parameters via `get_device_list()` and `get_parameter_value()` before mutating values with `set_parameter_value()`.
4. Bundle multi-step modifications into `run_batch(operations)` for atomic execution with rollback protection.
5. If an error envelope returns `AMBIGUOUS_MATCH` or `VERIFICATION_FAILED`, inspect the track/device index and retry with precise targets.High-efficiency separation between high-frequency LOM transport/device control and async WebSocket extension routines.
Low-latency python control surface operating inside Ableton Live's main thread looper. Handles high-frequency parameter mutations, transport commands, clip creation, scene firing, and LOM introspection.
Asynchronous WebSocket extension bridge handling complex operations: browser search and device loading, clip warping state, live fade clocking, and batch transaction rollbacks.
Copy-paste server launch configurations for MCP client environments (Claude Desktop, Antigravity IDE, Cursor, Windsurf).
{
"mcpServers": {
"ableton": {
"command": "C:\\path\\to\\ableton-mcp-server\\.venv-win\\Scripts\\ableton-mcp-server.exe",
"args": []
}
}
}Deterministic error codes returned when a command cannot be executed, enabling LLM agent runtimes to inspect and self-correct plans.
Returned when attempting an operation not supported by the connected Live version or missing extension bridge (e.g. calling warping on an unwarped audio clip).
Returned when a fuzzy track or device lookup matches multiple targets without sufficient specificity. Agent must supply exact index or full name.
Returned by the per-tick write-then-verify loop when a parameter write does not match the readback value from Live's object model after execution.
Returned when running destructive operations against an active production project instead of a disposable test Set (e.g. TESTE_CODEX).
`ableton-mcp-server` builds on design insights from open-source Ableton control surfaces and OSC bridges. Direct attribution:
Pioneered the TCP JSONL Remote Script protocol layout, typed error envelope structure, and per-tick write-then-verify loop discipline.
github.com/pnomolos/live-wire →Inspired the grouped `run_batch` transaction semantics with explicit `rolled_back: false` on partial failure.
github.com/hidingwill/AbletonBridge →De-facto reference for exposing the Live Object Model over OSC conventions used by the Extension Host bridge.
github.com/ideoforms/AbletonOSC →Influenced the tool boundary decision: keeping transport, clips, tracks, and devices on Remote Script while routing warping/loading through WebSockets.
github.com/Simon-Kansara/ableton-live-mcp-server →Typed parameter signatures and descriptions for all 65 tools exposed to AI agents. Search by name, category, or parameter signature.