原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Livepilot

作者:dreamrec版本 1.10.4i★ –i在你的电脑上运行
注册名称io.github.dreamrec/livepilot

安装

概览

作者提供的说明(英文原文)

317-tool agentic MCP production system for Ableton Live 12 — device atlas, sample engine, composer

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "livepilot": {
      "command": "npx",
      "args": [
        "-y",
        "livepilot"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add livepilot -- npx -y livepilot

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "livepilot": {
      "command": "npx",
      "args": [
        "-y",
        "livepilot"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "livepilot": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "livepilot"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 dreamrec 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 32564 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 32564 个服务器的 6% 更新
  • 基础检查结果等于或优于此分类中其他 32564 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Livepilot 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.10.4)于7个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Tools MCP

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新
安装

Tools MCP

作者:First-CH

Web production tools for AI agents: contrast, JP text, WebP, JSON-LD, slugs, dates and 40+ more

在你的电脑上运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

██╗     ██╗██╗   ██╗███████╗██████╗ ██╗██╗      ██████╗ ████████╗

██║ ██║██║ ██║██╔════╝██╔══██╗██║██║ ██╔═══██╗╚══██╔══╝ ██║ ██║██║ ██║█████╗ ██████╔╝██║██║ ██║ ██║ ██║ ██║ ██║╚██╗ ██╔╝██╔══╝ ██╔═══╝ ██║██║ ██║ ██║ ██║ ███████╗██║ ╚████╔╝ ███████╗██║ ██║███████╗╚██████╔╝ ██║ ╚══════╝╚═╝ ╚═══╝ ╚══════╝╚═╝ ╚═╝╚══════╝ ╚═════╝ ╚═╝

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.


Start Here

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.


What's New in v1.30.0

LivePilot now spends far less context describing itself and gives clearer answers about what it actually knows.

  • A focused first contact. Normal sessions advertise 28 useful entry points instead of sending all 474 schemas up front. The rest remain searchable and directly callable.
  • Options that mean something. Decorative Composer, Atlas, and routing parameters are gone; sample roles and material filters now change the result; unsupported abstract events fail with concrete guidance instead of disappearing silently.
  • Evidence with a label. Mix and evaluation reports separate measured audio, setup-derived heuristics, and artistic judgment. “Less bright” and other reduction goals now score in the right direction.
  • Depth when it earns its keep. Quick creative requests take a quick path. Three-way exploration, broad memory reads, and full critic passes are reserved for real ambiguity.
  • More resilient sessions. Startup no longer waits on optional services, ambiguous network failures do not replay destructive edits, and project memory follows the Live set rather than ordinary edits inside it.

Previous release v1.29.0 introduced learned perceptual taste, honest confidence gates, optional CLAP distance, and named Arrangement locators.

Full details in the CHANGELOG.


What LivePilot Does

LivePilot works at two levels: exact control when you know what you want, and informed help when you do not.

JobWhat LivePilot brings
Work directly in LiveControl transport, tracks, clips, notes, devices, routing, mixing, automation, and Arrangement View through explicit tools.
Find the right soundSearch Ableton's library, your own plugins and racks, local samples, and Splice before loading anything.
Listen before judgingRead live spectral data or analyze rendered audio, then compare the result with the state before the edit.
Explore safelyPreview alternatives, keep the winner, and route changes inside the set through Ableton's undo stack.
Learn your tasteRemember which moves, devices, and versions you keep across sessions without treating taste as a universal score.
Stay aware of the songTrack 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.


Two Ways to Talk to LivePilot

Start with the language that fits the moment. Both routes reach the same tool surface.

Route A — Artist / aesthetic shorthand

*"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.

Route B — Direct musical intent

*"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.

Mixing the routes

Most sessions use both. Start broad, listen, then get specific where the track needs it.


Architecture

┌──────────────────────────────────────────────────────────────────────┐

│ │ │ 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 │ │ │ └────────────────┘ │ └──────────────────────────────────────────────────────────────────────┘

How the pieces connect

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

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx