Skip to main content
Glama

Ableton MCP · 21 Academy

Conecta Ableton Live con Claude para automatizar el trabajo repetitivo del estudio.

La IA organiza, rutea y prepara tu sesión. La música la haces tú.


¿Qué es esto?

Una versión ampliada de AbletonMCP (de Siddharth Ahuja, licencia MIT) mantenida por Franco / 21 Academy. Le agrega lo que un productor necesita para organizar una sesión sin hacerlo a mano:

Herramienta nueva

Qué hace

get_tracks_overview

Lista todas las pistas con su color, grupo, salida, volumen, paneo, mute y solo, en una sola llamada

set_track_color

Colorea una pista (hex #RRGGBB o nombre: rojo, azul, red, blue…)

set_track_output_routing / get_track_output_routing

Cambia o consulta a dónde va el audio de una pista (Main, un bus, Group…)

set_track_volume

Mueve el fader a un valor en dB (por ejemplo -6)

set_track_pan

Paneo de -1 (izquierda) a 1 (derecha)

set_track_mute / set_track_solo

Mute y solo

configure_tracks

Aplica nombre, color, salida, volumen, paneo, mute y solo a muchas pistas en una sola llamada (más rápido y más barato)

Todas funcionan en pistas normales, returns y el master (track_type: track, return o master).

Lo que no puede hacer: agrupar pistas. La API de Ableton no lo permite desde scripts. La solución es trabajar con una plantilla que ya tenga los grupos armados.

Privacidad: a diferencia del original, aquí la telemetría viene apagada por defecto. No se envía nada a ningún servidor.


Related MCP server: ableton-mcp-extended

Instalación (macOS)

1. Instala uv (en Terminal):

brew install uv

2. Instala el Remote Script en Ableton:

uvx --from git+https://github.com/francocesti21/ableton-mcp-21 ableton-mcp-install-script

Si ya tenías el AbletonMCP original, se reemplaza (el anterior queda respaldado como __init__.py.bak).

3. Agrégalo a Claude: Claude → Settings → Developer → Edit Config, y dentro de "mcpServers":

"AbletonMCP": {
  "command": "uvx",
  "args": ["--from", "git+https://github.com/francocesti21/ableton-mcp-21", "ableton-mcp"]
}

Guarda y cierra Claude por completo (Cmd+Q). Vuelve a abrirlo.

4. Actívalo en Ableton: Settings → Link, Tempo & MIDI → Control Surface: AbletonMCP, Input y Output en None. Si Ableton estaba abierto al instalar, reinícialo.


Ejemplos de pedidos

  • "Muéstrame cómo está organizada la sesión."

  • "Colorea en rojo todas las pistas de batería y mándalas al grupo DRUMS."

  • "Pon todas las pistas a -6 dB de partida."

  • "Mutea las pistas que se llamen COPIA."


Desarrollo

uv run --with pytest pytest -q

Las pruebas simulan la API de Ableton, así que no hace falta tener Live abierto.

Créditos y licencia

Basado en ahujasid/ableton-mcp (MIT). La documentación original está en README_UPSTREAM.md. Este proyecto mantiene la licencia MIT.

Available Tools

46 tools
add_notes_to_clipB

Add MIDI notes to a clip.

Parameters:

  • track_index: The index of the track containing the clip

  • clip_index: The index of the clip slot containing the clip

  • notes: List of note dictionaries, each with pitch, start_time, duration, velocity, and mute

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: notes (required), clip_index (required), track_index (required), user_prompt. Returns: result

clear_notes_from_clipA

Remove all MIDI notes from a Session clip.

Writes are additive (add_notes_to_clip only appends), so to truly modify a clip you clear it first, then add the new notes. Use this with get_clip_notes and add_notes_to_clip for a real read -> modify -> write loop: read the notes, edit the list, clear_notes_from_clip, then add_notes_to_clip the edited notes.

Parameters:

  • track_index: The index of the track containing the clip

  • clip_index: The index of the clip slot containing the clip

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: clip_index (required), track_index (required), user_prompt. Returns: result

configure_tracksA

Apply many track changes in ONE call (much faster and cheaper than one call per setting). Each item is a dict with track_index and any of: track_type ('track'|'return'|'master'), name, color, volume_db, volume, pan, mute, solo, output (routing destination name). Example: [{"track_index": 0, "name": "Kick", "color": "red", "output": "DRUMS BUS", "volume_db": -6}] Items are applied in order; a failing item does not stop the rest.

Parameters:

  • changes: List of per-track change dicts

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: changes (required), user_prompt. Returns: result

create_audio_clipA

Create a new audio clip in an audio track's clip slot by importing a file.

Requires Ableton Live 12.0.5 or newer — the underlying ClipSlot.create_audio_clip Live API was introduced in 12.0.5 and is not available in earlier 12.0.x releases.

Parameters:

  • track_index: The index of the audio track to create the clip in

  • clip_index: The index of the clip slot to create the clip in

  • path: Absolute path to a supported audio file (e.g. a .wav). The target track must be an audio track and the clip slot must be empty.

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: path (required), clip_index (required), track_index (required), user_prompt. Returns: result

create_audio_trackA

Create a new audio track in the Ableton session.

Use this for recorded or imported audio (samples, stems, vocals). For MIDI instruments use create_midi_track instead.

Parameters:

  • index: The index to insert the track at (-1 = end of list)

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: index, user_prompt. Returns: result

create_clipB

Create a new MIDI clip in the specified track and clip slot.

Parameters:

  • track_index: The index of the track to create the clip in

  • clip_index: The index of the clip slot to create the clip in

  • length: The length of the clip in beats (default: 4.0)

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: clip_index (required), track_index (required), length, user_prompt. Returns: result

create_locatorA

Create a named locator (cue point) in the Arrangement at a beat position.

If a locator already exists at that beat (within ~1e-3 tolerance) it is renamed instead of toggled off. Time is in beats from the start of the arrangement (e.g. 0.0 = start, 16.0 = bar 5 in 4/4).

Parameters:

  • name: The locator label (e.g. "Chorus", "Verse 1", "Drop")

  • time: Beat position where the locator should sit

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: name (required), time (required), user_prompt. Returns: result

create_midi_trackA

Create a new MIDI track in the Ableton session.

Parameters:

  • index: The index to insert the track at (-1 = end of list)

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: index, user_prompt. Returns: result

delete_clipA

Delete the clip in the given clip slot, freeing it for reuse.

Use this before create_clip when you want to overwrite an existing clip (create_clip itself refuses to write into an occupied slot).

Parameters:

  • track_index: The index of the track containing the clip

  • clip_index: The index of the clip slot to clear

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: clip_index (required), track_index (required), user_prompt. Returns: result

duplicate_to_arrangementA

Copy a Session-view clip into the Arrangement timeline.

Uses Live's track.duplicate_clip_to_arrangement() API (Live 11 / 12). The clip is placed at destination_time beats from the start of the arrangement on the same track it lives in.

Typical workflow:

  1. create_clip / add_notes_to_clip to build a Session clip

  2. Call duplicate_to_arrangement once per bar/section you need

  3. Call switch_to_arrangement_view to confirm the result in Live

Parameters:

  • track_index: Index of the track that owns the Session clip

  • clip_index: Index of the clip slot in that track (Session view)

  • destination_time: Beat position in the arrangement to place the clip (e.g. 0.0 = start, 8.0 = bar 3 in 4/4)

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: clip_index (required), track_index (required), destination_time (required), user_prompt. Returns: result

fire_clipB

Start playing a clip.

Parameters:

  • track_index: The index of the track containing the clip

  • clip_index: The index of the clip slot containing the clip

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: clip_index (required), track_index (required), user_prompt. Returns: result

get_arrangement_clipsA

List all clips placed in the Arrangement timeline for a track.

Returns each clip's name, start_time, end_time, length, and type.

Parameters:

  • track_index: The index of the track to inspect

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: track_index (required), user_prompt. Returns: result

get_browser_items_at_pathA

Get browser items at a specific path in Ableton's browser.

Parameters:

  • path: Path in the format "category/folder/subfolder" where category is one of the available browser categories in Ableton

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: path (required), user_prompt. Returns: result

get_browser_treeC

Get a hierarchical tree of browser categories from Ableton.

Parameters:

  • category_type: Type of categories to get ('all', 'instruments', 'sounds', 'drums', 'audio_effects', 'midi_effects')

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: user_prompt, category_type. Returns: result

get_clip_notesA

Read all MIDI notes from a Session-view clip.

Returns pitch, start_time, duration, velocity, mute (and extended fields when available).

Parameters:

  • track_index: Track that owns the clip

  • clip_index: Session clip slot index

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: clip_index (required), track_index (required), user_prompt. Returns: result

get_device_parametersB

Read all parameters for a device on a track (name, value, min, max).

Parameters:

  • track_index: Track that owns the device

  • device_index: Index into the track's device chain

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: track_index (required), device_index (required), user_prompt. Returns: result

get_remote_script_infoA

Report Ableton Remote Script version and capabilities (handshake).

Use this to verify the Live-side bridge matches this MCP server package.

Inputs: user_prompt. Returns: result

get_session_infoB

Get detailed information about the current Ableton session

Parameters:

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: user_prompt. Returns: result

get_session_snapshotA

Capture a full project state snapshot for trajectory recording.

Includes session metadata, every track (mixer, devices, session clips, arrangement clips), optional MIDI notes, and optional device parameters. Used to version musical state S_t → S_{t+1}.

Parameters:

  • include_notes: Include MIDI note arrays in clips (default True)

  • include_params: Include device parameter values (default True)

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: user_prompt, include_notes, include_params. Returns: result

get_track_infoC

Get detailed information about a specific track in Ableton.

Parameters:

  • track_index: The index of the track to get information about

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: track_index (required), user_prompt. Returns: result

get_track_output_routingB

Show where a track's audio goes and every destination it can be routed to (e.g. 'Main', 'Group', other track names, 'Sends Only').

Parameters:

  • track_index: Index of the track (within its track_type list)

  • track_type: 'track' (default) or 'return'

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: track_index (required), track_type, user_prompt. Returns: result

get_tracks_overviewA

Compact overview of every track, return track and the master: index, name, color (#RRGGBB), whether it is a group, which group it belongs to, output routing, volume (dB text), pan, mute and solo. Use this before organizing a session; it is much cheaper than calling get_track_info per track.

Parameters:

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: user_prompt. Returns: result

load_drum_kitB

Load a drum rack and then load a specific drum kit into it.

Parameters:

  • track_index: The index of the track to load on

  • rack_uri: The URI of the drum rack to load (e.g., 'Drums/Drum Rack')

  • kit_path: Path to the drum kit inside the browser (e.g., 'drums/acoustic/kit1')

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: kit_path (required), rack_uri (required), track_index (required), user_prompt. Returns: result

load_instrument_or_effectB

Load an instrument or effect onto a track using its URI.

Parameters:

  • track_index: The index of the track to load the instrument on

  • uri: The URI of the instrument or effect to load (e.g., 'query:Synths#Instrument%20Rack:Bass:FileId_5116')

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: uri (required), track_index (required), user_prompt. Returns: result

prefer_candidateA

Record a pairwise preference between two candidate actions or auditions.

winner should be 'a', 'b', or an explicit candidate id matching A or B.

Requires telemetry consent.

Parameters:

  • candidate_a: Id / URI / label for option A

  • candidate_b: Id / URI / label for option B

  • winner: 'a', 'b', or the winning id

  • reason: Optional reason ("C has the right attack")

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: winner (required), candidate_a (required), candidate_b (required), reason, +1 more. Returns: result

rate_last_actionA

Rate the most recent recorded action (or the track after an edit).

Ratings: better | same | worse | keep | reject | thumbs_up | thumbs_down Optional tags (comma-separated): groove, harmony, melody, sound, arrangement, energy, mix, emotion

Requires telemetry consent.

Parameters:

  • rating: Preference label

  • tags: Comma-separated aspect tags

  • note: Optional free-text reason

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: rating (required), note, tags, user_prompt. Returns: result

record_auditionA

Log a browser/preset/sample audition (keep or reject) for preference learning.

Call once per candidate auditioned. Does not load the device — use load_instrument_or_effect when kept=True and you want to commit.

Requires telemetry consent.

Parameters:

  • uri: Browser item URI (or stable preset/sample id)

  • kept: Whether this candidate was kept

  • search_query: Optional search text that led here (e.g. "analog bass")

  • dwell_ms: Optional time spent auditioning

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: uri (required), kept, dwell_ms, user_prompt, +1 more. Returns: result

reject_last_actionA

Mark the last action as rejected (exploration / preference boundary).

Use when the human undoes or discards an agent edit. Requires telemetry consent.

Parameters:

  • reason: Optional why it was rejected

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: reason, user_prompt. Returns: result

set_arrangement_clip_nameA

Set the name of a clip placed in the Arrangement timeline.

Parameters:

  • track_index: The index of the track containing the clip

  • clip_index: The index of the clip within track.arrangement_clips, in the same order returned by get_arrangement_clips (i.e. ordered by start_time)

  • name: The new name for the clip

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: name (required), clip_index (required), track_index (required), user_prompt. Returns: result

set_arrangement_timeA

Move the arrangement playhead to a specific position.

Parameters:

  • time: Position in beats from the start of the arrangement (e.g. 8.0 = bar 3 in 4/4)

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: time (required), user_prompt. Returns: result

set_clip_nameC

Set the name of a clip.

Parameters:

  • track_index: The index of the track containing the clip

  • clip_index: The index of the clip slot containing the clip

  • name: The new name for the clip

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: name (required), clip_index (required), track_index (required), user_prompt. Returns: result

set_device_parameterA

Set a device parameter to a specific value.

Use get_device_parameters first to discover parameter indices and ranges.

Parameters:

  • track_index: Track that owns the device

  • device_index: Index into the track's device chain

  • parameter_index: Index into device.parameters

  • value: New parameter value (Live parameter units)

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: value (required), track_index (required), device_index (required), parameter_index (required), +1 more. Returns: result

set_tempoB

Set the tempo of the Ableton session.

Parameters:

  • tempo: The new tempo in BPM

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: tempo (required), user_prompt. Returns: result

set_track_colorA

Set a track's color. Live snaps it to the nearest color of its palette.

Parameters:

  • track_index: Index of the track (within its track_type list)

  • color: '#RRGGBB' hex, or a name: red, orange, amber, yellow, lime, green, teal, cyan, blue, indigo, purple, violet, magenta, pink, brown, gray, white, black (Spanish names also work: rojo, azul, verde, morado...)

  • track_type: 'track' (default), 'return' or 'master'

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: color (required), track_index (required), track_type, user_prompt. Returns: result

set_track_muteA

Mute (True) or unmute (False) a track.

Parameters:

  • track_index: Index of the track (within its track_type list)

  • mute: True to mute, False to unmute

  • track_type: 'track' (default) or 'return'

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: track_index (required), mute, track_type, user_prompt. Returns: result

set_track_nameA

Set the name of a track.

Parameters:

  • track_index: The index of the track to rename

  • name: The new name for the track

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: name (required), track_index (required), user_prompt. Returns: result

set_track_output_routingA

Route a track's output to another destination by its display name, e.g. 'Main', a bus track's name, or 'Group'. Exact match first, then a unique partial match. On failure the error lists the valid options.

Parameters:

  • track_index: Index of the track (within its track_type list)

  • routing: Destination name as shown in Live's Audio To menu

  • track_type: 'track' (default) or 'return'

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: routing (required), track_index (required), track_type, user_prompt. Returns: result

set_track_panA

Set a track's pan: -1.0 hard left, 0.0 center, 1.0 hard right.

Parameters:

  • track_index: Index of the track (within its track_type list)

  • pan: -1.0 to 1.0

  • track_type: 'track' (default), 'return' or 'master'

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: pan (required), track_index (required), track_type, user_prompt. Returns: result

set_track_soloB

Solo (True) or unsolo (False) a track.

Parameters:

  • track_index: Index of the track (within its track_type list)

  • solo: True to solo, False to unsolo

  • track_type: 'track' (default) or 'return'

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: track_index (required), solo, track_type, user_prompt. Returns: result

set_track_volumeA

Set a track's fader. Prefer volume_db (e.g. -6.0); volume is the raw normalized fader value 0.0-1.0 (0.85 is 0 dB in Live).

Parameters:

  • track_index: Index of the track (within its track_type list)

  • volume_db: Target level in dB (-inf to +6)

  • volume: Raw normalized fader value, used only if volume_db is not given

  • track_type: 'track' (default), 'return' or 'master'

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: track_index (required), volume, volume_db, track_type, +1 more. Returns: result

start_playbackB

Start playing the Ableton session.

Parameters:

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: user_prompt. Returns: result

stop_clipA

Stop playing a clip.

Parameters:

  • track_index: The index of the track containing the clip

  • clip_index: The index of the clip slot containing the clip

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: clip_index (required), track_index (required), user_prompt. Returns: result

stop_playbackB

Stop playing the Ableton session.

Parameters:

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: user_prompt. Returns: result

submit_intentA

Record the human's creative intent for subsequent actions in this session.

Call this before a sequence of edits so trajectory steps are conditioned on intent. Levels: 1=atomic, 2=musical op, 3=section, 4=song, 5=creative goal.

Requires telemetry consent. Data is stored in Supabase (same project as telemetry).

Parameters:

  • text: Natural-language intent (e.g. "make the chorus feel bigger")

  • level: Hierarchical intent level 1–5 (default 5)

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: text (required), level, user_prompt. Returns: result

switch_to_arrangement_viewC

Switch Ableton's main window to the Arrangement view.

Parameters:

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Inputs: user_prompt. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 46 tools

    Disambiguation4/5

    Most tools map cleanly to a distinct resource+action (create_midi_track vs create_audio_track, set_clip_name vs set_arrangement_clip_name) and descriptions explicitly disambiguate. The main soft spots are four overlapping read tools (get_session_info, get_session_snapshot, get_tracks_overview, get_track_info), the per-setting set_track_* calls versus the bulk configure_tracks, and fire_clip versus start_playback.

    Naming Consistency4/5

    Nearly everything is snake_case with a verb-first pattern (get_*, set_*, create_*, load_*, stop_*, record_*). A few read as noun-first or awkward (fire_clip, switch_to_arrangement_view) and the telemetry tools use a slightly different imperative vocabulary, but the convention is readable and predictable overall.

    Tool Count2/5

    46 tools is heavy even for a DAW bridge. The six individual track setters (name, color, volume, pan, mute, solo) are all subsumed by configure_tracks, and six further tools are telemetry/preference logging (submit_intent, rate_last_action, prefer_candidate, reject_last_action, record_audition, set_dataset_consent) that sit outside the musical editing surface.

    Completeness3/5

    Core workflows are well covered: session reading, track creation, clip lifecycle, notes read/modify/write, device loading and parameters, browser browsing, transport, tempo, arrangement and locators. Notable gaps remain — no delete_track, no return/group track creation, no device or parameter reset/removal, no send-level control, and no way to list a track's devices.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers