TM

theandrewstaker/mcp-midi-control

开发工具

本页由 AI 翻译,技术细节请以原文为准。 查看原文

20 stars 6 forks 质量 82 趋势 30NOASSERTION

MCP MIDI 控制是一个本地模型上下文协议(MCP)服务器,允许 Claude 或任何 MCP 主机通过对话控制你的 MIDI 设备。

概览

MCP MIDI 控制是一个本地模型上下文协议(MCP)服务器,允许 Claude 或任何 MCP 主机通过对话控制你的 MIDI 设备。你用通俗易懂的语言说出你想要的话;服务器通过 USB 向硬件传达 SysEx、NRPN 和 CC,并读取以确认。 它对设备有严格的看法,所以无论你是在和吉他建模师还是合成器对话,相同的指令和保证都表现得一样: - 你只需传递并读取前面板上的数值(0到10旋钮、dB、ms、比率、枚举名称),绝不读取原始线字节或内部索引。- 除非你允许,否则不会保存、覆盖或导航离开你的编辑,每次写入都等待设备确认后才报告成功。- 基于时间的设置更倾向于与歌曲节奏同步,因此虚点八分音符延迟保持为虚点八分符延迟。

概述(AI 翻译)

一个有主见的MCP服务器,通过对话控制你的MIDI设备。

MCP MIDI 控制是一种本地模型上下文协议 (MCP)服务器,允许Claude或任何MCP主机通过以下方式控制你的MIDI设备 对话。你用通俗易懂的语言说你想说的话;服务员开口说话 通过USB将SysEx、NRPN和CC连接到硬件,然后读取确认。

它对每设备都有严格的看法,所以是一样的 无论你是,指导和相同的保证都一样 与吉他建模师或合成器交流:

  • 显示优先。 你传递并读取前面板上的数值(a 0到10的旋钮、dB、ms、比率、枚举名称),绝不使用原始线路字节或 内部指数。
  • 没有破坏性的事情悄无声息地发生。 它不会保存,不会覆盖, 或者除非你自己说可以,否则就不要再做编辑,每次写作都不行 等待设备确认后才报告成功。
  • 设备支持时优先节奏。 基于时间的设置更倾向于 与歌曲节奏同步,所以附点八分音符延迟保持 附点八分音符延迟。

通用MIDI原语(CC、NRPN、SysEx、程序变更、音符、时钟)

本页由 AI 翻译,技术细节请以原文为准。

README

以下为原文 README 节选,完整内容请查看原文。

MCP MIDI Control

An opinionated MCP server for controlling your MIDI gear by conversation.

MCP MIDI Control is a local Model Context Protocol (MCP) server that lets Claude, or any MCP host, control your MIDI gear by conversation. You say what you want in plain language; the server speaks SysEx, NRPN, and CC to the hardware over USB and reads it back to confirm.

It holds a set of strict opinions on every device, so the same instruction and the same guarantees behave the same way whether you are talking to a guitar modeler or a synth:

  • Display-first. You pass and read the values on the front panel (a 0 to 10 knob, dB, ms, a ratio, an enum name), never raw wire bytes or internal indices.
  • Nothing destructive happens silently. It does not save, overwrite, or navigate away from your edits unless you say so, and every write waits for the device to acknowledge it before reporting success.
  • Tempo-first when the device supports it. Time-based settings prefer syncing to the song tempo, so a dotted-eighth delay stays a dotted-eighth delay.

Generic-MIDI primitives (CC, NRPN, SysEx, program change, notes, clock) reach any USB MIDI device the OS exposes, so a Line 6 Helix, a Boss GT-1000, or any synth with a CC chart works from day one. A growing set of devices get first-class depth: whole-preset and patch authoring, real-gear lineage data, and cross-device tone translation.

Today the hardware-verified tier is the Fractal AM4, Fractal Axe-Fx II XL+, ASM Hydrasynth Explorer, and the Boss VE-500 vocal processor (core parameter set/read, bypass, user-memory recall, whole-patch build, and save are confirmed on the unit; factory-preset recall is wired but hardware- unverified, and whole-patch reads remain undone). In community beta: the modern Fractal family (Axe-Fx III / FM3 / FM9 / VP4), the original Axe-Fx Standard/Ultra, the Fractal AX8 floorboard (shares the Axe-Fx II codec), the Novation Circuit Tracks (groove + melody sequencing, sample and project upload, pack-addressed so a groove can target any storage pack, not only Pack 1), the Roland SPD-SX (kit and sample authoring over USB mass storage, plus pad triggering over MIDI), and the Boss RC-505mk2 and RC-600 loop stations (live memory recall and looper/track control over MIDI, plus reading and authoring a memory’s control assignments in its .RC0 files over USB mass storage). The Circuit can also sequence outboard gear (a programmed drum groove routed out to the SPD-SX’s pads, for instance) from one conversation.

Adding a device is a descriptor, not a new set of tools. Line 6 Helix and other

在 GitHub 查看完整 README

安装

This server does not publish a one-line install command.

Open the repository installation guide 新手?先看 mcpskill.org 教程 →

配置

{ "mcpServers": { "mcp-midi-control": { "command": "node", "args": ["C:\\path\\to\\mcp-midi-control\\packages\\server-all\\dist\\server\\index.js"], "env": {} } } }