by ahujasid
Control Ableton Live for advanced music production—track creation, MIDI editing, playback, and sound design. Perfect for
Enables Claude AI to directly control Ableton Live music production software through bidirectional communication. Create tracks, edit MIDI, load instruments, and control playback using natural language prompts.
Ableton Live is a community-built MCP server published by ahujasid that provides AI assistants with tools and capabilities via the Model Context Protocol. Control Ableton Live for advanced music production—track creation, MIDI editing, playback, and sound design. Perfect for It is categorized under other, developer tools. This server exposes 16 tools that AI clients can invoke during conversations and coding sessions.
You can install Ableton Live in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Ableton Live is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Ableton Live is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
I recommend Ableton Live for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Ableton Live is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Ableton Live reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Useful MCP listing: Ableton Live is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated Ableton Live against two servers with overlapping tools; this profile had the clearer scope statement.
Ableton Live is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Useful MCP listing: Ableton Live is the kind of server we cite when onboarding engineers to host + tool permissions.
According to our notes, Ableton Live benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Useful MCP listing: Ableton Live is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 44
AbletonMCP connects Ableton Live to Claude AI through the Model Context Protocol (MCP), allowing Claude to directly interact with and control Ableton Live. This integration enables prompt-assisted music production, track creation, and Live session manipulation.
Give feedback, get inspired, and build on top of the MCP: Discord. Made by Siddharth
The system consists of two main components:
Ableton_Remote_Script/__init__.py): A MIDI Remote Script for Ableton Live that creates a socket server to receive and execute commandsserver.py): A Python server that implements the Model Context Protocol and connects to the Ableton Remote ScriptTo install Ableton Live Integration for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @ahujasid/ableton-mcp --client claude
If you're on Mac, please install uv as:
brew install uv
Otherwise, install from [uv's official website][https://docs.astral.sh/uv/getting-started/installation/]
⚠️ Do not proceed before installing UV
Follow along with the setup instructions video
{
"mcpServers": {
"AbletonMCP": {
"command": "uvx",
"args": [
"ableton-mcp"
]
}
}
}
Run ableton-mcp without installing it permanently through uvx. Go to Cursor Settings > MCP and paste this as a command:
uvx ableton-mcp
⚠️ Only run one instance of the MCP server (either on Cursor or Claude Desktop), not both
Follow along with the setup instructions video
Download the AbletonMCP_Remote_Script/__init__.py file from this repo
Copy the folder to Ableton's MIDI Remote Scripts directory. Different OS and versions have different locations. One of these should work, you might have to look:
For macOS:
Contents/App-Resources/MIDI Remote Scripts//Users/[Username]/Library/Preferences/Ableton/Live XX/User Remote ScriptsFor Windows:
C:\ProgramData\Ableton\Live XX\Resources\MIDI Remote Scripts\C:\Program Files\Ableton\Live XX\Resources\MIDI Remote Scripts\
Note: Replace XX with your Ableton version number (e.g., 10, 11, 12)Create a folder called 'AbletonMCP' in the Remote Scripts directory and paste the downloaded '__init__.py' file
Launch Ableton Live
Go to Settings/Preferences → Link, Tempo & MIDI
In the Control Surface dropdown, select "AbletonMCP"
Set Input and Output to "None"
Once the config file has been set on Claude, and the remote script is running in Ableton, you will see a hammer icon with tools for the Ableton MCP.
Here are some examples of what you can ask Claude to do:
The system uses a simple JSON-based protocol over TCP sockets:
type and optional paramsstatus and result or messageContributions are welcome! Please feel free to submit a Pull Request.
This is a third-party integration and not made by Ableton.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.