Skip to main content
Glama
pnilan

midi-mcp

by pnilan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_midi_portsB

List available MIDI output ports.

open_midi_portA

Open a MIDI output port by name. Use list_midi_ports to see available ports.

close_midi_portB

Close the currently open MIDI port.

get_midi_statusB

Return current MIDI connection status.

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)
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)
send_ccC

Send a MIDI Control Change message.

Args:
    channel: MIDI channel (0-15)
    control: CC number (0-127)
    value: CC value (0-127)
send_program_changeA

Send a MIDI Program Change message.

Args:
    channel: MIDI channel (0-15)
    program: Program number (0-127)
send_pitchwheelA

Send a MIDI Pitch Bend message.

Args:
    channel: MIDI channel (0-15)
    value: Pitch bend value (-8192 to 8191, 0 = center)
send_sysexB

Send a MIDI System Exclusive message.

Args:
    data: List of SysEx data bytes (0-127 each, without F0/F7 framing)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 10 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness5/5

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

ActivityInactive
ResponsivenessNo issues

Resources