agentleFS
CanArslanDevCanArslanDev/ableton-live-mcp/skills/ableton-setup/SKILL.md

ableton-setup

Skill11 starsChanged 36 days agoMITView on GitHub

Setting up and troubleshooting the connection between Claude and Ableton Live (the ableton MCP server and the AbletonMCP Remote Script). Use when the ableton tools fail to connect, time out, report an outdated or missing Remote Script, ask for authentication, or when the user is installing this for the first time.

The file

Files
SKILL.md

Setup and troubleshooting

The MCP server talks to Live through a MIDI Remote Script ("AbletonMCP") that runs inside Live and listens on 127.0.0.1:9877. Live must be running with that script selected as a Control Surface.

First-time setup

  1. install_remote_script() copies the script into Live's User Library (Remote Scripts/AbletonMCP). It works for Live 11 and 12, the Trial too.
  2. The user restarts Live, because Live loads Remote Scripts only at launch.
  3. In Live: Settings → Link, Tempo & MIDI → Control Surface → AbletonMCP (Input/Output: None).
  4. doctor() should now report the connection as ok.

Diagnose

doctor() checks the server and Remote Script versions, every installed copy of the script, the connection and its latency, dialogs open in Live, CPU load, and AbletonMCP errors in Live's log. Each failed check comes with its fix; do what it says rather than guessing.

SymptomCause and fix
Could not connect to Ableton LiveLive is not running, or AbletonMCP is not chosen as a Control Surface, or something else holds port 9877.
"Connection reset by peer" right after connectingThe Remote Script serves at most 8 clients, one per MCP server; other assistant sessions hold them. Ask the user to close the sessions they no longer use, or to restart Live.
"older than this server" / outdated scriptinstall_remote_script(), then restart Live. If the version does not change, an old AbletonMCP folder inside the Live application (…/Contents/App-Resources/MIDI Remote Scripts/) shadows the User Library copy; doctor() finds it. Live updates have restored one there.
Authentication requiredThe server is older than the Remote Script, which wants the session token since 2.0. Update the server.
Invalid session tokenLive restarted and wrote a new token (~/.ableton-mcp/live-session.json); the next call reads it again. Across users or containers, set ABLETON_MCP_TOKEN.
Tools hang while a dialog is openLive waits for the user to close it; doctor() names the dialog.
Claude Desktop: no response within 2 minutes (macOS)A pending "uv wants to access files in your Documents folder" prompt; allow it and restart the client.

Live's own log is ~/Library/Preferences/Ableton/Live <version>/Log.txt on macOS (lines tagged (AbletonMCP)).

Live Trial

Everything works in the Trial, Max for Live included, except that saving and exporting are disabled once the trial has expired. Analysis tools record by themselves and do not need export.

Tool set

ABLETON_MCP_PROFILE=full adds the reference-song tools (dissect_reference, reference_job, index_sound_library, build_from_blueprint) and the original upstream tools that newer tools replace (for prompts written against them). The default core profile has one tool per job. The server reads the variable from the client's environment: in Claude Code, start it as ABLETON_MCP_PROFILE=full claude (or export it in the shell profile); in Claude Desktop, pick "full" under the extension's Tool set. doctor's reference-dissector line says when the server runs without them.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.