M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
L

LivePilot

Community
Agentic production system for Ableton Live 12 — 472 tools, 57 domains
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #295 of 438
Stars
★ 79 Popular
Transport
stdio (local process)
Runtime
Node.js 18+ · Python 3.12+
Credentials
No credential needed
License
Other / unspecified
Last commit
Tools
10
46FMRS · D

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.

Strongest · Documentation 12/20 Weakest · Reliability 8/20

Reliability
8/20
Security and permissions
8/20
Maintenance
9/20
Documentation
12/20
Setup experience
9/20
Why each score
Reliability 8/20
Evidence: The manifest claims 472 tools across 57 domains; the README describes a TCP 9878 Remote Script, UDP 9880/OSC 9881 M4L bridge, a file-based listening engine, and many version-specific fixes (event-loop offloading, stalled-stream detection, capture-pipeline timeout fixes). These narrative changelogs suggest active reliability engineering, but the manifest is the only machine-readable metadata; no repository files were supplied, so CI runs, committed tests, or actual tool-to-implementation consistency cannot be verified. Deductions: no verifiable evidence of committed tests or CI workflows; the target environment (Ableton 12, Python 3.12, Node 18+, OSC/M4L device) is complex with high failure potential; the static-review constraint caps the score at 12.
Security and permissions 8/20
Evidence: The v1.28.0 changelog details authentication for OSC 9881 — shared secret written to a 0600 file, rotated per startup, unauthenticated commands dropped — and a required re-freeze of the .amxd device. The README also discloses side effects beyond Live's undo stack: Splice downloads, memory/ledger writes, installer actions, atlas scans, filesystem writes. These are explicit data-flow disclosures, and downloads have a credit floor (CREDIT_HARD_FLOOR=5). Deductions: implementation is unverified from description alone; the TCP/OSC network surface can issue remote commands into a DAW with broad side effects; the license is BSL-1.1 (conflicting with the manifest's NOASSERTION, a governance inconsistency) and no security policy content was provided. No red line is triggered.
Maintenance 9/20
Evidence: The README shows frequent semver releases (1.27.x → 1.28.0) with substantial changelog entries, fixes from prior audits, and CI badges; 0 open issues are reported. Deductions: commit activity, release cadence, and CI status cannot be verified from the supplied materials; the license inconsistency (NOASSERTION vs BSL-1.1) and no verifiable security-response channel; v1.28.0 is very recent with no long-term track record established.
Documentation 12/20
Evidence: Documentation is extensive — architecture diagram, eight-layer description, tool-catalog reference, install instructions with JSON config snippets, CLI reference, compatibility table, version tiers, links to manuals/guides, and limitations (warnings about active development and pinning versions). Deductions: credentials/ports, tool parameters, and troubleshooting guides are only mentioned or linked, not included; the 472-tool count is claimed but only a curated list is shown; cost/limits are disclosed only for the Splice portion; link targets cannot be verified as real.
Setup experience 9/20
Evidence: Multiple paths are provided: MCPB one-click install, `npx livepilot --setup` wizard, manual Remote Script installation, and client config JSON examples for Claude Desktop/Code, Cursor, and VS Code. Prerequisites (Python 3.12+, Node 18+) are detected and clearly listed. Deductions: static review cannot verify the installers actually work; Ableton 12 plus optional M4L device/Splice app are required, so the out-of-box experience depends on an external DAW and external services; no output from the claimed verification commands (`--status`, `--doctor`) and no saved test/CI artifacts.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesUses the networkControls a browser

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.

Setup

Before you start

Runtime：Node.js 18+ · Python 3.12+

  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"] }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "LivePilot": {
      "command": "npx",
      "args": [
        "livepilot"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add LivePilot -- npx livepilot

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After install, LivePilot tools (e.g. ensure_analyzer_on_master, atlas_search) should appear in your MCP client's tool list, or run npx livepilot --status to confirm the Ableton connection.

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.

Things to try

Once connected, you can ask your AI assistant things like:

  • Make me a dark minimal techno loop at 128 BPM with industrial textures
  • Humanize the drum loop like J Dilla: 62% swing with ghost snares
  • Scan my installed plugins and build knowledge profiles for them
  • Capture a render and run an A/B comparison to check if the low end got tighter

Tools 10

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

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 Desktop
Claude Code
Cursor
VS Code

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision d2e0a7a725c8 Data synced 2026-10-11 Read the FMRS scoring method