Summary

It maps the OSC surface exhaustively rather than picking a handful of convenient commands.

Because it is built on AbletonOSC's address space rather than a curated shortlist, the reach is wide — which matters for the bulk edits that are tedious in the UI, like changing input routing on every track matching a name. The daemon is a second process you have to remember to start.

What it is

A server that talks to Ableton Live over OSC, mapping the AbletonOSC address space to MCP tools. Two pieces run: the MCP server, and an OSC daemon that relays to Live.

What you get

Control of Ableton Live from an MCP client, with the available OSC addresses exhaustively mapped to tools
Request-response handling, so a command's result comes back rather than being fired and forgotten
Prompts like preparing a set to record a band, or setting the input routing on every track whose name contains a word

Requirements

Python 3.8+, AbletonOSC installed as a control surface in Live, and uv to install the project. Run osc_daemon.py alongside the server: it listens for MCP client connections on port 65432, sends to Live on 11000 and receives on 11001, all on localhost by default. Point the client at mcp_ableton_server.py using the project's virtualenv Python.

Setup effort

One command — uvx ableton-live-mcp-server