Log inSubmit server
Livepilot logo

Livepilot

Connects AI clients to Ableton Live 12 for set editing, sound search, mixing, analysis, and musical exploration.

InstallRepository
Full README Compare alternatives Embed widget Claim this listing

Install Livepilot

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "livepilot": {
      "command": "npx",
      "args": [
        "-y",
        "livepilot"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y livepilot

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 4d ago.

Overview

The livepilot MCP server connects AI clients to Ableton Live 12 for direct control of music projects. It exposes 474 tools across 57 domains for transport, tracks, clips, notes, devices, routing, mixing, automation, arrangement, sound search, audio analysis, and version exploration. A setup wizard installs the Ableton Remote Script, Python environment, and Max for Live Analyzer, with communication through TCP, UDP, OSC, and local SQLite components. Reach for it when an agent needs to make, inspect, compare, or refine changes inside an Ableton set on macOS or Windows.

Use cases

  • Edit tracks, clips, notes, and devices in an Ableton Live set
  • Search libraries, plugins, racks, samples, and Splice before loading sounds
  • Analyze rendered audio and inspect live spectral information
  • Compare creative alternatives and keep a preferred version
  • Refine timing, mixing, automation, and arrangement with exact instructions

Key features

  • 474 MCP tools across 57 domains
  • Ableton Live 12 control
  • Library, plugin, sample, and Splice search
  • Live and offline audio analysis
  • Version comparison and project memory
  • macOS and Windows support

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

8/8 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · livepilot (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars89Stargazers on the source repository.
npm downloads1.8kPackage downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.

How Livepilot works

What the livepilot MCP server does

The livepilot MCP server gives AI clients an MCP interface to Ableton Live 12. It supports both precise editing and higher-level musical requests. Agents can control transport, tracks, clips, MIDI notes, devices, routing, mixing, automation, and Arrangement View. They can also search Ableton’s library, local plugins and racks, local samples, and Splice before loading material.

The tool surface covers 474 tools grouped into 57 domains. Beyond direct set control, the system includes audio inspection and creative assistance. It can read live spectral information, analyze rendered audio, compare a result with the state before an edit, preview alternatives, and help retain a preferred version. Project memory can track open creative threads, section roles, protected elements, and choices kept across sessions.

How it works

LivePilot connects to Ableton through an installed Remote Script over TCP port 9878. A Max for Live bridge provides additional communication over UDP port 9880 and OSC port 9881. Local sample and Splice-related data uses SQLite for downloaded samples. The architecture also includes a device atlas, sample-processing knowledge, audio perception, corpus analysis, planning, evaluation, and memory systems.

Requests can be expressed as broad musical intent or exact parameters. For example, an agent may ask for a stylistic direction, or specify timing offsets, gain changes, frequency ranges, modulation, automation, or note behavior. Changes made inside the Live set use Ableton’s undo stack, allowing edits to be reversed through Live. Downloads, library scans, saved memory, and installer changes are outside that undo mechanism.

Setup and configuration

The livepilot MCP server includes a setup wizard invoked with:

Terminal
npx livepilot --setup

The wizard installs the Ableton Remote Script, creates the Python environment, copies the Max for Live Analyzer, and checks connectivity. Claude Desktop users can instead download the current .mcpb package from the project’s GitHub releases and open it directly.

For studio or live-performance systems, pinning a version is recommended because the project is changing quickly. Review the changelog before upgrading. The README identifies macOS and Windows as supported platforms.

Tools and capabilities

  • Control Live transport, tracks, clips, notes, devices, routing, mixing, automation, and arrangement.
  • Search Ableton content, plugins, racks, local samples, and Splice before loading sounds.
  • Inspect live spectral data and analyze rendered audio.
  • Compare edits with earlier state and preview alternatives before keeping a result.
  • Use device, drum-kit, sample-processing, and musical-technique knowledge.
  • Preserve project context and learn from versions or moves retained across sessions.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Livepilot

livepilot is an MCP server that connects AI clients to Ableton Live 12. Its main tools control transport, tracks, clips, notes, devices, routing, mixing, automation, and arrangement, while also supporting library and sample search, audio analysis, alternative comparison, and project memory across sessions.

Run `npx livepilot --setup` to use the setup wizard. It installs the Ableton Remote Script, creates the Python environment, copies the Max for Live Analyzer, and checks the connection. Claude Desktop users can also download the latest `.mcpb` release package and open it.

Yes, livepilot works with Cursor. The README also names Claude Code, Claude Desktop, Codex, VS Code, and Windsurf as compatible clients, and states that it works with any MCP client.

It can control transport, tracks, clips, notes, devices, routing, mixing, automation, and Arrangement View. It also supports sound searches, live spectral inspection, rendered-audio analysis, alternative previews, comparisons with earlier state, and memory of retained choices.

Related MCP servers

All in Multimedia Process All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLivepilot AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/livepilot?style=directory)](https://allmcps.com/mcp/livepilot)
HTML Embed
<a href="https://allmcps.com/mcp/livepilot"><img src="https://allmcps.com/api/badge/livepilot?style=directory" alt="Livepilot on AllMCPs" /></a>