midifier
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MIDIFIER_HF_TOKEN | No | Hugging Face token needed to download transcription weights. | |
| MIDIFIER_MODEL_SIZE | No | Model size: 'small', 'medium', or 'large'. | large |
| MIDIFIER_API_KEY_HASH | No | When set, callers must present the key; the hash of the API key. | |
| MIDIFIER_MINIO_BUCKET | No | MinIO bucket name (required if storage backend is 's3'). | |
| MIDIFIER_DECODE_ATTEMPTS | No | Number of decode attempts per segment before a job fails. | 3 |
| MIDIFIER_SEGMENT_SECONDS | No | Length of each decoded segment in seconds. | 60 |
| MIDIFIER_STORAGE_BACKEND | No | Storage backend: 'local' or 's3'. | local |
| MIDIFIER_MAX_CONCURRENT_JOBS | No | Number of transcriptions that can run at a time. | 1 |
| MIDIFIER_MAX_DURATION_SECONDS | No | Longest song accepted in seconds. | 360 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| transcribe_audioA | Start transcribing a song into a multi-track MIDI file. Returns a job id to poll with |
| transcription_status | Check a transcription, including its place in the queue and estimated wait. |
| transcription_settings | Report how this instance is configured, and how busy it currently is. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no ambiguity between tools.
With a single tool, naming consistency is trivially maintained.
The server has only one tool, which is insufficient for the stated purpose. It references a polling tool that is not provided, making the interface incomplete.
The tool only starts a transcription job but provides no way to check status or retrieve results, leaving agents with a dead end. The domain requires at least a status-checking tool.