ableton-mcp-extended
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_session_infoB | Get detailed information about the current Ableton session |
| get_track_infoC | Get detailed information about a specific track in Ableton. Parameters:
|
| create_midi_trackB | Create a new MIDI track in the Ableton session. Parameters:
|
| set_track_nameC | Set the name of a track. Parameters:
|
| create_clipA | Create a new MIDI clip in the specified track and clip slot. Parameters:
|
| add_notes_to_clipB | Add MIDI notes to a clip. Parameters:
|
| set_clip_nameB | Set the name of a clip. Parameters:
|
| set_tempoA | Set the tempo of the Ableton session. Parameters:
|
| load_instrument_or_effectC | Load an instrument or effect onto a track using its URI. Parameters:
|
| fire_clipA | Start playing a clip. Parameters:
|
| stop_clipB | Stop playing a clip. Parameters:
|
| start_playbackA | Start playing the Ableton session. |
| stop_playbackA | Stop playing the Ableton session. |
| get_browser_treeA | Get a hierarchical tree of browser categories from Ableton. Parameters:
|
| get_browser_items_at_pathA | Get browser items at a specific path in Ableton's browser. Parameters:
|
| load_drum_kitB | Load a drum rack and then load a specific drum kit into it. Parameters:
|
| get_mixerA | Get the mixer state (volume, panning and sends) for a track. Each value is reported three ways: the raw 0..1 parameter value, the dB it corresponds to, and the string Live itself displays. Parameters:
|
| set_track_volumeA | Set a track's volume fader. Prefer Parameters:
|
| set_track_panningA | Set a track's pan position. Parameters:
|
| set_sendA | Set one of a track's send levels. As with volume, prefer Parameters:
|
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 20 tools
Most tools have clearly distinct purposes, but load_instrument_or_effect and load_drum_kit both load devices, and get_mixer vs get_track_info could cause initial confusion. Descriptions clarify these boundaries, so ambiguity is low.
All tool names follow a consistent verb_noun pattern in snake_case, such as set_tempo, get_mixer, create_clip, and add_notes_to_clip. Even special cases like fire_clip fit the pattern. No mixed conventions or inconsistent naming styles.
At 20 tools, the server is on the heavier side of the typical range, but the scope justifies the count. Each tool addresses a distinct aspect of Ableton control, from transport and mixing to clip editing and browser navigation, so the number feels appropriate rather than bloated.
The tool set covers core workflows: creating tracks, loading devices, creating and editing clips, controlling playback, and adjusting mixer settings. Missing operations like deleting tracks/clips or retrieving detailed clip info are minor gaps that agents can work around or that may be outside the server's intended scope.