Skip to content
Back to search

ableton-live-mcp

Control Ableton Live from an AI assistant. 156 tools for building, editing MIDI, mixing, and mastering in a running Live set. Typed, tested on Live 12.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/wstierhout--ableton-live-mcp/badge.svg)](/listings/wstierhout--ableton-live-mcp)

HTML

<a href="/listings/wstierhout--ableton-live-mcp"><img src="/api/listings/wstierhout--ableton-live-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

You need Ableton Live 11 or 12, Python 3.10+, and [uv](https://docs.astral.sh/uv/) (`brew install uv`).

**1. Register the MCP server.**

Codex (local desktop, CLI or IDE host):

codex mcp add ableton -- uvx mcp-server-ableton-live@1.8.1
codex mcp list

For manual configuration and troubleshooting, see the [Codex guide](https://abletonmcp.com/docs/codex/).

Claude Code:

claude mcp add AbletonMCP -s user -- uvx mcp-server-ableton-live@1.8.1

Claude Desktop or Cursor, in the `mcpServers` block of the config file:

{
  "mcpServers": {
    "AbletonMCP": {
      "command": "uvx",
      "args": ["mcp-server-ableton-live@1.8.1"]
    }
  }
}

(To run an unreleased revision instead, use `uvx --from git+https://github.com/wstierhout/ableton-live-mcp ableton-live-mcp`.)

**2. Install the Remote Script.** This copies the Live-side script into your User Library:

uvx mcp-server-ableton-live@1.8.1 install

Then activate the bridge in Live:

1. Fully restart Ableton Live. 2. Open **Settings > Tempo & MIDI**, then find the **MIDI** section and its **Control Surface** list. 3. In an unused **Control Surface** row, select **AbletonMCP**. Leave existing hardware controller rows unchanged. 4. In that same row, set **Input: None** and **Output: None**.

Link is a separate Settings page in current Live versions. In older versions, look under **Link, Tempo & MIDI** (or **Link/MIDI**) in Settings/Preferences, then find the MIDI section.

This selection is required for every MCP client. Installation copies the Remote Script; selecting the Control Surface starts it inside Live. The bridge uses a local socket, so its row does not need hardware MIDI input/output ports.

Run the installer again after upgrading the package so the Live-side script stays version-matched. See Ableton's [guide to third-party Remote Scripts](https://help.ableton.com/hc/en-us/articles/209072009-Installing-third-party-remote-scripts) if the entry does not appear.

**3. Check the setup.**

uvx mcp-server-ableton-live@1.8.1 doctor --json

Use the same `--user-library "/path/to/User Library"` for install and doctor if your library has moved. If an older/different script exists, installation stops: review it before adding `--replace`. A unique backup is retained. Restart Live before diagnosing; doctor checks both installed bytes and the running bridge version.

**4. Start read-only.** Ask for the tempo and track names without changes. Then, in a disposable set, try: "Make a lofi beat at 80 BPM with a dusty drum kit, an upright bass, and Rhodes chords, then put a limiter on the master at -1 dB."

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 247 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <!-- mcp-name: io.github.wstierhout/ableton-live-mcp -->
  2. # Ableton Live MCP Server
  3. [![CI](https://github.com/wstierhout/ableton-live-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/wstierhout/ableton-live-mcp/actions/workflows/ci.yml)
  4. [![Release](https://img.shields.io/github/v/release/wstierhout/ableton-live-mcp)](https://github.com/wstierhout/ableton-live-mcp/releases)
  5. [![License: MIT](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
  6. [![Python](https://img.shields.io/badge/python-3.10%2B-blue)](pyproject.toml)
  7. [![Glama tool quality](https://glama.ai/mcp/servers/wstierhout/ableton-live-mcp/badges/score.svg)](https://glama.ai/mcp/servers/wstierhout/ableton-live-mcp)
  8. **Website and installation guide: [abletonmcp.com](https://abletonmcp.com)**
  9. Control Ableton Live from an AI assistant. This is a Model Context Protocol (MCP)
  10. server that gives Claude, Cursor, Codex, or any MCP client 156 tools for building
  11. tracks, editing MIDI, loading instruments and effects, mixing, and mastering inside
  12. a running Ableton Live set, plus offline tools that read and diff saved `.als`
  13. project files with Live closed.
  14. A Remote Script runs inside Live and exposes the Live API over a local socket. The
  15. MCP server turns that into typed, validated tools that an AI can call correctly,
  16. with per-tool documentation, read-only and destructive hints, and workflow prompts.
  17. ## Quickstart
  18. You need Ableton Live 11 or 12, Python 3.10+, and [uv](https://docs.astral.sh/uv/)
  19. (`brew install uv`).
  20. **1. Register the MCP server.**
  21. Codex (local desktop, CLI or IDE host):
  22. ```bash
  23. codex mcp add ableton -- uvx mcp-server-ableton-live@1.8.1
  24. codex mcp list
  25. ```
  26. For manual configuration and troubleshooting, see the [Codex guide](https://abletonmcp.com/docs/codex/).
  27. Claude Code:
  28. ```bash
  29. claude mcp add AbletonMCP -s user -- uvx mcp-server-ableton-live@1.8.1
  30. ```
  31. Claude Desktop or Cursor, in the `mcpServers` block of the config file:
  32. ```json
  33. {
  34. "mcpServers": {
  35. "AbletonMCP": {
  36. "command": "uvx",
  37. "args": ["mcp-server-ableton-live@1.8.1"]
  38. }
  39. }
  40. }
  41. ```
  42. (To run an unreleased revision instead, use
  43. `uvx --from git+https://github.com/wstierhout/ableton-live-mcp ableton-live-mcp`.)
  44. **2. Install the Remote Script.** This copies the Live-side script into your User
  45. Library:
  46. ```bash
  47. uvx mcp-server-ableton-live@1.8.1 install
  48. ```
  49. Then activate the bridge in Live:
  50. 1. Fully restart Ableton Live.
  51. 2. Open **Settings > Tempo & MIDI**, then find the **MIDI** section and its
  52. **Control Surface** list.
  53. 3. In an unused **Control Surface** row, select **AbletonMCP**. Leave existing
  54. hardware controller rows unchanged.
  55. 4. In that same row, set **Input: None** and **Output: None**.
  56. Link is a separate Settings page in current Live versions. In older versions, look
  57. under **Link, Tempo & MIDI** (or **Link/MIDI**) in Settings/Preferences, then find
  58. the MIDI section.
  59. This selection is required for every MCP client. Installation copies
  60. the Remote Script; selecting the Control Surface starts it inside Live. The bridge
  61. uses a local socket, so its row does not need hardware MIDI input/output ports.
  62. Run the installer again after upgrading the package so
  63. the Live-side script stays version-matched. See Ableton's
  64. [guide to third-party Remote Scripts](https://help.ableton.com/hc/en-us/articles/209072009-Installing-third-party-remote-scripts)
  65. if the entry does not appear.
  66. **3. Check the setup.**
  67. ```bash
  68. uvx mcp-server-ableton-live@1.8.1 doctor --json
  69. ```
  70. Use the same `--user-library "/path/to/User Library"` for install and doctor if your
  71. library has moved. If an older/different script exists, installation stops: review
  72. it before adding `--replace`. A unique backup is retained. Restart Live before
  73. diagnosing; doctor checks both installed bytes and the running bridge version.
  74. **4. Start read-only.** Ask for the tempo and track names without changes. Then,
  75. in a disposable set, try: "Make a lofi beat at 80 BPM with a dusty drum kit,
  76. an upright bass, and Rhodes chords, then put a limiter on the master at -1 dB."
  77. ## What it can do
  78. | Area | Tools |
  79. |---|---|
  80. | Session and transport | session info, one-call session snapshot, play/stop, tempo, tap tempo, time signature, loop, locators and cue navigation, scenes, undo/redo, capture MIDI, song scale, global groove and swing, Ableton Link |
  81. | Tracks and mixer | create and delete MIDI, audio, and return tracks; delete devices; take lanes; group-track fold; volume, pan, mute, solo, arm, sends; input/output routing; meters |
  82. | Clips and notes | create clips, write and edit MIDI notes (with probability), quantize with strength, Groove Pool swing, loop, gain, pitch, warp mode |
  83. | Devices | browse and search by name, load instruments and effects onto any track including Master and Returns, read and set any parameter, sidechain routing, sample preview, rack macro variations, Simpler sample slicing, per-pad drum control, curated device knowledge base |
  84. | Arrangement | place clips on the timeline, read and delete arrangement clips, write clip automation |
  85. | Generators | drum patterns in 7 styles, euclidean rhythms, chord progressions, voice-led jazz voicings, 50-plus genre-aware progressions, voice-leading melodies, walking basslines, motif transforms (invert, retrograde, augment), minimalist processes, humanize, one-call session setup |
  86. | Batch | run many edits in one round trip and one undo step |
  87. | Audio and analysis | record a section to a WAV without the Export dialog, detect key and scale, scan the mix for problems, diff the session since the last check |
  88. | Offline (no Live) | summarize, list tracks, extract MIDI, detect key, read mixer and locator detail, diff two versions, lint a saved `.als`, and parse `.adg`/`.adv` racks with edition detection |
  89. | Recipes | scaffold a genre starter (lofi, house) in one call |
  90. There are also five workflow prompts (`make_a_beat`, `mix_and_master`, `start_a_track`,
  91. `sound_design`, `analyze_and_improve`) and a set of server instructions that teach the
  92. model the conventions before its first call:
  93. 0-based indices, beats for time, 0.85 volume equals 0 dB, and native ranges for
  94. device parameters.
  95. ## Notes
  96. Every action is a specific tool with validated arguments; there is no arbitrary-code
  97. path. Some tools still make destructive edits (delete a track, replace a clip's
  98. notes, overwrite an arrangement region), so save your work before a big session.
  99. ## Audio analysis and session changes
  100. `analyze_audio_file` reads WAV (integer and floating point), AIFF/AIFF-C, FLAC,
  101. Ogg Vorbis, MP3, AAC and M4A/MP4 (AAC or Apple Lossless) locally. The package installs
  102. the PyAV decoder dependency. It preserves the file, sample rate, channel layout and
  103. floating-point headroom; compressed files are measured after decoding. Analysis
  104. covers the first 30 seconds by default (up to 120 seconds, with a 32-million-sample
  105. processing budget), and reports when the result is partial. Measurements include
  106. sample peak and RMS, not LUFS or true peak.
  107. `session_diff` distinguishes renames, reordering and duplicate track names using
  108. identifiers from the running bridge. Call it before and after an edit; the first
  109. call establishes the comparison baseline. Installing an updated Remote Script and
  110. restarting Live keeps the bridge's snapshot format matched to the server.
  111. ## Focusing the toolset
  112. The server registers 156 tools. That is a lot for a model to choose from on a small
  113. task. Set `ABLETON_TOOLSETS` to load only the groups you need, for example
  114. `ABLETON_TOOLSETS=session,tracks,clips,generators`. Groups (each may span several modules): `session`, `tracks`, `clips`, `devices`,
  115. `browser`, `arrangement`, `generators`, `audio`, `analysis`, `offline`, `recipes`.
  116. Unset loads everything.
  117. ## Conventions
  118. - Indices are 0-based. Times and lengths are in beats. Volume uses Live's 0.0 to 1.0
  119. fader range where 0.85 is 0 dB.
  120. - Device parameters use each parameter's own range. Read `get_device_parameters`
  121. first and check min, max, and the display value before setting.
  122. - `add_notes_to_clip` replaces the clip's notes. Use `edit_notes` to add or remove a
  123. few without touching the rest.
  124. - Placing a session clip into the arrangement overwrites whatever is under it, which
  125. is also how you replace a section.
  126. - Transport replies report the state before the command ran. Confirm with
  127. `get_session_info`.
  128. ## Troubleshooting
  129. - `AbletonMCP` is missing from the Control Surface list: the folder has to be named
  130. exactly `AbletonMCP`, and Live only scans scripts at startup, so restart it.
  131. - Every command times out: a dialog is open in Live and it blocks the script. On the
  132. trial, that is the startup nag. Dismiss it and retry.
  133. - Port 9877 is not listening: Live is not running, or the Control Surface is not
  134. set. If another program already uses 9877, set `ABLETON_MCP_PORT` in Live's
  135. launch environment and `ABLETON_PORT` for the server so both sides match.
  136. - You cannot export or freeze from a tool: Live's API has no render or freeze
  137. function, so those stay manual. For rendered audio, export with the shortcut and
  138. analyse the file separately.
  139. ## Security
  140. The Remote Script listens on `127.0.0.1:9877` with no authentication. It is bound to
  141. loopback so only local processes can reach it. Do not forward that port or change the
  142. bind address to a public interface. See [SECURITY.md](SECURITY.md).
  143. ## Development
  144. ```
  145. ableton_live_mcp/
  146. server.py entrypoint: runs the MCP server or a setup subcommand
  147. app.py FastMCP app, lifecycle, and server instructions
  148. connection.py socket client to the Remote Script
  149. cli.py install / uninstall / doctor subcommands
  150. tools/ session, tracks, clips, devices, browser, arrangement,
  151. generators, prompts
  152. remote_script/
  153. __init__.py the Live-side script and its command dispatch tables
  154. tests/ protocol, dispatch-contract, and registration tests
  155. ```
  156. ```bash
  157. uv run --extra dev pytest # tests
  158. uvx ruff check . # lint
  159. ```
  160. CI runs lint, a byte-compile of the Remote Script, and tests on Python 3.10, 3.12,
  161. 3.13, and 3.14.
  162. ## Frequently asked questions
  163. ### What is the Ableton Live MCP Server?
  164. It is a local Model Context Protocol server that lets AI clients such as Claude,
  165. Cursor, and Codex inspect and control Ableton Live through typed tools. It can build
  166. tracks, edit MIDI, load and configure devices, arrange clips, mix a set, and analyze
  167. saved `.als` projects.
  168. ### How is this different from other Ableton MCP servers?
  169. This server exposes 156 specific, validated tools rather than an arbitrary-code
  170. execution tool. It includes destructive/read-only hints, workflow prompts, built-in
  171. music generators, mixing and analysis tools, and offline `.als`/`.adg` inspection.
  172. The Remote Script and MCP package are versioned and tested together.
  173. ### Can it work while Ableton Live is closed?
  174. The real-time control tools require Ableton Live and the bundled Remote Script to be
  175. running. The offline tools can summarize, inspect, lint, extract MIDI from, and diff
  176. saved `.als`, `.adg`, and `.adv` files without launching Live.
  177. ### Which MCP clients are supported?
  178. Any client that can launch a local stdio MCP server can use it, including Claude
  179. Desktop, Claude Code, Cursor, Codex, and compatible IDEs. The canonical command is
  180. `uvx mcp-server-ableton-live`.
  181. ### Is this an official Ableton product?
  182. No. It is an independent, open-source integration and is not affiliated with or
  183. endorsed by Ableton.
  184. ## Credits and license
  185. MIT licensed, maintained by [Wouter Stierhout](https://github.com/wstierhout).
  186. See `LICENSE`. Ableton and Live are trademarks of Ableton AG. This independent
  187. open-source project is not affiliated with or endorsed by Ableton AG.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.