ableton-mcp
Control Ableton Live with any LLM: create tracks, arrange clips & compose music via MCP
Runs with mockssource: GitHubPythonMITcommit 9dddc7bd5b95
Python, MIT licensed. The project labels itself: ableton, ai, claude, daw, generative ai, llm, mcp and model context protocol.
ableton-mcp runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Project installs, builds, runs tests (49/49 pass), and the MCP server starts on stdio and SSE transports responding correctly to MCP initialize and tools/list requests.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- uv not available in container1 minute
- pytest not in project dependencies1 minute
- Install time
- 2 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- uv run pytest -v: 49 passed. stdio MCP tools/list returns 30+ tools. SSE transport returns 200 on /sse.
- Model tokens used
- 61,272
- Exact commit tested
- 9dddc7bd5b95
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
All working perfectly. Here's the full report: **Install:** `uv` was installed from astral.sh, `uv sync` built the project and installed all 68 de… **Tests:** `uv run pytest -v` — 49 passed, 0 failed, 0 skipped (0.75s). **Server launch:** Three transports verified: - **stdio** — MCP `tools/list` returns all 30+ tools (get_session_info, create_midi_track, add_note… - **SSE** — server starts on `http://127.0.0.1:8000`, `/sse` returns 200 - **Install script** — `ableton-mcp-install-script --help` prints usage; `--list-targets` returns n… **Errors encountered:** 1. `uv` not pre-installed — fixed in 1m by running astral.sh installer 2. `pytest` not in dependencies — fixed in 1m via `uv add pytest --dev` 3. No Ableton Live running — expected; server handles gracefully with clear log messages 4. No `config.py` — by design (gitignored, Supabase credentials kept out-of-distribution)
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 2 minutes.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.08 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.03 |
Topics (from GitHub)
abletonaiclaudedawgenerative-aillmmcpmodel-context-protocolmusicpython
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ableton-mcp)Questions
- Does ableton-mcp run?
- ableton-mcp runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test ableton-mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9dddc7bd5b95. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ableton-mcp?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ableton-mcp take to install?
- 2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does ableton-mcp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ableton-mcp?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for ableton-mcp?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.