midi-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@midi-mcp list my MIDI ports and send a middle C note to channel 1"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
midi-mcp
MCP server that lets Claude control electronic music instruments via MIDI. Exposes tools for sending MIDI messages (notes, CC, program changes, pitch bend, sysex) to hardware synths and drum machines connected via USB or DIN MIDI.
Setup
Requires uv.
cd midi-mcp
uv syncRelated MCP server: FL Studio MCP
Usage
Add to Claude Code
claude mcp add midi-mcp -- uv --directory /path/to/midi-mcp run midi-mcpOr add manually to your MCP config:
{
"mcpServers": {
"midi-mcp": {
"command": "uv",
"args": ["--directory", "/path/to/midi-mcp", "run", "midi-mcp"]
}
}
}Run standalone
uv run midi-mcpTools
Tool | Description |
| List available MIDI output ports |
| Open a specific MIDI output port by name |
| Close the currently open port |
| Return current port name and connection state |
| Send Note On (channel, note, velocity) |
| Send Note Off (channel, note, velocity) |
| Send Control Change (channel, control, value) |
| Send Program Change (channel, program) |
| Send Pitch Bend (channel, value) |
| Send SysEx message (list of data bytes) |
Dependencies
mcp[cli] - MCP Python SDK with FastMCP
mido - MIDI message library
python-rtmidi - Real-time MIDI I/O backend
Available Tools
10 toolsclose_midi_portB
Close the currently open MIDI port.
Inputs: no named parameters.
get_midi_statusB
Return current MIDI connection status.
Inputs: no named parameters.
list_midi_portsB
List available MIDI output ports.
Inputs: no named parameters.
open_midi_portA
Open a MIDI output port by name. Use list_midi_ports to see available ports.
Inputs: name (required).
send_ccC
Send a MIDI Control Change message.
Args:
channel: MIDI channel (0-15)
control: CC number (0-127)
value: CC value (0-127)
Inputs: channel (required), control (required), value (required).
send_note_offA
Send a MIDI Note Off message.
Args:
channel: MIDI channel (0-15)
note: Note number (0-127)
velocity: Release velocity (0-127, usually 0)
Inputs: channel (required), note (required), velocity.
send_note_onA
Send a MIDI Note On message.
Args:
channel: MIDI channel (0-15)
note: Note number (0-127). 60 = middle C.
velocity: Velocity (0-127)
Inputs: channel (required), note (required), velocity (required).
send_pitchwheelA
Send a MIDI Pitch Bend message.
Args:
channel: MIDI channel (0-15)
value: Pitch bend value (-8192 to 8191, 0 = center)
Inputs: channel (required), value (required).
send_program_changeA
Send a MIDI Program Change message.
Args:
channel: MIDI channel (0-15)
program: Program number (0-127)
Inputs: channel (required), program (required).
send_sysexB
Send a MIDI System Exclusive message.
Args:
data: List of SysEx data bytes (0-127 each, without F0/F7 framing)
Inputs: data (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Each tool has a distinct purpose with no overlap: port management (list/open/close/status), and specific MIDI message types (note on/off, CC, pitch bend, program change, sysex). The descriptions clearly differentiate them, eliminating any ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., list_midi_ports, send_note_on). The verbs are appropriate and predictable across the set, making the naming highly consistent.
With 10 tools, this server is well-scoped for MIDI operations. It covers essential port management and a comprehensive set of MIDI message types, with each tool serving a clear and necessary function in the domain.
The tool set provides complete coverage for basic MIDI output: port lifecycle (list, open, close, status) and all standard message types (note on/off, CC, pitch bend, program change, sysex). There are no obvious gaps for the stated purpose.
Maintenance
Related MCP Connectors
MCP server for Producer/Riffusion AI music generation
OSC ↔ MIDI bridge for synthesizers and DAWs, with the SynthHub catalogue. A MIDI MCP and OSC MCP.
Remote MCP server for audio stem separation, denoise, reverb, and MIDI export.
AI image, video, voice and music generation over MCP, routed to Veo 3.1, Seedance 2.5 and more.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA FastMCP server that creates a virtual MIDI output port, allowing LLMs to generate and send MIDI data to any software that accepts MIDI input.17-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that connects Claude to FL Studio, allowing the AI to send melodies, chords, and drum patterns directly to the DAW via virtual MIDI ports.57-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects AI assistants to FL Studio for music production via Virtual MIDI. It enables users to control transport, manage the mixer, write notes, and manipulate plugin parameters through natural language.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI-powered music production by allowing Claude to control Bitwig Studio, including transport, mixer, and device controls.79MIT