Ableton MCP Server

AbletonMCP connects Ableton Live to Claude AI through the Model Context Protocol (MCP), allowing Claude to directly interact with and control Ableton

Local serverstdioPython

What is the Ableton MCP MCP server?

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, end-to-end track. Exposed over MCP by the ableton mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

  • Two-way communication — Connect Claude AI to Ableton Live through a socket-based server
  • Track manipulation — Create, modify, and manipulate MIDI and audio tracks
  • Instrument and effect selection — Claude can access and load the right instruments, effects and sounds from Ableton's library
  • Clip creation — Create and edit MIDI clips with notes
  • Arrangement view composition — Build full songs autonomously in Arrangement View, including sections like intro, buildup, drop, breakdown, and outro
  • Session control — Start and stop playback, fire clips, and control transport across Session View and Arrangement View

Adding it to your client

@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Its toolset

Everything the assistant can do here goes through one of these:

  • Prerequisites — If you're on Mac, please install uv as: brew install uv

Configuration

You will need one environment variable: ABLETON_MCP_DISABLE_TELEMETRY. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the ableton mcp mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ableton MCP's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by ahujasid; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
PrerequisitesIf you're on Mac, please install uv as: brew install uv

How to install the Ableton MCP MCP server

{
  "mcpServers": {
    "ableton": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"],
      "env": {
        "ABLETON_MCP_DISABLE_TELEMETRY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
ABLETON_MCP_DISABLE_TELEMETRYConfiguration value read at startup.Optional

Example prompts to try

  • Use Ableton MCP to Prerequisites.

Frequently asked questions

It connects Ableton MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Prerequisites) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Ableton MCP directly.