AbletonMCP
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_clipC | 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_treeB | Get a hierarchical tree of browser categories from Ableton. Parameters:
|
| get_browser_items_at_pathC | Get browser items at a specific path in Ableton's browser. Parameters:
|
| load_drum_kitC | Load a drum rack and then load a specific drum kit into it. 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 16 tools
Most tools have distinct purposes targeting different aspects of Ableton (clips, tracks, browser, playback, session settings), but there is some potential overlap between 'fire_clip' and 'start_playback' as both initiate playback, though at different scopes. The descriptions help clarify that 'fire_clip' is clip-specific while 'start_playback' is session-wide, but an agent might still need to discern this carefully.
Tool names follow a highly consistent snake_case pattern with clear verb_noun structures (e.g., 'add_notes_to_clip', 'create_clip', 'get_session_info'). All tools adhere to this convention, making them predictable and easy to parse, with no deviations or mixed styles observed.
With 16 tools, the count is well-scoped for controlling Ableton Live, covering key areas like clip management, track operations, browser navigation, and playback control. Each tool appears to serve a specific, useful function without redundancy, fitting the domain's complexity appropriately.
The toolset provides solid coverage for core Ableton workflows, including clip creation/editing, track setup, instrument loading, and session control. Minor gaps exist, such as no tools for deleting clips or tracks, adjusting clip parameters beyond notes, or handling audio clips, but agents can likely work around these with the available operations.