Ableton Live MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ABLETON_HOST | No | The hostname or IP address of the Ableton Live Remote Script TCP bridge. | 127.0.0.1 |
| ABLETON_PORT | No | The TCP port used to communicate with the Ableton Live Remote Script. | 9877 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_healthA | Ping Ableton Live Remote Script TCP bridge, report connection status, script version, and available capabilities. |
| get_session_infoA | Get global session metadata including tempo, time signature, track counts, and master track state. |
| get_track_structureA | Get summary of all tracks in the session including group tracks, group membership, and arm/mute/solo status. |
| get_track_detailA | Get detailed information for a specific track, including session clip slots, arrangement clips, and device list. |
| get_clip_notesB | Read all MIDI notes from a clip in a track clip slot. |
| get_device_parametersA | Get parameter list for a specific device on a track, including index, name, current value, min, max. |
| get_browser_treeB | Explore top-level categories in Live browser (instruments, sounds, drums, audio_effects, midi_effects). |
| get_browser_itemsB | Get browser items at a given category path (e.g. "instruments/Simpler"). |
| get_bulk_session_structureA | Retrieve full session structure (tempo, scenes, tracks with clips summary and device counts) in a single batched call. |
| set_tempoB | Set session tempo in BPM. |
| set_track_nameB | Rename a track. |
| set_track_colorB | Set color of a track using integer RGB color code. |
| set_clip_colorC | Set color of a clip using integer RGB color code. |
| set_track_muteB | Mute or unmute a track. |
| set_track_soloC | Solo or unsolo a track. |
| set_track_armB | Arm or disarm a track for recording. |
| create_midi_trackC | Create a new MIDI track. |
| create_clipC | Create a new MIDI clip in a clip slot. |
| set_clip_nameC | Rename a clip in a clip slot. |
| edit_clip_notesB | Add or replace MIDI notes in a clip. In "replace" mode, existing notes are cleared first before writing the new note list. |
| delete_clipC | Delete clip from clip slot. |
| fire_clipC | Fire a clip slot in Session view. |
| stop_clipC | Stop a clip slot. |
| fire_sceneC | Fire a scene in Session view. |
| set_scene_nameC | Rename a scene in Session view. |
| stop_all_clipsB | Stop playing all session clips. |
| start_playbackB | Start global transport playback. |
| stop_playbackA | Stop global transport playback. |
| set_device_parameterC | Set value of a device parameter. |
| load_browser_itemC | Load a browser item onto a track by URI. |
| bulk_edit_clipsB | Batch edit multiple clip names and/or batch create clips in a single round trip. |
| bulk_set_device_parametersB | Batch update multiple device parameters in a single round trip. |
| eval_pythonB | Evaluate raw Python code on the Ableton Remote Script instance (for development and advanced debugging). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 33 tools
Most tools have clearly distinct purposes, but there is overlap among retrieval tools (get_session_info, get_track_structure, get_bulk_session_structure) and between bulk and single-operation tools (e.g., create_clip vs. bulk_edit_clips). Descriptions clarify these differences, so misselection is unlikely but possible.
All tool names use snake_case and follow a consistent verb_noun pattern (get_*, set_*, create_*, fire_*, stop_*, etc.), with only minor variations like the 'bulk' prefix. The convention is predictable throughout.
With 33 tools, the server exceeds the typical well-scoped range. While Ableton Live is complex, several tools are convenience duplicates (bulk versions of single operations), making the set feel inflated rather than tightly scoped.
The surface covers many clip, device, and track operations but lacks essential lifecycle and mixer controls: no track deletion, no audio/return track creation, no scene creation/deletion, and no direct track volume/pan/send adjustment. These gaps would cause agent failures in common DAW workflows.