AbletonMCP: Control Ableton Live with Claude AI
AbletonMCP connects Claude AI to Ableton Live through the Model Context Protocol, letting Claude create tracks, edit clips, and assemble arrangements inside a running Live session. It's a third-party project, not made by Ableton. Reach for it if you own Ableton Live and want to sketch ideas by typing prompts instead of clicking through menus; skip it if you lack a Live license, since AbletonMCP controls Ableton rather than including it.
What is AbletonMCP?
AbletonMCP is a Python-based bridge pairing Ableton Live with an MCP client such as Claude Desktop or Cursor, built from two pieces: a Remote Script that runs inside Live as a socket server, and a separate MCP server (server.py) that speaks the Model Context Protocol to the AI client. Commands travel between them as JSON over TCP, so a Claude prompt turns into an action like creating a MIDI track or firing a clip inside your open Ableton session.
Who is AbletonMCP for?
AbletonMCP is for Ableton Live owners who already know their way around Session and Arrangement View and want an AI pair to handle the repetitive parts — adding a bass track, loading a drum rack, sketching a chord progression — while they steer with plain-language prompts through Claude Desktop or Cursor. It's built for producers experimenting with prompt-driven composition, not as a substitute for learning Ableton itself: you still need the Live license and a working sense of tracks, clips, and devices to make sense of what Claude is doing. Skip it if you don't own Ableton Live 10 or newer, since the whole integration only works inside a running Live session.
Key Capabilities
- ✓Two-way socket communication: a Remote Script running inside Ableton opens a socket server that the separate MCP server (server.py) talks to, per the README.
- ✓The handling of tracks allows for the creation, modification, and manipulation of MIDI and audio tracks from a Claude prompt.
- ✓Instrument and effect selection — Claude can access and load instruments, effects, and sounds from Ableton's own library.
- ✓Clip creation and editing — build and edit MIDI clips, including adding individual notes.
- ✓Arrangement View composition — assemble full songs autonomously in Arrangement View, including named sections like intro, buildup, drop, breakdown, and outro.
- ✓Through session control, users can initiate and halt playback, trigger clips, and manage transport operations within both Session View and Arrangement View.
- ✓JSON-over-TCP protocol — JSON objects serve as commands, containing a type along with optional params, and responses come back with a status plus a result or message, per the README's technical-details section.
Example Music Commands
- •Describing a genre and letting Claude build the track — the README's own examples include an 80s synthwave track (with a linked demo video) and a Metro Boomin-style hip-hop beat.
- •Asking for a complete arrangement in one prompt, including sections like intro, buildup, drop, breakdown, and outro.
- •Building specific pieces on request — a new MIDI track loaded with a synth bass instrument, a 4-bar MIDI clip with a simple melody, or a jazz chord progression added to the clip in track 1.
- •Tweaking an existing session — adding reverb to your drums, loading an 808 drum rack onto a selected track, or setting the tempo to 120 BPM.
- •Querying and controlling playback — asking for information about the current Ableton session, or having Claude play the clip in track 2.
Getting Started with AbletonMCP
AbletonMCP can be installed two ways. Via Smithery, a single command (npx -y @smithery/cli install @ahujasid/ableton-mcp --client claude) sets up the Claude Desktop integration automatically. For a manual setup, the prerequisites are Ableton Live 10 or newer, Python 3.8 or newer, and the uv package manager (brew install uv on a Mac, or from uv's own site otherwise) — the README is explicit that you shouldn't proceed before uv is installed. For Claude Desktop, you edit claude_desktop_config.json (via Claude > Settings > Developer > Edit Config) to add an AbletonMCP entry under mcpServers with command "uvx" and args ["ableton-mcp"]. For Cursor, you paste "uvx ableton-mcp" as a command under Cursor Settings > MCP instead — the README warns against running both Cursor's and Claude Desktop's MCP servers at the same time. Separately, you install the Remote Script: download the AbletonMCP_Remote_Script/__init__.py file from the repo, copy it into a folder named "AbletonMCP" inside Ableton's MIDI Remote Scripts directory (the exact path varies by OS and Live version — the README lists a couple of candidate locations for macOS and Windows), then in Ableton go to Settings/Preferences → Link, Tempo & MIDI, pick "AbletonMCP" in the Control Surface dropdown, and set both Input and Output to "None". The README also links a setup walkthrough video for these steps.
Interacting with Claude AI
Once the Remote Script is loaded in Ableton and the MCP server is configured in Claude Desktop or Cursor, the connection is established automatically the moment you interact with Claude — the README describes seeing a hammer icon appear with the Ableton MCP tools once both sides are set. From there you type what you want in plain language and Claude issues the corresponding commands to Live. If the connection doesn't come up, the README's troubleshooting notes point to checking that the Remote Script is actually loaded and the MCP server is configured; for timeout errors, it suggests simplifying a request or breaking it into smaller steps; and if problems persist, restarting both Claude and Ableton Live.
Strengths
- ✓Two distinct, documented components (Remote Script plus MCP server) make the moving parts easy to reason about — you know what runs on the Ableton side versus the Claude side.
- ✓Covers a wide slice of Live's workflow: track creation, clip editing, instrument/effect loading, and full Arrangement View composition, not just triggering a couple of clips.
- ✓Works with either Claude Desktop or Cursor as the MCP client, per the README, so you're not locked into one AI tool.
- ✓Telemetry is opt-out via a documented environment variable, and the README states personal information, project names, and audio content are not gathered.
- ✓MIT license, a one-command install path via Smithery, and an active Discord for support and feedback.
Current Limitations
- △The README says complex arrangements might need to be broken into smaller steps rather than requested in a single large prompt.
- △AbletonMCP is described as whose functionality is centered on Ableton's default devices and browser items — the README doesn't document behavior with third-party plugins or custom Max for Live devices.
- △AbletonMCP collects anonymous telemetry by default (usage statistics, session activity, error and performance metrics) unless you set one of three documented environment variables to opt out.
- △The README recommends saving your work before extensive experimentation, which implies no built-in undo or safety net beyond Ableton's own.
- △It's a third-party integration, not made or officially supported by Ableton, per the README's own disclaimer.
- △Setup requires editing a JSON config file and manually placing a Python script inside Ableton's Remote Scripts folder, with file paths that differ by OS and Ableton version.
Exploring Similar Tools
Common Questions
For AbletonMCP to function, Python 3.8 or newer must be present, along with Ableton Live 10 or newer. Additionally, the uv package manager is needed. Mac users, according to the README, should install uv using 'brew install uv' prior to any other steps.
AbletonMCP does support Cursor: the README documents pasting a short uvx command under Cursor Settings > MCP as an alternative to Claude Desktop. Just don't run both clients' MCP servers at the same time — the README says only one instance should run at once.
AbletonMCP collects anonymous telemetry by default — tool usage statistics, session information for active-user counts, and error and performance metrics — though the README states the tool does not collect personal information, project names, or audio content.
Telemetry in AbletonMCP is disabled by setting an environment variable before starting the MCP server: ABLETON_MCP_DISABLE_TELEMETRY=true, or alternatively DISABLE_TELEMETRY=true or MCP_DISABLE_TELEMETRY=true. In a Claude Desktop config, the variable goes under that server's env block.
Through AbletonMCP, Claude can create and modify MIDI and audio tracks, create and trigger clips, import instruments and effects using Ableton's browser, insert notes into MIDI clips, build Arrangement View song structures, and control playback and tempo, per the README's capabilities list.
AbletonMCP is not an official Ableton product — its own README carries a disclaimer stating it's a third-party integration and not made by Ableton.
The problem it solves
Producing in Ableton Live still means clicking through the same sequence of menus for repetitive setup work — loading an instrument, naming a track, laying down a chord progression — before getting to the part that's actually creative. AbletonMCP's README frames the project's purpose around a specific pairing: wiring Claude directly into a running Live session over a socket connection, so requests like adding a synth bass track or putting reverb on the drums become a prompt instead of a sequence of clicks, without exporting stems or leaving Ableton for a separate app.
Related repositories
Curious whether ableton-mcp is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about ableton-mcp.