AbletonMCP

AbletonMCP connects Ableton Live to Claude AI through the Model Context Protocol (MCP), giving Claude direct, two-way control over your Live session. Create full arrangements, manipulate tracks, load instruments and effects, and compose music — all through natural language prompts.

• Features
• How It Works
• Installation
  • Prerequisites
  • 1. Install the MCP Server
  • 2. Install the Ableton Remote Script
  • 3. Configure Your AI Client
• Usage
• Example Prompts
• Troubleshooting
• Technical Details
• Telemetry
• Community
• Contributing

AbletonMCP has two components that work together:

1. Ableton Remote Script (AbletonMCP_Remote_Script/__init__.py) — A MIDI Remote Script installed inside Ableton Live. It opens a local TCP socket server and listens for JSON commands.
2. MCP Server (MCP_Server/) — A Python server implementing the Model Context Protocol. It connects to the Remote Script socket and exposes Ableton's capabilities as MCP tools to Claude.

Claude Desktop / Cursor
        │
        │  MCP (stdio/SSE)
        ▼
  MCP Server (Python)
        │
        │  TCP socket (localhost:9000)
        ▼
Ableton Remote Script
        │
        ▼
   Ableton Live

• Ableton Live 10 or newer
• Python 3.8 or newer
• uv package manager

Install uv for your platform:

# macOS (Homebrew)
brew install uv

# Windows / Linux
# See: https://docs.astral.sh/uv/getting-started/installation/

⚠️ Do not proceed without installing uv first.

npx -y @smithery/cli install @ahujasid/ableton-mcp --client claude

No installation needed — uvx downloads and runs ableton-mcp on demand. See client configuration below.

📹 Follow the video walkthrough

1. Download AbletonMCP_Remote_Script/__init__.py from this repository.
2. Create a folder named AbletonMCP inside Ableton's MIDI Remote Scripts directory and copy the file there.

Remote Scripts directory locations:

3. Launch Ableton Live.
4. Open Settings / Preferences → Link, Tempo & MIDI.
5. In Control Surface, select AbletonMCP.
6. Set Input and Output to None.

⚠️ Run only one instance of the MCP server at a time (Claude Desktop or Cursor, not both).

{
  "mcpServers": {
    "AbletonMCP": {
      "command": "uvx",
      "args": ["ableton-mcp"]
    }
  }
}

uvx ableton-mcp

{
  "servers": {
    "AbletonMCP": {
      "type": "stdio",
      "command": "uvx",
      "args": ["ableton-mcp"]
    }
  }
}

1. Make sure the AbletonMCP Remote Script is active in Ableton Live (the Control Surface indicator should appear).
2. Open Claude Desktop or Cursor — the MCP server starts automatically.
3. Look for the 🔨 hammer icon in the chat interface — this confirms MCP tools are available.
4. Start prompting Claude to control Ableton.

"Create an 80s synthwave track"
"Build a Metro Boomin style hip-hop beat"
"Create a full song with intro, buildup, drop, breakdown, and outro"
"Add a jazz chord progression to track 1"
"Load an 808 drum rack and create a 4-bar pattern"
"Add reverb and delay to the lead synth"
"Set the tempo to 128 BPM and create 8 bars of house music"
"Get information about the current session"
"Fire the clip in track 2, scene 3"

📹 Demo: 80s Synthwave track

Commands flow as JSON objects over a local TCP socket (default port 9000):

// Request
{ "type": "create_midi_track", "params": { "index": -1 } }

// Response
{ "status": "success", "result": { "track_id": "track_0", "name": "1-MIDI" } }

• Complex arrangements may need to be broken into multiple steps.
• Designed for Ableton's built-in devices and browser content; third-party plug-in automation support varies.
• Always save your project before running extensive AI-driven changes.

AbletonMCP collects anonymous usage data to help improve the tool:

• Which MCP tools are invoked (no content or project data)
• Session activity for active-user counts
• Aggregate error rates

No personal information, file names, audio content, or project details are ever collected.

Set any of these environment variables before starting the server:

export ABLETON_MCP_DISABLE_TELEMETRY=true

Or in your claude_desktop_config.json:

{
  "mcpServers": {
    "AbletonMCP": {
      "command": "uvx",
      "args": ["ableton-mcp"],
      "env": {
        "ABLETON_MCP_DISABLE_TELEMETRY": "true"
      }
    }
  }
}

Contributions are welcome! To get started:

1. Fork the repository
2. Create a feature branch: git checkout -b feature/my-feature
3. Commit your changes: git commit -m "feat: add my feature"
4. Push and open a Pull Request

Please open an issue first for substantial changes so we can discuss the approach.

Thanks to everyone who has contributed to this project!

_{Made with contrib.rocks}