MIDI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_midiA | Generate a MIDI file from structured composition data with chord support. Supports single notes, note arrays (chords), and chord names (5, 6, 7, 9, 11, 13, maj, m, min, dim, etc.). Returns base64-encoded MIDI data and displays an interactive preview with piano-roll notation and playback. |
| parse_chordA | Parse a chord name and return its component MIDI pitches. Useful for understanding chord voicings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Harmony & Music Theory | Intervals, chord types, diatonic chords, cadences, and voice leading rules |
| Chord Progressions | Common progressions by mood/genre, substitutions, and modulation strategies |
| Counterpoint | Species counterpoint rules (Fux's five species), consonance/dissonance, motion types |
| Modes & Scales | Seven diatonic modes, minor scale variants, pentatonic/blues scales, genre guide |
| Orchestration | Instrument ranges, GM program numbers, four-part harmony ranges, texture types |
| Rhythm Patterns | Time signatures, MIDI duration reference, genre grooves, velocity and tempo guides |
| Voice Leading | Forbidden parallels, chord voicing strategies, non-chord tones, MIDI tips |
| MIDI Preview |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: create_midi generates MIDI files from composition data, while parse_chord analyzes chord names into pitches. No overlap or ambiguity exists.
Both tool names follow a consistent verb_noun pattern (create_midi, parse_chord), making the naming predictable and intuitive.
With only 2 tools, the server is minimal but appropriately scoped for a niche MIDI/chord utility. The low count is justified by the focused domain, though it is on the thin side.
The server covers generation of MIDI files and chord parsing, addressing its core purpose. Minor gaps like MIDI file reading or conversion exist, but they are not obvious omissions for the stated functionality.