{ "markdown": "\n\n# Ableton Live MCP Server\n\n[![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)\n[![Release](https://img.shields.io/github/v/release/wstierhout/ableton-live-mcp)](https://github.com/wstierhout/ableton-live-mcp/releases)\n[![License: MIT](https://img.shields.io/badge/license-MIT-blue)](LICENSE)\n[![Python](https://img.shields.io/badge/python-3.10%2B-blue)](pyproject.toml)\n[![Glama tool quality](https://glama.ai/mcp/servers/wstierhout/ableton-live-mcp/badges/score.svg)](https://glama.ai/mcp/servers/wstierhout/ableton-live-mcp)\n\n**Website and installation guide: [abletonmcp.com](https://abletonmcp.com)**\n\nControl Ableton Live from an AI assistant. This is a Model Context Protocol (MCP)\nserver that gives Claude, Cursor, Codex, or any MCP client 156 tools for building\ntracks, editing MIDI, loading instruments and effects, mixing, and mastering inside\na running Ableton Live set, plus offline tools that read and diff saved `.als`\nproject files with Live closed.\n\nA Remote Script runs inside Live and exposes the Live API over a local socket. The\nMCP server turns that into typed, validated tools that an AI can call correctly,\nwith per-tool documentation, read-only and destructive hints, and workflow prompts.\n\n## Quickstart\n\nYou need Ableton Live 11 or 12, Python 3.10+, and [uv](https://docs.astral.sh/uv/)\n(`brew install uv`).\n\n**1. Register the MCP server.**\n\nCodex (local desktop, CLI or IDE host):\n\n```bash\ncodex mcp add ableton -- uvx mcp-server-ableton-live@1.8.0\ncodex mcp list\n```\n\nFor manual configuration and troubleshooting, see the [Codex guide](https://abletonmcp.com/docs/codex/).\n\nClaude Code:\n\n```bash\nclaude mcp add AbletonMCP -s user -- uvx mcp-server-ableton-live@1.8.0\n```\n\nClaude Desktop or Cursor, in the `mcpServers` block of the config file:\n\n```json\n{\n \"mcpServers\": {\n \"AbletonMCP\": {\n \"command\": \"uvx\",\n \"args\": [\"mcp-server-ableton-live@1.8.0\"]\n }\n }\n}\n```\n\n(To run an unreleased revision instead, use\n`uvx --from git+https://github.com/wstierhout/ableton-live-mcp ableton-live-mcp`.)\n\n**2. Install the Remote Script.** This copies the Live-side script into your User\nLibrary:\n\n```bash\nuvx mcp-server-ableton-live@1.8.0 install\n```\n\nThen activate the bridge in Live:\n\n1. Fully restart Ableton Live.\n2. Open **Settings > Tempo & MIDI**, then find the **MIDI** section and its\n **Control Surface** list.\n3. In an unused **Control Surface** row, select **AbletonMCP**. Leave existing\n hardware controller rows unchanged.\n4. In that same row, set **Input: None** and **Output: None**.\n\nLink is a separate Settings page in current Live versions. In older versions, look\nunder **Link, Tempo & MIDI** (or **Link/MIDI**) in Settings/Preferences, then find\nthe MIDI section.\n\nThis selection is required for every MCP client. Installation copies\nthe Remote Script; selecting the Control Surface starts it inside Live. The bridge\nuses a local socket, so its row does not need hardware MIDI input/output ports.\n\nRun the installer again after upgrading the package so\nthe Live-side script stays version-matched. See Ableton's\n[guide to third-party Remote Scripts](https://help.ableton.com/hc/en-us/articles/209072009-Installing-third-party-remote-scripts)\nif the entry does not appear.\n\n**3. Check the setup.**\n\n```bash\nuvx mcp-server-ableton-live@1.8.0 doctor --json\n```\n\nUse the same `--user-library \"/path/to/User Library\"` for install and doctor if your\nlibrary has moved. If an older/different script exists, installation stops: review\nit before adding `--replace`. A unique backup is retained. Restart Live before\ndiagnosing; doctor checks both installed bytes and the running bridge version.\n\n**4. Start read-only.** Ask for the tempo and track names without changes. Then,\nin a disposable set, try: \"Make a lofi beat at 80 BPM with a dusty drum kit,\nan upright bass, and Rhodes chords, then put a limiter on the master at -1 dB.\"\n\n## What it can do\n\n| Area | Tools |\n|---|---|\n| 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 |\n| 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 |\n| Clips and notes | create clips, write and edit MIDI notes (with probability), quantize with strength, Groove Pool swing, loop, gain, pitch, warp mode |\n| 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 |\n| Arrangement | place clips on the timeline, read and delete arrangement clips, write clip automation |\n| 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 |\n| Batch | run many edits in one round trip and one undo step |\n| 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 |\n| 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 |\n| Recipes | scaffold a genre starter (lofi, house) in one call |\n\nThere are also five workflow prompts (`make_a_beat`, `mix_and_master`, `start_a_track`,\n`sound_design`, `analyze_and_improve`) and a set of server instructions that teach the\nmodel the conventions before its first call:\n0-based indices, beats for time, 0.85 volume equals 0 dB, and native ranges for\ndevice parameters.\n\n## Notes\n\nEvery action is a specific tool with validated arguments; there is no arbitrary-code\npath. Some tools still make destructive edits (delete a track, replace a clip's\nnotes, overwrite an arrangement region), so save your work before a big session.\n\n## Audio analysis and session changes\n\n`analyze_audio_file` reads WAV (integer and floating point), AIFF/AIFF-C, FLAC,\nOgg Vorbis, MP3, AAC and M4A/MP4 (AAC or Apple Lossless) locally. The package installs\nthe PyAV decoder dependency. It preserves the file, sample rate, channel layout and\nfloating-point headroom; compressed files are measured after decoding. Analysis\ncovers the first 30 seconds by default (up to 120 seconds, with a 32-million-sample\nprocessing budget), and reports when the result is partial. Measurements include\nsample peak and RMS, not LUFS or true peak.\n\n`session_diff` distinguishes renames, reordering and duplicate track names using\nidentifiers from the running bridge. Call it before and after an edit; the first\ncall establishes the comparison baseline. Installing an updated Remote Script and\nrestarting Live keeps the bridge's snapshot format matched to the server.\n\n## Focusing the toolset\n\nThe server registers 156 tools. That is a lot for a model to choose from on a small\ntask. Set `ABLETON_TOOLSETS` to load only the groups you need, for example\n`ABLETON_TOOLSETS=session,tracks,clips,generators`. Groups (each may span several modules): `session`, `tracks`, `clips`, `devices`,\n`browser`, `arrangement`, `generators`, `audio`, `analysis`, `offline`, `recipes`.\nUnset loads everything.\n\n## Conventions\n\n- Indices are 0-based. Times and lengths are in beats. Volume uses Live's 0.0 to 1.0\n fader range where 0.85 is 0 dB.\n- Device parameters use each parameter's own range. Read `get_device_parameters`\n first and check min, max, and the display value before setting.\n- `add_notes_to_clip` replaces the clip's notes. Use `edit_notes` to add or remove a\n few without touching the rest.\n- Placing a session clip into the arrangement overwrites whatever is under it, which\n is also how you replace a section.\n- Transport replies report the state before the command ran. Confirm with\n `get_session_info`.\n\n## Troubleshooting\n\n- `AbletonMCP` is missing from the Control Surface list: the folder has to be named\n exactly `AbletonMCP`, and Live only scans scripts at startup, so restart it.\n- Every command times out: a dialog is open in Live and it blocks the script. On the\n trial, that is the startup nag. Dismiss it and retry.\n- Port 9877 is not listening: Live is not running, or the Control Surface is not\n set. If another program already uses 9877, set `ABLETON_MCP_PORT` in Live's\n launch environment and `ABLETON_PORT` for the server so both sides match.\n- You cannot export or freeze from a tool: Live's API has no render or freeze\n function, so those stay manual. For rendered audio, export with the shortcut and\n analyse the file separately.\n\n## Security\n\nThe Remote Script listens on `127.0.0.1:9877` with no authentication. It is bound to\nloopback so only local processes can reach it. Do not forward that port or change the\nbind address to a public interface. See [SECURITY.md](SECURITY.md).\n\n## Development\n\n```\nableton_live_mcp/\n server.py entrypoint: runs the MCP server or a setup subcommand\n app.py FastMCP app, lifecycle, and server instructions\n connection.py socket client to the Remote Script\n cli.py install / uninstall / doctor subcommands\n tools/ session, tracks, clips, devices, browser, arrangement,\n generators, prompts\n remote_script/\n __init__.py the Live-side script and its command dispatch tables\ntests/ protocol, dispatch-contract, and registration tests\n```\n\n```bash\nuv run --extra dev pytest # tests\nuvx ruff check . # lint\n```\n\nCI runs lint, a byte-compile of the Remote Script, and tests on Python 3.10, 3.12,\n3.13, and 3.14.\n\n## Frequently asked questions\n\n### What is the Ableton Live MCP Server?\n\nIt is a local Model Context Protocol server that lets AI clients such as Claude,\nCursor, and Codex inspect and control Ableton Live through typed tools. It can build\ntracks, edit MIDI, load and configure devices, arrange clips, mix a set, and analyze\nsaved `.als` projects.\n\n### How is this different from other Ableton MCP servers?\n\nThis server exposes 156 specific, validated tools rather than an arbitrary-code\nexecution tool. It includes destructive/read-only hints, workflow prompts, built-in\nmusic generators, mixing and analysis tools, and offline `.als`/`.adg` inspection.\nThe Remote Script and MCP package are versioned and tested together.\n\n### Can it work while Ableton Live is closed?\n\nThe real-time control tools require Ableton Live and the bundled Remote Script to be\nrunning. The offline tools can summarize, inspect, lint, extract MIDI from, and diff\nsaved `.als`, `.adg`, and `.adv` files without launching Live.\n\n### Which MCP clients are supported?\n\nAny client that can launch a local stdio MCP server can use it, including Claude\nDesktop, Claude Code, Cursor, Codex, and compatible IDEs. The canonical command is\n`uvx mcp-server-ableton-live`.\n\n### Is this an official Ableton product?\n\nNo. It is an independent, open-source integration and is not affiliated with or\nendorsed by Ableton.\n\n## Credits and license\n\nMIT licensed, maintained by [Wouter Stierhout](https://github.com/wstierhout).\nSee `LICENSE`. Ableton and Live are trademarks of Ableton AG. This independent\nopen-source project is not affiliated with or endorsed by Ableton AG.\n", "bytes": 11750, "sha": "b1aa986c6a712dfe4935ba529917dda0a6068c5957f3c2b3016defa744dcf46d", "repo_slug": "wstierhout/ableton-live-mcp", "fonte": "repo", "truncated": false, "api": "https://agentalog.com/api/listings/mcp_io_github_wstierhout_ableton_live_mcp_ba4f1b4e/readme" }