← Back to directory
L

LivePilot

Community
Agentic production system for Ableton Live 12 — 472 tools, 57 domains
GitHub source repository ↗
★ 64 Stars Category · Dev Tools Popular Source revision 73f98c8960be
46FMRS · D
Reliability
8/20
Security and permissions
8/20
Maintenance
9/20
Documentation
12/20
Setup experience
9/20

LivePilot is a powerful agentic Ableton production system with a broad toolset, but it's specific to Ableton Live 12. It requires installing a Remote Script and optional M4L analyzer, and depends on a local Python environment. It's ideal for advanced users wanting AI-assisted composition, device recommendations, and creative exploration. Users should be aware of side effects (like Splice downloads) and its active development status.

Read the FMRS scoring method →

LivePilot is an agentic MCP server for Ableton Live 12, providing 472 tools across 57 domains. It integrates a device atlas (5264 devices), user corpus (detects and learns your third-party plugins), Splice intelligence (gRPC + GraphQL), 9-band spectral perception (auto-loaded), offline listening engine, Creative Director skill, technique memory, and 12 creative engines. All tools execute on Ableton's main thread through the official Live Object Model API; mutations go through Ableton's undo stack, while side effects outside the project (Splice downloads, memory/ledger writes, installer actions, atlas scans, filesystem writes) persist beyond undo. It works with any MCP client, including Claude Code, Claude Desktop, Cursor, and VS Code.

Tools

compose_fast_apply
Quick loop sketch: generate a single-scene loop from a text prompt.
compose_full_apply
Full track with song form: intro, verse, hook, breakdown, outro.
develop_apply
Develop an existing loop without disturbing seed material.
ensure_analyzer_on_master
Idempotent pre-flight: load M4L analyzer on master track if missing.
scan_full_library
Scan installed Ableton library and plugins to rebuild a personal device atlas.
corpus_setup_wizard
One-shot orchestration to run the full user corpus pipeline and synthesize plugin identity profiles.
atlas_transplant
Adapt a demo/preset to new BPM, scale, or aesthetic with PRESERVE/SCALE/REMAP/REPLACE decisions.
atlas_macro_fingerprint
Find similar presets across sidecars by macro fingerprint — 'more like this'.
listen_capture
Offline analysis of a rendered audio file: stereo width, bass-mono, groove microtiming, transient character, LUFS, etc.
listen_ab
A/B compare two rendered captures, returning audio quality snapshots.

Setup

  1. Run npx livepilot --setup (macOS) or double-click a .mcpb file for Claude Desktop. The setup wizard checks Python, installs the Remote Script, creates a Python environment, copies the M4L Analyzer, and tests the Ableton connection. 2. In Ableton Live 12, open Preferences → Link, Tempo & MIDI → Control Surface → select LivePilot. 3. For Claude Code, run claude mcp add LivePilot -- npx livepilot; for Claude Desktop, Cursor, and VS Code, use the install config JSON shown. 4. (Optional) Drag LivePilot_Analyzer.amxd onto the master track as the last device for spectral analysis. 5. Run npx livepilot --status to verify the connection.
claude_desktop_config.json
{
  "mcpServers": {
    "LivePilot": { "command": "npx", "args": ["livepilot"] }
  }
}

Fit and risk

Best for

  • Ableton Live 12 users who want an AI assistant for music production.
  • Producers needing intelligent device recommendations, sample analysis, and composition assistance.
  • Musicians who prefer controlling their DAW with natural language or artist/genre shorthand.
  • Advanced users who want the system to learn their personal plugin library.
  • Studios wanting AI-assisted mixing, sound design, and composition with deep integration.

Not for

  • Beginners unfamiliar with Ableton Live 12 (requires operating the DAW).
  • Users needing fully autonomous AI composition (LivePilot returns plans, not autonomous execution).
  • Users who only need simple MIDI control without complex tooling.
  • Those expecting a free commercial plugin (it uses BSL-1.1 license).
  • Users on other DAWs (Logic, FL Studio) — it only supports Ableton Live 12.

Required permissions

  • Communicates with Ableton Live 12 over TCP 9878 (requires Remote Script installation).
  • Communicates with the Max for Live analyzer over UDP 9880 and OSC 9881 (optional, for spectral tools).
  • Reads local Splice database files and communicates with the Splice desktop app over gRPC (optional).
  • Scans the filesystem for plugins and samples (requires user directory access).
  • Writes state files to `~/.livepilot/`, including atlas overlays, memory, and logs.
  • Makes changes to the Live session (tempo, tracks, devices) — all through the undo stack.

Risks and side effects

  • Modifies the Live session in real time, which may inadvertently change your project; backup recommended.
  • Splice interactions can consume credits on downloads; there's a safety floor of 5 credits, but still a risk.
  • The M4L analyzer listens on LAN (OSC 9881); unauthenticated commands are dropped since v1.28.0, but use trusted networks.
  • Filesystem scans can be time-consuming and expose plugin paths/names (privacy).
  • With many tools, mis-calling may lead to complex state changes; experimental in production sessions.
  • Actively developed; APIs may change frequently. Pin a version for stable work.

Troubleshooting

  1. Connection issues: run `npx livepilot --status` to check Ableton connection; ensure the Remote Script is installed and selected in Ableton.
  2. Spectral tools unavailable: make sure the M4L analyzer is loaded on the master track last and call `ensure_analyzer_on_master`.
  3. Splice search returns no results: ensure Splice desktop app is running and samples are downloaded; check gRPC/port config.
  4. Unexpected behavior: run `npx livepilot --doctor` for full diagnostics and check logs.
  5. Version issues: upgrade to latest version, note breaking changes in CHANGELOG.
  6. Installation problems: verify Python 3.12+, Node.js 18+, and Ableton Live 12 minimum requirements.

Use cases

Music production via natural language, e.g., 'make dark minimal techno at 128bpm'.
Use artist or aesthetic shorthand like 'sound like J Dilla' to guide device choices and processing.
Search devices, samples, and techniques with descriptive queries like 'warm pad'.
Generate song loops, full tracks, or extend existing ideas using the composer engines.
A/B evaluate rendered audio via the offline listening engine.
Search and download Splice catalog samples with plan-aware usage, and get processing plans.

Supported clients

Claude DesktopFull support
Claude CodeFull support
CursorFull support
VS CodeFull support