theandrewstaker/mcp-midi-control

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。原文を見る

20 stars 6 forks 品質 82 トレンド 30NOASSERTION

MCP MIDI Control is a local Model Context Protocol (MCP) server that lets Claude, or any MCP host, control 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 device, so the same instruction and the same guarantees behave the same way whether you are talking to a guitar modeler or a synth: - 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. - 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. - Time-based settings prefer syncing to the song tempo, so a dotted-eighth delay stays a dotted-eighth delay.

README

以下は原文 README の抜粋です。原文を見る。

MCP MIDI Control

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

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 MCP 初心者？mcpskill.org のガイドから始めましょう →

設定

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