ableton-live-mcp
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| live_pingA | Check bridge health/version. |
| live_getC | Resolve object; read selected properties/children. |
| live_set_summaryD | Compact set summary. |
| live_setC | Set a writable Live object property. |
| live_callC | Call one Live object method. |
| live_childrenC | List child objects from a collection. |
| live_device_parametersD | Compact Device parameter metadata. |
| live_parameter_setB | Set one DeviceParameter value with min/max and quantized validation. |
| live_clip_notesC | List MIDI notes from a clip compactly. |
| live_clip_update_notesC | Update existing MIDI notes by note_id. |
| live_clip_add_notesC | Add MIDI notes to a clip from JSON note specs. |
| live_clip_duplicate_to_arrangementB | Duplicate a Session clip to Arrangement on a target track. |
| live_clip_envelopeC | Inspect or edit a clip automation envelope for one parameter. |
| live_clip_velocity_envelopeC | Create parameter automation from MIDI note velocities in a clip. |
| live_clip_warp_markersC | Inspect or edit audio clip warp state and markers. |
| live_track_create_audio_clipC | Create an Arrangement audio clip on a track from a local audio file. |
| live_track_insert_deviceC | Insert a named built-in Live device on a track. |
| live_batchB | Run multiple generic bridge operations in one Live main-thread request; preserves full object-model flexibility. |
| live_browser_rootsB | List app.browser roots. |
| live_browser_capabilitiesD | Browser roots/filter types/semantic API exposure. |
| live_browser_searchC | Bounded app.browser search; returns BrowserItem ids. |
| live_browser_loadB | Load BrowserItem from search by id, uri, or path. |
| live_browser_previewC | Preview or stop previewing a BrowserItem. |
| live_evalA | Evaluate a Python expression inside Live with song, app, obj, and Live bindings. General Live object-model bridge; examples are heuristics, not limits. Use live_exec for statements; prefer installed browser/library assets before generated assets unless asked. |
| live_execC | Execute Python statements inside Live with song, app, obj, this, Live, and result bindings. Set result to a compact dict/list summary to return it. General Live object-model bridge; examples are heuristics, not limits. |
| live_observeC | Add or remove a listener for an object's property. |
| live_eventsC | Drain retained Live listener events. |
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 27 tools
Many tools have clear, distinct purposes for specific resources like clips, devices, and browser. However, the generic object-model bridge tools (live_call, live_get, live_set, live_eval, live_exec, live_observe, live_batch) have overlapping functionality and subtle differences that could cause confusion for agents. Descriptions help but don't fully resolve ambiguity.
All tools start with 'live_' and most follow a 'live_[resource]_[action]' pattern, e.g., live_clip_add_notes, live_browser_search. A few generic tools like live_call, live_children, and live_ping deviate from this pattern but are still readable. The naming is mostly consistent with minor exceptions.
27 tools cover a broad range of Ableton Live functionality including clips, devices, browser, tracks, and a general object bridge. The count is slightly high but justified by the complexity of the domain. It is well-scoped and not excessive.
The tool set provides comprehensive coverage for major workflows: browser navigation, clip editing (notes, envelopes, warp), device control, and track management. The inclusion of general bridge tools (live_get, live_set, live_call, live_eval) fills any gaps, allowing agents to perform essentially any operation on the Live object model.