av-conductor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ABLETON_MCP_DISABLE_DATASET | No | Set to true to disable dataset collection for ableton-mcp. | true |
| ABLETON_MCP_DISABLE_TELEMETRY | No | Set to true to disable anonymous telemetry for ableton-mcp. | true |
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_stateC | Current scene, saved cue names, targets, and running ramps. |
| set_sceneA | Change the shared scene and broadcast it to every target over OSC. energy and macros are 0..1. palette is a list of hex colors. Only fields you pass are changed. Note: bpm here is informational for the visuals; to change Live's tempo also call ableton-mcp's set_tempo (or use Ableton Link so everything follows Live). |
| rampB | Glide a numeric value over time (a build, a fade). Returns immediately. param: "energy", "bpm", or "macro:" (e.g. "macro:brightness"). |
| save_cueB | Snapshot the current scene under a name (kept until the server restarts). |
| recall_cueB | Jump to a saved cue (from config/av.toml or save_cue) and send /av/cue . |
| send_oscA | Escape hatch: send a raw OSC message, to all targets or the named ones. Use for program-specific messages the scene model doesn't cover (e.g. "/visuals/layer/2/opacity" 0.5). |
| resend_allA | Re-broadcast the whole scene, e.g. after restarting Max or the visual engine. |
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 7 tools
Each tool has a clearly distinct purpose: save/recall cues, raw OSC escape, full rebroadcast, state query, scene update, and time-based ramping. No two tools overlap in function or would cause misselection.
Names are consistently snake_case and mostly follow a verb_noun pattern (save_cue, recall_cue, send_osc, get_state, set_scene, resend_all). The lone 'ramp' breaks the pattern slightly, but the overall convention is clear.
Seven tools are well-scoped for an AV conductor, covering scene management, cue handling, OSC messaging, and ramping without bloat. Each tool earns its place.
Core lifecycle is present (create/read/update for scenes and cues), but notable gaps exist: no tool to delete or overwrite cues explicitly, and no way to cancel or stop an active ramp. These are common AV operations that agents cannot perform directly.