ableton-mindThe definitive MCP for Ableton Live

"Make me a 128 BPM tech house with a punchy kick, rolling bassline, swung hi-hats." — the assistant builds it in Live, reads it back, and tells you what changed.

I'm an artist

Prompt cookbook

Developer reference

🎛️

Live tools, not guesses

33 MCP tools today, targeting ~180 across the 21 Live Object Model domains — transport, tracks, clips, devices, automation, browser, arrangement, Push and more.

🧠

Embedded knowledge base

55+ Live 12 native devices with parameter schemas (name, range, default, unit). The LLM never guesses "Osc 1 Position".

🍳

Music recipes

14 declarative JSON recipes for drums, bass, chords, racks, arrangements, mixing and live performance.

🔁

Verify loop

After every batch, re-read state and diff against intent. Tools return { ok, verified, diff } — not just ok.

📡

Reactive listeners

LOM property changes become MCP notifications. The LLM "sees" the user play, record, change tempo.

📦

Distribution path

Source install works today. One-click .mcpb, npm, Docker and Smithery are wired but the public RC waits on package validation.

Two ways in

I make music. Start with What is ableton-mind?, then install from source, make your first Live set, and keep the prompt cookbook open.

I'm a developer. Jump to the architecture, tools reference, knowledge base, recipes and distribution notes.

Current status

33 MCP tools, 5 prompts, 3 MCP resources, 55 device schemas, 14 recipes across 7/7 categories, verify loop 23/23, and real Ableton Live 12.4.1 smoke PASS for core bridge/session/transport/track flows.

Public npm and release bundles are not published yet. The next engineering step is TD-048: make npm run typecheck, npm test, npm run build and npm run build:dxt:check green, then cut v0.1.0-rc.1.