Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ulm0/ableton-live-mcp --skill ableton-livegit clone --depth 1 https://github.com/ulm0/ableton-live-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ulm0/ableton-live-mcp/ableton-live)<a href="https://agentmods.dev/skills/ulm0/ableton-live-mcp/ableton-live"><img src="https://agentmods.dev/badge/skills/ulm0/ableton-live-mcp/ableton-live/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ulm0/ableton-live-mcp/ableton-live"><img src="https://agentmods.dev/badge/skills/ulm0/ableton-live-mcp/ableton-live.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00065 | $0.01271 |
| Opus 5 | $0.00032 | $0.00635 |
| Sonnet 5 | $0.00013 | $0.00254 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
ableton-live scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ableton Live via MCP
The ableton-live MCP server (streamable HTTP, http://127.0.0.1:8722/mcp) controls a running
Ableton Live 12. If tools fail to connect: Live is not running, the extension is not installed,
or the port was changed in the extension's config.json (default 8722).
Core workflow
- Always start with
song_get. It returns the set with object ids. Every other tool takes those ids. Passincludeto fetch only some sections. - Drill down with
track_get/device_get/clip_get— they return child ids (clips, parameters, chains).track_getalso acceptstrack_nameortrack_indexdirectly, and anincludeselector to skip sections you don't need. - Ids become stale when objects are deleted/moved or a different set is loaded. On a stale-id
error, re-run
song_getand re-resolve.
Units and conventions
- All times, positions, durations are beats (quarter notes), not seconds or bars.
At 4/4, one bar = 4 beats. Seconds → beats:
seconds * tempo / 60. - MIDI pitch: 0–127, C3 = 60 in Live's naming (C-2 = 0). Kick drum pad usually C1 = 36.
- Colors:
"#RRGGBB"strings. - Velocity 0–127, probability 0–1.
MIDI composition
- Create track:
track_create {type:"midi"}, then create clip + notes in ONE call:- Session:
clip_create {type:"midi", target_id:<track_id>, scene_index:0, duration:4, notes:[...], name, color} - Arrangement:
clip_create {type:"midi", target_id:<midi_track_id>, start_time, duration, notes:[...]}
- Session:
- Layer more notes:
midi_clip_set_notes {mode:"merge", notes:[...]}(default modereplacewipes the clip — only use it when rewriting everything). - Mechanical edits (transpose, shift, quantize, velocity, delete a range): use
midi_clip_edit_noteswith an optional pitch/timeselect— server-side, no need to read and resend the note list. Note times are relative to the clip start. - Respect the song scale from
song_get(scale.root_note,scale.intervals) when composing.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 90 lines · 65 tokens per session scan A cd6730e9659c
ableton-live is a skill published in the GitHub repository ulm0/ableton-live-mcp (0 stars, last pushed 6d ago), licensed MIT. It adds 65 tokens to every session and 1,271 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ableton-live
Connect and operate the Loophole Bridge (Ableton Live MCP server). Use when the user wants to check Live/bridge prerequisites, wire an MCP client to Loophole, or run a Live editing recipe (humanize, build arrangement, batch rename, chord from prompt). Triggers: "is my Ableton bridge working", "set up loophole"…
groove-builder
Use when the user wants drum patterns by genre - kick, snare, hi-hat, percussion. Examples - "give me a trap beat", "house drum pattern", "DnB drums at 174", "lo-fi drums with swing", "boom-bap pattern".
midi-cleanup
Use when the user asks to humanize a MIDI part, fix voice leading, quantize notes, clean up timing, fix stuck/duplicate notes, or generally polish a MIDI clip they recorded or wrote. Examples - "humanize this hat", "voice these chords better", "the timing is too stiff", "fix the voice leading on the strings".
mixer-doctor
Use when the user describes a mix problem ("muddy", "harsh", "no headroom", "vocals get lost", "kick and bass fighting") or asks for a mix audit. Diagnoses the issue from session state and proposes specific corrective moves with EQ, compression, sends, and routing.
producer-mode
Use when the user asks to set up tracks, pick instruments, scaffold an arrangement, build a project template, or describe a track they want to make in Ableton Live. Examples - "make me a 4-bar lo-fi loop", "set up a film score template", "I want to start a hip-hop beat in C minor".
reference-match
Use when the user references another track they want to emulate the vibe/sound of. Examples - "make this sound like Ólafur Arnalds", "I want a Tame Impala vibe", "match the mix of Kendrick's Money Trees". Translates artist/track references into actionable production decisions.