Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
317-tool agentic MCP production system for Ableton Live 12 — device atlas, sample engine, composer
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"livepilot": {
"command": "npx",
"args": [
"-y",
"livepilot"
]
}
}
}Run this in your terminal
claude mcp add livepilot -- npx -y livepilotPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"livepilot": {
"command": "npx",
"args": [
"-y",
"livepilot"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"livepilot": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"livepilot"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account dreamrec, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.10.4) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Rystic
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Start, seed, clock, inspect and diff Rystic API simulators from your agent.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
██╗ ██╗██╗ ██╗███████╗██████╗ ██╗██╗ ██████╗ ████████╗
██║ ██║██║ ██║██╔════╝██╔══██╗██║██║ ██╔═══██╗╚══██╔══╝ ██║ ██║██║ ██║█████╗ ██████╔╝██║██║ ██║ ██║ ██║ ██║ ██║╚██╗ ██╔╝██╔══╝ ██╔═══╝ ██║██║ ██║ ██║ ██║ ███████╗██║ ╚████╔╝ ███████╗██║ ██║███████╗╚██████╔╝ ██║ ╚══════╝╚═╝ ╚═══╝ ╚══════╝╚═╝ ╚═╝╚══════╝ ╚═════╝ ╚═╝
Make the change. Hear what happened. Keep what works.
LivePilot connects an AI client to Ableton Live 12. Sketch ideas, edit the set, compare versions, and learn from the choices you keep.
474 tools · 57 domains · macOS + Windows
[!NOTE]
LivePilot works with any MCP client, including Claude Code, Claude Desktop, Codex,
Cursor, VS Code, and Windsurf. Changes inside the Live set use Ableton's undo stack.
Downloads, saved memory, library scans, and installer changes happen outside the set
and cannot be undone from Ableton.
[!WARNING]
LivePilot is moving quickly. Pin a version for repeatable studio or live-performance setups,
and check the changelog before updating.
The setup wizard installs the Ableton Remote Script, creates the Python environment, copies the Max for Live Analyzer, and checks the connection:
npx livepilot --setup
Using Claude Desktop? Download the latest livepilot- .mcpb from Releases and double-click it.
See Install for client-specific setup and manual options.
LivePilot now spends far less context describing itself and gives clearer answers about what it actually knows.
Previous release v1.29.0 introduced learned perceptual taste, honest confidence gates, optional CLAP distance, and named Arrangement locators.
Full details in the CHANGELOG.
LivePilot works at two levels: exact control when you know what you want, and informed help when you do not.
| Job | What LivePilot brings |
|---|---|
| Work directly in Live | Control transport, tracks, clips, notes, devices, routing, mixing, automation, and Arrangement View through explicit tools. |
| Find the right sound | Search Ableton's library, your own plugins and racks, local samples, and Splice before loading anything. |
| Listen before judging | Read live spectral data or analyze rendered audio, then compare the result with the state before the edit. |
| Explore safely | Preview alternatives, keep the winner, and route changes inside the set through Ableton's undo stack. |
| Learn your taste | Remember which moves, devices, and versions you keep across sessions without treating taste as a universal score. |
| Stay aware of the song | Track identity, open creative threads, section roles, and protected elements so local fixes do not flatten the whole piece. |
Under the hood: a 5,264-device atlas, 683 mapped drum kits, 29 sample-processing techniques, 44 semantic moves, real-time and offline listening, and 12 planning and evaluation systems. The sections below show how each part works.
Start with the language that fits the moment. Both routes reach the same tool surface.
*"Sound like J Dilla."* *"Make this feel more like Burial."* *"BoC-style pads."*
Use a producer or genre as shorthand for rhythm, density, space, texture, and device choices. LivePilot translates the reference into techniques rather than pretending to clone someone's identity.
*"Push the snare 4 ms early, keep the kick on-grid, add ±2 ms timing variation to the hats,
and cut 3 dB around 380 Hz on the snare."*
When the detail matters, name it: notes, milliseconds, dB, frequency, modulation depth, envelope shape, send level, automation curve, scale degree, or voice leading.
Most sessions use both. Start broad, listen, then get specific where the track needs it.
┌──────────────────────────────────────────────────────────────────────┐
│ │ │ KNOWLEDGE PERCEPTION MEMORY │ │ ────────────── ────────────── ────────────── │ │ │ │ Device Atlas 9-band FFT recall by mood, │ │ 5264 devices RMS / peak genre, texture │ │ 120 enriched pitch tracking 29 techniques │ │ 683 drum kits key detection replay into session │ │ │ │ Sample Engine Corpus Intelligence Taste Graph │ │ Splice (local SQLite) EmotionalRecipe move preferences │ │ Browser search GenreChain device affinities │ │ Filesystem scan PhysicalModelRecipe novelty tolerance │ │ 6 fitness critics AutomationGesture │ │ │ │ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │ │ │ Device │ │ M4L │ │ Technique │ │ │ │ Atlas │──│ Analyzer │──│ Memory │ │ │ └──────┬───────┘ └──────┬───────┘ └──────┬───────┘ │ │ │ │ │ │ │ ┌──────┴───────┐ ┌──────┴───────┐ ┌──────┴───────┐ │ │ │ Sample │ │ Corpus │ │ Composer │ │ │ │ Engine │ │ Intelligence│ │ Engine │ │ │ └──────┬───────┘ └──────┬───────┘ └──────┬───────┘ │ │ └─────────────────┼──────────────────┘ │ │ ▼ │ │ ┌─────────────────┐ │ │ │ 474 MCP Tools │ │ │ │ 57 domains │ │ │ └────────┬────────┘ │ │ │ │ │ Remote Script ──┤── TCP 9878 │ │ M4L Bridge ─────┤── UDP 9880 / OSC 9881 │ │ Splice (local) ─┤── SQLite (downloaded samples) │ │ │ │ │ ┌────────────────┐ │ │ │ Ableton Live │ │ │ │ 12 │ │ │ └────────────────┘ │ └──────────────────────────────────────────────────────────────────────┘
Remote Script (remote_script/LivePilot/) — A Python ControlSurface that runs inside Ableton's process. Listens on TCP 9878. All Live Object Model calls execute on Ableton's main thread via schedule_message. Detects Ableton version at startup and enables four capability tiers: Core (12.0+), Enhanced Arrangement (12.1.10+), Full Intelligence (12.3+), Collaborative (12.4+).
MCP Server (mcp_server/) — Python FastMCP server. Validates inputs, routes commands to the Remote Script over TCP, manages the M4L bridge, and runs the atlas, sample engine, composer, planning, and evaluation systems. This is what your AI client connects to.
M4L Bridge (m4l_device/) — Optional Max for Live Audio Effect on the master track. Provides deep LOM access through Max's LiveAPI that the ControlSurface API can't reach. UDP 9880 (M4L to server) carries spectral data and LiveAPI responses. OSC 9881 (server to M4L) sends commands. The 38 spectral/analyzer tools strictly require the bridge; device and sample tools that call the bridge also have graceful fallbacks, so core functionality works without it. Backed by 32 bridge commands for hidden parameters, Simpler internals, warp markers, display values, and Simpler warp / Compressor sidechain writes that live on child objects Python can't reach.
Device Atlas (mcp_server/atlas/) — In-memory indexed JSON database. 5264 devices with browser URIs (bundled baseline), 120 enriched with YAML sonic profiles (mood, genre, texture, recommended chains). 7 indexes: by_id, by_name, by_uri, by_category, by_tag, by_genre, by_pack. Reverse-index device_techniques_index.json powers atlas_techniques_for_device (146 cross-references across 58 devices). Device and preset choices resolve against the atlas before loading, which reduces guessed names and dead ends. v1.22.0+: run scan_full_library after install to index your packs, User Library, and plugins into ~/.livepilot/atlas/device_atlas.json — your personal atlas overrides the baseline and survives npm updates.
Sample Engine (mcp_server/sample_engine/) — Searches three sources simultaneously: BrowserSource (Ableton's library), SpliceSource (local Splice catalog via SQLite), FilesystemSource (user directories). Every result passes through a 6-critic fitness battery (key, tempo, spectral, genre, mood, technical). 29 processing techniques (Surgeon precision vs. Alchemist experimentation). Builds complete sample processing plans with warp, slice, and effect recommendations.
Splice Client (mcp_server/splice_client/) — Searches Splice's catalog through two layers: the local SQLite database (sounds.db, already-downloaded samples) and the live gRPC API (full catalog, including samples you haven't downloaded yet). The gRPC client auto-detects Splice's dynamic port via port.conf, handles self-signed TLS, and enforces
Only the beginning is shown; read the rest in the repo