Skip to content
Back to search

ableton-mcp

Control Ableton Live with any LLM: create tracks, arrange clips & compose music via MCP

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/ahujasid--ableton-mcp/badge.svg)](/listings/ahujasid--ableton-mcp)

HTML

<a href="/listings/ahujasid--ableton-mcp"><img src="/api/listings/ahujasid--ableton-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.

Three steps: install `uv`, point your MCP client at the server, install the Ableton Remote Script.

**1. Install uv**

# macOS
brew install uv

Otherwise, install from [uv's official website](https://docs.astral.sh/uv/getting-started/installation/).

> **Warning:** Do not proceed before installing uv.

**2. Add the MCP server to your client**

<details open> <summary><b>Claude Desktop</b> — Settings → Developer → Edit Config</summary>

{
    "mcpServers": {
        "AbletonMCP": {
            "command": "uvx",
            "args": [
                "ableton-mcp"
            ]
        }
    }
}

</details>

<details> <summary><b>Cursor</b> — Settings → MCP</summary>

Paste this as a command:

uvx ableton-mcp

</details>

> **Warning:** Only run one instance of the MCP server (either on Cursor or Claude Desktop), not both.

**3. Install the Ableton Remote Script**

uvx --from ableton-mcp ableton-mcp-install-script
uvx --from ableton-mcp ableton-mcp-install-script --list-targets   # preview target folders first

**4. Connect**

1. Launch Ableton Live 2. Go to **Settings/Preferences → Link, Tempo & MIDI** 3. In the **Control Surface** dropdown, select **AbletonMCP** 4. Set **Input** and **Output** to **None**

That's it — ask Claude to build something.

---

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 · 371 lines

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

  1. <div align="center">
  2. # Ableton MCP
  3. **Connect Ableton Live to Claude AI**
  4. Prompt-assisted music production, end-to-end track creation, and Live session and arrangement manipulation — driven by AI.
  5. [![PyPI Version](https://img.shields.io/pypi/v/ableton-mcp?color=blue)](https://pypi.org/project/ableton-mcp/)
  6. [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
  7. [![Discord](https://img.shields.io/badge/Discord-join-5865F2?logo=discord&logoColor=white)](https://discord.gg/JK4hNKGprW)
  8. [**Setup Video**](https://youtu.be/iJWJqyVuPS8) · [**Discord**](https://discord.gg/JK4hNKGprW) · [**Issues**](https://github.com/ahujasid/ableton-mcp/issues)
  9. </div>
  10. ---
  11. ## Quickstart
  12. Three steps: install `uv`, point your MCP client at the server, install the Ableton Remote Script.
  13. **1. Install uv**
  14. ```bash
  15. # macOS
  16. brew install uv
  17. ```
  18. Otherwise, install from [uv's official website](https://docs.astral.sh/uv/getting-started/installation/).
  19. > **Warning:** Do not proceed before installing uv.
  20. **2. Add the MCP server to your client**
  21. <details open>
  22. <summary><b>Claude Desktop</b> — Settings → Developer → Edit Config</summary>
  23. ```json
  24. {
  25. "mcpServers": {
  26. "AbletonMCP": {
  27. "command": "uvx",
  28. "args": [
  29. "ableton-mcp"
  30. ]
  31. }
  32. }
  33. }
  34. ```
  35. </details>
  36. <details>
  37. <summary><b>Cursor</b> — Settings → MCP</summary>
  38. Paste this as a command:
  39. ```
  40. uvx ableton-mcp
  41. ```
  42. </details>
  43. > **Warning:** Only run one instance of the MCP server (either on Cursor or Claude Desktop), not both.
  44. **3. Install the Ableton Remote Script**
  45. ```bash
  46. uvx --from ableton-mcp ableton-mcp-install-script
  47. uvx --from ableton-mcp ableton-mcp-install-script --list-targets # preview target folders first
  48. ```
  49. **4. Connect**
  50. 1. Launch Ableton Live
  51. 2. Go to **Settings/Preferences → Link, Tempo & MIDI**
  52. 3. In the **Control Surface** dropdown, select **AbletonMCP**
  53. 4. Set **Input** and **Output** to **None**
  54. That's it — ask Claude to build something.
  55. ---
  56. ## Table of Contents
  57. - [Quickstart](#quickstart)
  58. - [Features](#features)
  59. - [Components](#components)
  60. - [Installation](#installation)
  61. - [Prerequisites](#prerequisites)
  62. - [Claude for Desktop Integration](#claude-for-desktop-integration)
  63. - [Cursor Integration](#cursor-integration)
  64. - [Installing the Ableton Remote Script](#installing-the-ableton-remote-script)
  65. - [Usage](#usage)
  66. - [Starting the Connection](#starting-the-connection)
  67. - [Using with Claude](#using-with-claude)
  68. - [Capabilities](#capabilities)
  69. - [Example Commands](#example-commands)
  70. - [Troubleshooting](#troubleshooting)
  71. - [Technical Details](#technical-details)
  72. - [Limitations & Security Considerations](#limitations--security-considerations)
  73. - [Telemetry](#telemetry)
  74. - [Join the Community](#join-the-community)
  75. - [Contributing](#contributing)
  76. - [Disclaimer](#disclaimer)
  77. ---
  78. ## Features
  79. | | |
  80. |---|---|
  81. | **Two-way communication** | Connect Claude AI to Ableton Live through a socket-based server |
  82. | **Track manipulation** | Create, modify, and manipulate MIDI and audio tracks |
  83. | **Instrument and effect selection** | Claude can access and load the right instruments, effects and sounds from Ableton's library |
  84. | **Clip creation** | Create and edit MIDI clips with notes |
  85. | **Arrangement view composition** | Build full songs autonomously in Arrangement View, including sections like intro, buildup, drop, breakdown, and outro |
  86. | **Session control** | Start and stop playback, fire clips, and control transport across Session View and Arrangement View |
  87. | **Anonymous telemetry** | Usage tracking to help improve the tool (can be disabled) |
  88. ## Components
  89. The system consists of two main components:
  90. 1. **Ableton Remote Script** (`Ableton_Remote_Script/__init__.py`) — a MIDI Remote Script for Ableton Live that creates a socket server to receive and execute commands
  91. 2. **MCP Server** (`server.py`) — a Python server that implements the Model Context Protocol and connects to the Ableton Remote Script
  92. ---
  93. ## Installation
  94. ### Prerequisites
  95. - **Ableton Live** 10 or newer
  96. - **Python** 3.8 or newer
  97. - **uv** package manager
  98. If you're on Mac, please install uv as:
  99. ```
  100. brew install uv
  101. ```
  102. Otherwise, install from [uv's official website](https://docs.astral.sh/uv/getting-started/installation/)
  103. > **Warning:** Do not proceed before installing uv.
  104. ### Claude for Desktop Integration
  105. [Follow along with the setup instructions video](https://youtu.be/iJWJqyVuPS8)
  106. Go to **Claude → Settings → Developer → Edit Config → `claude_desktop_config.json`** to include the following:
  107. ```json
  108. {
  109. "mcpServers": {
  110. "AbletonMCP": {
  111. "command": "uvx",
  112. "args": [
  113. "ableton-mcp"
  114. ]
  115. }
  116. }
  117. }
  118. ```
  119. ### Cursor Integration
  120. Run ableton-mcp without installing it permanently through uvx. Go to **Cursor Settings → MCP** and paste this as a command:
  121. ```
  122. uvx ableton-mcp
  123. ```
  124. > **Warning:** Only run one instance of the MCP server (either on Cursor or Claude Desktop), not both.
  125. ### Claude Code Integration
  126. In the terminal, run:
  127. ```
  128. claude mcp add AbletonMCP uvx ableton-mcp
  129. ```
  130. ### Installing the Ableton Remote Script
  131. [Follow along with the setup instructions video](https://youtu.be/iJWJqyVuPS8)
  132. Install the Remote Script with:
  133. ```bash
  134. uvx --from ableton-mcp ableton-mcp-install-script
  135. uvx --from ableton-mcp ableton-mcp-install-script --list-targets # preview target folders first
  136. ```
  137. > If you installed the package with `pip` or `pipx`, the command is on your PATH directly — just run `ableton-mcp-install-script`.
  138. This copies the matching Remote Script into your Ableton **User Library**'s `Remote Scripts` folder — the location Live (10.1.13+) scans for third-party control surface scripts. The installer reads the User Library location from Live's `Library.cfg`, falling back to the default (`~/Music/Ableton/User Library` on macOS, `Documents\Ableton\User Library` on Windows). If a different version of the script is already there, the existing file is backed up to `__init__.py.bak` before being replaced.
  139. If your User Library lives somewhere non-standard and isn't detected, point the installer at it directly:
  140. ```bash
  141. uvx --from ableton-mcp ableton-mcp-install-script --target "/path/to/User Library/Remote Scripts"
  142. ```
  143. > The legacy `Preferences/User Remote Scripts` folder (used for instant-mapping configs, not Python control surfaces) is no longer targeted by default; pass `--legacy` if you need it for an old Live version.
  144. Then **restart Ableton** (or re-select the AbletonMCP control surface) so Live loads it. Re-run the command after upgrading the package — the server logs a warning when the loaded script version doesn't match what it expects.
  145. > **Note:** The server does **not** install the script on startup. Writing into Ableton's preferences directory is an explicit action, not a side effect of launching a server.
  146. **First-time Ableton setup:**
  147. 1. Run `uvx --from ableton-mcp ableton-mcp-install-script`
  148. 2. Launch Ableton Live
  149. 3. Go to **Settings/Preferences → Link, Tempo & MIDI**
  150. 4. In the **Control Surface** dropdown, select **AbletonMCP**
  151. 5. Set **Input** and **Output** to **None**
  152. <details>
  153. <summary><b>Manual fallback locations (User Library → Remote Scripts)</b></summary>
  154. - **macOS:** `~/Music/Ableton/User Library/Remote Scripts/AbletonMCP/`
  155. - **Windows:** `C:\Users\[Username]\Documents\Ableton\User Library\Remote Scripts\AbletonMCP\`
  156. If you've moved your User Library, use its actual location (shown in Live under **Preferences → Library → Location of User Library**), and create the `Remote Scripts` folder inside it if it doesn't exist yet.
  157. </details>
  158. The MCP server and Remote Script share a version handshake (`get_remote_script_info`). If they diverge, newer tools degrade gracefully until Live is restarted.
  159. ---
  160. ## Usage
  161. ### Starting the Connection
  162. 1. Ensure the Ableton Remote Script is loaded in Ableton Live
  163. 2. Make sure the MCP server is configured in Claude Desktop or Cursor
  164. 3. The connection should be established automatically when you interact with Claude
  165. ### Using with Claude
  166. Once the config file has been set on Claude, and the remote script is running in Ableton, you will see a hammer icon with tools for the Ableton MCP.
  167. ### Capabilities
  168. - Get session and track information
  169. - Create and modify MIDI and audio tracks
  170. - Create full song arrangements from start to finish in Arrangement View
  171. - Create, edit, and trigger clips
  172. - Control playback
  173. - Load instruments and effects from Ableton's browser
  174. - Add notes to MIDI clips
  175. - Change tempo and other session parameters
  176. ### Example Commands
  177. Here are some examples of what you can ask Claude to do:
  178. | Prompt | Demo |
  179. |---|---|
  180. | *"Create an 80s synthwave track"* | [Watch](https://youtu.be/VH9g66e42XA) |
  181. | *"Create a Metro Boomin style hip-hop beat"* | |
  182. | *"Create a full arrangement with an intro, buildup, drop, breakdown, and outro"* | |
  183. | *"Create a new MIDI track with a synth bass instrument"* | |
  184. | *"Add reverb to my drums"* | |
  185. | *"Create a 4-bar MIDI clip with a simple melody"* | |
  186. | *"Get information about the current Ableton session"* | |
  187. | *"Load a 808 drum rack into the selected track"* | |
  188. | *"Add a jazz chord progression to the clip in track 1"* | |
  189. | *"Set the tempo to 120 BPM"* | |
  190. | *"Play the clip in track 2"* | |
  191. ---
  192. ## Troubleshooting
  193. | Problem | Fix |
  194. |---|---|
  195. | **Connection issues** | Make sure the Ableton Remote Script is loaded, and the MCP server is configured on Claude |
  196. | **Timeout errors** | Try simplifying your requests or breaking them into smaller steps |
  197. | **Have you tried turning it off and on again?** | If you're still having connection errors, try restarting both Claude and Ableton Live |
  198. ## Technical Details
  199. ### Communication Protocol
  200. The system uses a simple JSON-based protocol over TCP sockets:
  201. - **Commands** are sent as JSON objects with a `type` and optional `params`
  202. - **Responses** are JSON objects with a `status` and `result` or `message`
  203. ## Limitations & Security Considerations
  204. - Creating complex musical arrangements might need to be broken down into smaller steps
  205. - The tool is designed to work with Ableton's default devices and browser items
  206. - Always save your work before extensive experimentation
  207. ---
  208. ## Telemetry
  209. There are two tiers, and they have different defaults.
  210. **Anonymous telemetry — on by default.** A random install ID, a per-run session ID, which tools ran, whether they succeeded, and how long they took. This is what counts active users and catches broken tools. It contains none of your content: no prompts, no MIDI, no track or clip names, no device settings.
  211. **Dataset recording — off by default, opt-in.** Everything with your work in it: prompts, MIDI notes, track and clip names, and device settings, which may be published as part of an open dataset used to train music-production models. Nothing here is collected unless you explicitly turn it on.
  212. To see exactly what data each tier collects, see the [Terms & Data Use](TERMS.md).
  213. ### Opting in to dataset recording
  214. Either set the environment variable before starting the server:
  215. ```bash
  216. export ABLETON_MCP_ENABLE_DATASET=true
  217. ```
  218. …or answer the question when your client asks it. On your first tool call you're asked once — as a dialog if your client supports MCP elicitation, otherwise as a message in the chat — and answering yes turns it on from that point. Your answer is stored in `~/.ableton-mcp/consent.json`. Declining, or never answering, records nothing. If you dismiss the dialog without choosing, that isn't treated as an answer and you may be asked again in a later session.
  219. ### Opting out of anonymous telemetry
  220. Set one of these before starting the MCP server:
  221. ```bash
  222. export ABLETON_MCP_DISABLE_TELEMETRY=true
  223. ```
  224. Or use any of these alternatives:
  225. - `DISABLE_TELEMETRY=true`
  226. - `MCP_DISABLE_TELEMETRY=true`
  227. This also disables dataset recording. `ABLETON_MCP_DISABLE_DATASET=true` turns off dataset recording only, and overrides any stored grant.
  228. For Claude Desktop, add the environment variable to your config:
  229. ```json
  230. {
  231. "mcpServers": {
  232. "AbletonMCP": {
  233. "command": "uvx",
  234. "args": ["ableton-mcp"],
  235. "env": {
  236. "ABLETON_MCP_DISABLE_TELEMETRY": "true"
  237. }
  238. }
  239. }
  240. }
  241. ```
  242. ---
  243. ## Join the Community
  244. Give feedback, get inspired, and build on top of the MCP: [**Discord**](https://discord.gg/JK4hNKGprW)
  245. ## Contributing
  246. Contributions are welcome! Please feel free to submit a Pull Request.
  247. ## Disclaimer
  248. This is a third-party integration and not made by Ableton. Made by [Siddharth](https://x.com/sidahuj).
  249. ---
  250. <div align="center">
  251. **If Ableton MCP is useful to you, consider starring the repo**
  252. </div>

Ratings and comments

Sign in to rate this skill.

Sign in

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