BLASTO

On a positive note, this will work with dozens of other AI "agents" such as Cursor, GitHub Copilot, Windsurf, Cline, Kiro, and OpenClaw.
All of these "agents" are simply extra text that is passed along with your chat with the LLM. That is it. An agent is simple given the ability to run scripts on your computer (or a server etc...) So if it works with one of them, it will work with the others.

I didn't realize the official Ableton MCP doesn't expose the API, I just wanted to share the most official of the dozens of Ableton MCP out there.

There are dozens of other Ableton MCP implementations that have multiple active developers, why do we need this one, that uses a clunky max for live patch instead of using python that runs inside of ableton and gives you access to more than the 232 tools you mention. With python remote scripts you have access to redo/undo, you can focus windows, toggle the visibility of the Browser, Clip Detail, or Plugin windows, uses much less overhead compared to a m4l device/
The following are big projects that have been around a while
I have personally used
https://github.com/ahujasid/ableton-mcp
^^^ Uses a MIDI remote script instead of a max patch

http://github.com/Simon-Kansara/ableton-live-mcp-server
^^^ Uses OSC instead of Max Patch

Have not used:
https://github.com/uisato/ableton-mcp-extended
You would learn a LOT more by helping contribute to one of the active projects that have developers that are more experienced than you.

Understanding security is very different from having an LLM write stuff you don't understand.

Ableton made their own working MCP, this one does not work and completely ignores the fact that security matters. I would read all this code before using this. https://claude.ai/directory/connectors/ant.dir.gh.ableton.ableton-knowledge

It'd be really easy to download the demo device and undo the 10 minute limit. Would take less than 10 minues.

Also would take about 10 minutes to recreate a simliar device in max on your own. Try it!