Skip to content
ReviewRamble

The weekly brief

AI, reviewed, in your inbox.

  • New reviews of tools, models, MCP servers and repos, with the verdict up front
  • Re-checked prices and ratings when something changes
  • New analysis pieces as they are published

Models, agents, MCP servers and the tools actually worth your time.

One email a week. Unsubscribe with the link in any brief. How we use your email

Ableton Live MCP Server

Independent MIT server with 156 typed tools for Ableton Live 11 and 12, plus offline reading and diffing of saved .als sets.

Reviewed by ReviewRamble editors · Updated

Setup docs Source codeOpen source

Share this page:XLinkedInFacebookRedditWhatsAppEmail

Our rating

3.9/5

The better-engineered Ableton server for editing and checking real sessions, trading the original's crowd of users for typed tools, offline diffs and no telemetry.

What is Ableton Live MCP Server?

Ableton Live MCP Server, maintained by Wouter Stierhout, connects an MCP client to a running Ableton Live 11 or 12 set through a Remote Script that listens on 127.0.0.1:9877. It started from Siddharth Ahuja's ableton-mcp, whose copyright its MIT licence keeps, but it is a separate project with its own package, mcp-server-ableton-live, and a tool count that has grown from 104 at version 1.0.0 to 156 at 1.8.1. It is not made by Ableton.

The tools cover transport, tracks and mixer, MIDI clips and notes, devices and racks, the arrangement, clip automation, batch edits in one undo step, local audio analysis and generators for drum patterns, chord progressions and basslines. A separate group reads, lints and diffs saved .als, .adg and .adv files with Live closed. The repository has about 78 stars, and version 1.8.1 shipped in September 2026.

How to install Ableton Live MCP Server

uvx mcp-server-ableton-live@1.8.1

Is Ableton Live MCP Server worth it?

This is the more carefully built of the two main Ableton servers, and the one to look at if an agent is meant to edit and check a set rather than sketch one. Every action is a named tool with validated arguments and read-only or destructive hints; there is no tool that runs arbitrary Python. Server instructions teach the model Live's conventions before its first call (0-based indices, time in beats, 0.85 on the fader as 0 dB), which heads off a frequent source of wrong edits.

Against ableton-mcp, the project it grew from, the trade is breadth against context. ableton-mcp registers 37 tools and has about 3,280 stars; this one registers 156 with about 78. Setting ABLETON_TOOLSETS loads only named groups such as session, tracks and clips, which keeps small jobs light. It adds what the original lacks: offline .als inspection and diffs, session_diff for before-and-after checks, a doctor command that confirms the running bridge version, and no network calls of its own, where ableton-mcp sends anonymous telemetry by default. The two do not sit side by side easily: both default to port 9877, and this installer refuses to overwrite a different Remote Script without --replace.

Live's API sets the ceiling. Nothing can render, export or freeze, so bounces stay manual; analyze_audio_file measures sample peak and RMS on a file you export yourself, not LUFS or true peak, and reads the first 30 seconds by default, up to 120. An open dialog in Live, including the trial's startup nag, blocks every command until it is dismissed. Several tools are destructive by design: add_notes_to_clip replaces a clip's notes, and placing a clip in the arrangement overwrites what is under it. Seven issues are open.

The Remote Script listens on 127.0.0.1:9877 with no authentication, so any process on the same computer can drive Live while the script is loaded. SECURITY.md says not to forward the port or point ABLETON_MCP_HOST at a public interface. That is the same exposure as ableton-mcp after its loopback fix, and acceptable on a single-user studio machine.

Where it earns its place

  • A producer running a small mixing service

    See what changed between two revisions of a client's set before sending it back

    Run the offline tools on both saved .als files to list changed tracks, devices, mixer and locator settings, with Live closed. Free, and it saves opening two sessions to hunt for differences by ear and eye.

  • A songwriter on Live 12

    Lay out a lofi sketch at 80 BPM with drums, bass and chords

    Ask for the beat in a disposable set; generators write the drum pattern and voice-led chords, devices load from the browser, and batch edits land as one undo step. Expect to rewrite the parts, since the model does not hear them.

  • A music technology teacher

    Check student projects for common mix problems

    Load ABLETON_TOOLSETS=offline,analysis and lint each submitted .als, then analyse exported WAVs for peak and RMS levels. Results are labelled heuristics, so marking still needs ears.

Before you commit

Setup
Register uvx mcp-server-ableton-live@1.8.1 in the client, run its install subcommand to copy the Remote Script, restart Live, select AbletonMCP in a Control Surface row with input and output set to None, then run doctor --json. Needs Python 3.10 or newer and uv.
Integrations
Claude Desktop, Claude Code, Cursor, Codex and any stdio client; five workflow prompts; listed in the official MCP Registry as io.github.wstierhout/ableton-live-mcp.
Data and privacy
Runs locally; the README and changelog say the server makes no network calls of its own, and audio files are decoded and analysed on your machine. Session details and notes the model reads go to your model provider.
Cost at scale
Free under MIT; the only costs are your Ableton Live 11 or 12 licence and the model provider.
Limits
No render, export or freeze through Live's API; open dialogs block commands; destructive tools replace notes and overwrite arrangement regions, so save first. Seven open issues.

What’s good

  • 156 validated tools with read-only and destructive hints
  • ABLETON_TOOLSETS trims the tool list per task
  • Offline .als, .adg and .adv reading and diffs
  • Makes no network calls of its own

What’s not

  • Far smaller user base than ableton-mcp
  • Cannot render, export or freeze
  • Clashes with ableton-mcp on port 9877
  • Unauthenticated local control socket

Best for

Producers and engineers on Live 11 or 12 who want an agent to set up, edit and check mixes in a running set, with tight control over which tools it sees.

Ableton Live MCP Server alternatives

Ableton Live MCP Server: common questions

Is Ableton Live MCP Server worth it?
The better-engineered Ableton server for editing and checking real sessions, trading the original's crowd of users for typed tools, offline diffs and no telemetry. We rate it 3.9 out of 5.
How much does Ableton Live MCP Server cost?
Free and open source (MIT). Requires your own Ableton Live 11 or 12 licence.
What are the downsides of Ableton Live MCP Server?
Far smaller user base than ableton-mcp; cannot render, export or freeze; clashes with ableton-mcp on port 9877; unauthenticated local control socket.
Who is Ableton Live MCP Server best for?
Producers and engineers on Live 11 or 12 who want an agent to set up, edit and check mixes in a running set, with tight control over which tools it sees.
How much does Ableton Live MCP Server cost for a team or in production?
Free under MIT; the only costs are your Ableton Live 11 or 12 licence and the model provider.
Is Ableton Live MCP Server safe for company data?
Runs locally; the README and changelog say the server makes no network calls of its own, and audio files are decoded and analysed on your machine. Session details and notes the model reads go to your model provider.
What are the best Ableton Live MCP Server alternatives?
The closest alternatives we have reviewed are Ableton MCP and Audio Studio MCP.

Answers checked Nov 14, 2026.