ableton-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKSPACE | No | Absolute path to the production workspace directory, passed to the server via `--workspace`. With a workspace, 22 tools are exposed by default. |
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 |
|---|---|
| ableton_statusA | Compact live session ID, tempo, transport and counts. Call before edits. |
| ableton_capabilitiesA | List available edit operations, argument names and hard limits. |
| ableton_tracksC | Page tracks and top-level device names. Limit 1..128. |
| ableton_parametersB | Page a device's parameters with native value bounds. Limit 1..512. |
| ableton_clipA | Inspect one Session clip, optionally a page of MIDI notes. Limit 1..512. |
| ableton_inspect_setA | Read a local .als file without changing or opening it. Works while Live is disconnected. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| ableton_workflow | Prepare a concise musical task with selective context and honest capabilities. Selected explicitly by the user/client; not an automatic hook. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct area: live session status, capability metadata, track listing, device parameters, a single clip, and offline .als file inspection. Status and capabilities are both metadata, but the descriptions clearly separate runtime state from supported operations and limits.
All tools use the ableton_ prefix with snake_case, making the set easy to scan and predict. Five names are noun-style inspection tools while ableton_inspect_set adds a verb, but this is a minor deviation rather than a confusing convention mix.
Six tools sits comfortably in the well-scoped 3-15 range, and each tool maps to a specific inspection need. The set feels deliberately compact rather than padded or arbitrarily large.
The surface is read-only despite references to edits and a capabilities tool that advertises edit operations; no tool actually performs mutations such as tempo/transport changes, track creation, device parameter changes, or clip edits. It also lacks explicit scene/clip enumeration, making navigation to ableton_clip potentially difficult for an agent.