ableton-live-mcp
This server is an MCP bridge for inspecting, controlling, and automating Ableton Live via a local HTTP connection. It can:
Read project state: transport, session, arrangement timeline, tracks, clips, devices, routing, locators, meters, returns, buses, and production reports.
Control transport and project settings: start/stop playback, set tempo/time signature, save project, create/rollback snapshots.
Manage tracks and clips: create, duplicate, modify, freeze, flatten tracks; create/edit/delete/consolidate/launch/humanize/quantize/apply groove to MIDI clips; import MIDI; insert arrangement clips; add locators.
Manage devices and plugins: search browser, list installed plugins/VSTs/AUs, match presets/plugins to musical intent; load instruments/effects/racks/presets onto tracks, returns, or master; set/reorder/delete devices and set device parameters.
Mix and master: modify mixer state (volume, pan, mute/solo/arm, sends, routing), manage return tracks/buses/master channel; apply mastering chains; run render-analyze-adjust mastering loops; analyze rendered audio and full mixes for LUFS, peak, RMS, clipping, dynamics.
Export and bounce: export master, selected tracks, all tracks, or stems with configurable sample rate, bit depth, and normalization; bounce tracks/audio for review.
Automate: write automation points for mixer, device, or tempo targets.
Diagnose and plan: diagnose playback/plugin issues, get bridge observability, evaluate action risk, list risk policies, and list production workflow plans.
Click on "Deploy 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., "@ableton-live-mcp Analyze the current mix"
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.
Ableton Live MCP
Local MCP stdio server for inspecting and controlling Ableton Live through a local bridge.
Current package version: 0.2.1.
Product site: ableton-mcp.jterrats.dev
This repo does not assume a specific Ableton integration layer. The MCP server speaks JSON-RPC over stdio to an MCP client, then forwards tool calls to a local HTTP bridge that you can implement with Max for Live, Ableton's Extensions SDK, a Python Remote Script helper, or another Live automation layer.
Product Workflows
Start with docs/product-workflows.md for end-to-end setup, MIDI import, instrument assignment, arrangement, mixing, mastering, validation, and export workflows. The guide also documents safe operating rules for open user sets, destructive commands, explicit export approval, and unsupported bridge operations.
Related MCP server: ableton-mind
Tools
The exact tools/list response is capability-aware. It reads the active
bridge's read-only GET /capabilities contract, hides hard-unsupported bridge
actions, keeps MCP-local analysis/risk/workflow tools, and labels
target-dependent tools Conditional. Clients should re-list tools after
reconnecting or changing bridges. An unavailable or malformed handshake fails
closed and does not advertise unverified Live writes.
Read and inspect:
ableton_get_statusableton_get_projectableton_get_arrangementableton_get_scene_tempo_signature_capabilitiesableton_list_pluginsableton_search_browserableton_diagnose_pluginsableton_get_production_reportableton_diagnose_playbackableton_get_metersableton_list_returnsableton_list_busesableton_get_clip_notesableton_launch_clipableton_launch_sceneableton_get_device_parametersableton_analyze_audioableton_analyze_mixableton_get_bridge_observabilityableton_evaluate_action_riskableton_list_risk_policyableton_match_preset_intentableton_list_workflow_plansableton_get_workflow_plan
Project, transport, track, and clip editing:
ableton_create_snapshotableton_rollback_snapshotableton_set_tempoableton_set_signatureableton_set_scene_tempo_signature_overridesableton_start_transportableton_stop_transportableton_create_midi_trackableton_duplicate_trackableton_freeze_trackableton_flatten_trackableton_modify_trackableton_create_midi_clipableton_consolidate_clipableton_delete_clipableton_humanize_clipableton_quantize_clipableton_apply_grooveableton_import_midi
Devices, routing, returns, arrangement, mastering, and export:
ableton_load_deviceableton_load_master_deviceableton_select_vst_for_midiableton_set_device_parameterableton_reorder_deviceableton_delete_deviceableton_set_automationableton_create_return_trackableton_modify_returnableton_delete_return_trackableton_modify_masterableton_apply_mastering_chainableton_analyze_and_apply_masteringableton_export_renderableton_bounce_tracksableton_insert_arrangement_clipableton_add_locator
Production Workflow
For meaningful LLM control, the recommended sequence is:
ableton_get_status,ableton_get_project,ableton_get_arrangement, andableton_get_production_reportto inspect transport, tracks, devices, clips, locators, routing, meters, returns, and mixer state.ableton_create_snapshotbefore broad edits. For real user sets, also save or duplicate the.alsfile before destructive, export, or mastering work.ableton_list_pluginsandableton_search_browserso the LLM can choose available instruments, effects, presets, samples, racks, grooves, plugins, and Max devices. Useableton_match_preset_intentfirst when the request is musical, such as realistic violin, concert piano, classical guitar, flute, or concert hall mastering.ableton_import_midi,ableton_create_midi_clip, or both.ableton_humanize_clip,ableton_quantize_clip, orableton_apply_groovefor controlled MIDI timing edits.ableton_select_vst_for_midi,ableton_load_device, orableton_load_master_deviceto assign sounds and processing.ableton_duplicate_track,ableton_consolidate_clip,ableton_insert_arrangement_clip,ableton_add_locator,ableton_modify_track,ableton_modify_return,ableton_modify_master,ableton_set_device_parameter, andableton_set_automationfor arrangement and mix moves.ableton_freeze_trackandableton_flatten_trackwhen committing tracks to audio is supported by the active bridge.ableton_apply_mastering_chainfor master bus preparation.ableton_export_render,ableton_bounce_tracks, andableton_analyze_audio, andableton_analyze_mixfor approved export, stem, and audio-validation workflows. File analysis runs locally in the MCP process and does not depend on Ableton's Remote Script meters.
Risk tiers and default blocking recommendations are documented in
docs/risk-policy.md and exposed through
ableton_evaluate_action_risk and ableton_list_risk_policy. High-level
plan-only workflows are exposed through ableton_list_workflow_plans and
ableton_get_workflow_plan. Render/export support is documented in
docs/render-export-plan.md; the current Python
Remote Script bridge returns explicit 501 unsupported responses for
render-backed routes instead of simulating Live renders.
Quick Start
From npm:
npx -y @jterrats/ableton-live-mcp --helpInstall the bundled Ableton Remote Script:
npx -y @jterrats/ableton-live-mcp install-remote-script --app-path "/Applications/Ableton Live 12 Lite.app"Then restart Ableton Live, select AbletonMcpBridge in Preferences -> Link,
Tempo & MIDI, and verify the installation:
npx -y @jterrats/ableton-live-mcp doctor --app-path "/Applications/Ableton Live 12 Lite.app"Run the MCP stdio server:
npx -y @jterrats/ableton-live-mcpLocal development from this repo:
npm run smokeRun the server:
npm startRun the deterministic local development bridge:
npm run bridgeFor dry-run development without Ableton:
ABLETON_MCP_DRY_RUN=1 npm startMCP Client Config
Use this shape in an MCP client that supports stdio servers:
{
"mcpServers": {
"ableton-live": {
"command": "npx",
"args": ["-y", "@jterrats/ableton-live-mcp"],
"env": {
"ABLETON_BRIDGE_URL": "http://127.0.0.1:9789"
}
}
}
}Set ABLETON_MCP_DRY_RUN=1 in env when you want the tools to return the
intended bridge calls without touching Ableton.
Bridge
The local bridge must listen on ABLETON_BRIDGE_URL and implement the HTTP
contract in docs/ableton-bridge-contract.md.
This repo includes a deterministic development bridge for local MCP integration
tests. It listens on 127.0.0.1:9789 by default, or on ABLETON_BRIDGE_PORT
when configured, and implements the product workflow surface without requiring
Ableton Live.
For the real Ableton Live adapter, install the Python Remote Script documented
in docs/ableton-python-remote-script.md.
That script runs inside Ableton and exposes the same bridge endpoints on
127.0.0.1:9789.
On this machine Ableton Live Lite and Suite were detected. Install the bundled Remote Script into the edition you actually launch, for example Suite:
npx -y @jterrats/ableton-live-mcp install-remote-script --app-path "/Applications/Ableton Live 12 Suite.app"If macOS rejects writes to /Applications with Operation not permitted, close
Ableton and retry with sudo -E npx -y @jterrats/ableton-live-mcp install-remote-script --app-path "/Applications/Ableton Live 12 Suite.app".
If sudo is still blocked, grant App Management or Full Disk Access to your
terminal app in System Settings -> Privacy & Security, then rerun the installer.
Finder manual copy with authentication is also valid.
Release readiness checks are documented in docs/release-checklist.md.
Edition detection, Lite/Intro capacity guards, and Standard/Suite behavior are documented in docs/ableton-editions.md.
Keep the bridge local-only. Do not bind it to a public network interface unless you add authentication and understand the risk of remote DAW control.
Available Tools
59 toolsableton_add_locatorC
Add or update an arrangement locator/marker.
Inputs: beat (required), name (required).
ableton_analyze_and_apply_masteringC
Render, analyze, and apply deterministic mastering adjustments to the master chain.
Inputs: targetLufs (required), truePeakDb (required), chain, bitDepth, +4 more.
ableton_analyze_audioA
Analyze a rendered audio file for LUFS, true peak, RMS, crest factor, and clipping.
Inputs: path (required).
ableton_analyze_mixB
Analyze a rendered master and optional stems using verified offline audio measurements.
Inputs: masterPath (required), stems.
ableton_apply_grooveC
Apply a measurable swing groove to MIDI note start times in an existing editable clip.
Inputs: amount (required), trackIndex (required), clipSlotIndex (required), grid, +1 more.
ableton_apply_mastering_chainC
Apply or update a mastering chain on the master channel.
Inputs: mode, chain, style, targetLufs, +2 more.
ableton_bounce_tracksC
Bounce selected tracks or stems into audio artifacts for production review.
Inputs: outputPath (required), scope, bitDepth, normalize, +5 more.
ableton_consolidate_clipC
Consolidate a beat range on a track into a new clip where the bridge supports it.
Inputs: startBeat (required), trackIndex (required), lengthBeats (required), name, +1 more.
ableton_create_midi_clipC
Create or replace a MIDI clip with note events.
Inputs: notes (required), trackIndex (required), lengthBeats (required), clipSlotIndex (required).
ableton_create_midi_trackB
Create a MIDI track in Ableton Live.
Inputs: name, color.
ableton_create_return_trackC
Create an Ableton return track.
Inputs: name (required), returnIndex.
ableton_create_snapshotB
Save a project snapshot before broad edits.
Inputs: label (required).
ableton_delete_clipC
Delete a clip from an Ableton Live track slot.
Inputs: trackIndex (required), clipSlotIndex (required).
ableton_delete_deviceC
Delete a device from a track, return, or master device chain.
Inputs: location (required), deviceIndex (required).
ableton_delete_return_trackB
Delete an Ableton return track.
Inputs: returnIndex (required).
ableton_diagnose_playbackA
Diagnose silent playback from transport, Session clips, Arrangement clips, meters, routing, mute, and solo state.
Inputs: no named parameters.
ableton_diagnose_pluginsA
Compare plugins installed on disk against Ableton's indexed plugin/browser results and recommend rescan actions.
Inputs: query, queries, pluginDirectories, includeDefaultDirectories.
ableton_duplicate_trackC
Duplicate an existing Ableton Live track and return the new track index.
Inputs: trackIndex (required), name.
ableton_evaluate_action_riskB
Evaluate the risk tier and approval recommendation for a tool or HTTP endpoint.
Inputs: path, route, method, toolName.
ableton_export_renderC
Export a master render, selected tracks, all tracks, or stems.
Inputs: scope (required), outputPath (required), bitDepth, normalize, +5 more.
ableton_flatten_trackC
Flatten a frozen Ableton Live track to audio when the bridge exposes a real flatten operation.
Inputs: trackIndex (required).
ableton_freeze_trackD
Freeze an Ableton Live track when the bridge exposes a real freeze operation.
Inputs: trackIndex (required).
ableton_get_arrangementB
Read arrangement timeline clips, locators, song length, and derived sections.
Inputs: no named parameters.
ableton_get_bridge_observabilityB
Read local bridge version, endpoint support, stale-runtime, and installed-file diagnostics.
Inputs: livePid, lastError, runtimeStartedAt, installedFilePaths.
ableton_get_clip_notesC
Read MIDI notes from an existing Ableton Live clip.
Inputs: trackIndex (required), clipSlotIndex (required).
ableton_get_device_parametersB
List parameters exposed by devices on a track, return, or master chain before changing them.
Inputs: target, location, deviceName, trackIndex, +2 more.
ableton_get_metersB
Read observable output meters for tracks, return tracks, and the master channel.
Inputs: no named parameters.
ableton_get_production_reportB
Summarize tracks, buses, devices, meters, arrangement, and production risks.
Inputs: no named parameters.
ableton_get_projectA
Read project structure: tracks, clips, devices, locators, routing, and mixer state.
Inputs: no named parameters.
ableton_get_statusA
Read Ableton Live transport and session status.
Inputs: no named parameters.
ableton_get_workflow_planA
Read a high-level plan-only production workflow by id.
Inputs: workflowId (required).
ableton_humanize_clipC
Apply deterministic MIDI note humanization to an existing editable clip.
Inputs: trackIndex (required), clipSlotIndex (required), seed, velocityAmount, +2 more.
ableton_import_midiA
Import a MIDI file into a target track/clip slot or create tracks from the file.
Inputs: path (required), quantize, trackIndex, createTracks, +1 more.
ableton_insert_arrangement_clipC
Place an existing clip or audio/MIDI reference on the arrangement timeline.
Inputs: startBeat (required), trackIndex (required), kind, name, +5 more.
ableton_launch_clipB
Launch a Session View clip so transport can produce audible playback.
Inputs: trackIndex (required), clipSlotIndex (required).
ableton_launch_sceneB
Launch a Session View scene by clip slot index.
Inputs: sceneIndex (required).
ableton_list_busesA
List master, return buses, and track routing options.
Inputs: no named parameters.
ableton_list_pluginsB
List instruments, effects, racks, presets, VSTs, and Audio Units.
Inputs: kind, query.
ableton_list_returnsB
List Ableton return tracks and their mixer/device state.
Inputs: no named parameters.
ableton_list_risk_policyA
List risk classifications for all known MCP tools and bridge HTTP endpoints.
Inputs: no named parameters.
ableton_list_workflow_plansA
List high-level plan-only production workflows and their risk tiers.
Inputs: no named parameters.
ableton_load_deviceB
Load a Live device, preset, plugin, VST, AU, or rack onto a track.
Inputs: query (required), trackIndex (required), kind, position.
ableton_load_master_deviceB
Load an audio effect, preset, plugin, or rack onto the master track.
Inputs: query (required), kind, position, rationale.
ableton_match_preset_intentA
Match a musical intent to local VST, preset, rack, or effect catalog candidates.
Inputs: intent (required), limit.
ableton_modify_masterC
Modify master mixer state such as volume, pan, or cue volume.
Inputs: pan, solo, muted, volumeDb, +2 more.
ableton_modify_returnC
Modify a return track mixer state.
Inputs: returnIndex (required), pan, name, solo, +3 more.
ableton_modify_trackC
Modify track name, color, mixer state, mute/solo/arm, routing, or sends.
Inputs: trackIndex (required), pan, name, solo, +8 more.
ableton_quantize_clipC
Quantize MIDI note start times in an existing editable clip.
Inputs: grid (required), trackIndex (required), clipSlotIndex (required), strength.
ableton_reorder_deviceC
Move a device within a track, return, or master device chain.
Inputs: toIndex (required), location (required), deviceIndex (required).
ableton_rollback_snapshotB
Rollback the project to a previously created bridge snapshot.
Inputs: snapshotId (required).
ableton_save_projectC
Save the current Ableton Live set through the bridge when supported.
Inputs: path, label.
ableton_search_browserB
Search Ableton browser items with loadable metadata for presets, samples, racks, grooves, plugins, and Max devices.
Inputs: kind, limit, query.
ableton_select_vst_for_midiB
Load the LLM-chosen instrument/plugin for a MIDI role after inventory inspection.
Inputs: role (required), query (required), trackIndex (required), rationale.
ableton_set_automationC
Write automation points for mixer, device, or tempo targets.
Inputs: points (required), target (required), trackIndex.
ableton_set_device_parameterC
Set a device/plugin parameter on a track.
Inputs: parameter (required), value, target, location, +5 more.
ableton_set_signatureC
Set Ableton Live time signature.
Inputs: numerator (required), denominator (required).
ableton_set_tempoB
Set Ableton Live tempo in BPM.
Inputs: bpm (required).
ableton_start_transportA
Start Ableton Live playback.
Inputs: no named parameters.
ableton_stop_transportA
Stop Ableton Live playback.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 59 tools
Most tools have distinct purposes, though some overlap exists (e.g., ableton_analyze_audio vs. ableton_analyze_mix) but descriptions help differentiate. Overall, an agent can distinguish tools with minimal confusion.
All tools follow a consistent 'ableton_verb_noun' pattern, e.g., get_status, create_midi_track, set_tempo. No mixing of conventions; names are predictable and readable.
With 59 tools, the server covers many DAW functionalities but feels heavy for a single MCP server. While each tool has a place, some could be merged (e.g., multiple clip operations). The count is borderline high.
The tool surface is extensive, covering transport, tracks, clips, devices, mixing, analysis, and more. Minor gaps exist (e.g., no delete_regular_track, no create_audio_track/clip) but most core workflows are supported.
Maintenance
Related MCP Connectors
MCP server for Producer/Riffusion AI music generation
Remote MCP server for audio stem separation, denoise, reverb, and MIDI export.
Create, co-edit, analyze, publish, and export collaborative step-sequencer sessions through MCP.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Related MCP Servers
- AlicenseCqualityDmaintenanceA Model Context Protocol server that enables real-time interaction with Ableton Live, allowing AI assistants to control song creation, track management, clip operations, and audio recording workflows.2343 npm94MIT
- AlicenseAqualityCmaintenanceMCP server for Ableton Live that exposes the Live Object Model to LLMs, enabling natural language control of music production.3660 npm12MIT
- AlicenseAqualityDmaintenanceMCP server that bridges Ableton Live with AI models, enabling real-time project inspection and control such as track overview, device parameters, and audio analysis.1273 PyPI1MIT
- FlicenseBqualityDmaintenanceMCP server for controlling Ableton Live, enabling AI assistants to interact with Live sessions through tools for track/clip/scene management, playback control, and device parameter adjustments.48-