EasyMuseMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MSCORE_BIN | No | Full path to the MuseScore executable (e.g. MuseScore4.exe on Windows). MuseScore is auto-detected from common paths; set this to override. |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| musescore_doctorA | Report whether the MuseScore CLI binary is available and which version is installed. |
| musescore_notation_referenceA | Return the compact score-notation cheat sheet. Read this before composing for the first time. |
| musescore_composeA | Build a real MuseScore score from compact text notation (see musescore_notation_reference). Writes MusicXML, then renders the requested formats with MuseScore. Returns output paths, a musical summary and any measure/notation warnings. |
| musescore_renderB | Export any score MuseScore can open (.mscz, .musicxml, .mid, .gp, …) to other formats, optionally a single page. |
| musescore_viewA | Render one page of a score to PNG and return it as an image so you can check the engraving yourself. |
| musescore_inspectA | Read title, composer, key, time signature, tempo, part list, page/measure count and duration from a score file. |
| musescore_transposeB | Transpose any score by a number of semitones (positive = up) and export the result. |
| musescore_extract_partsA | Generate one .mscz per instrument/part from a full score. |
| musescore_editA | Modify a score that already exists (any format MuseScore can open), at measure or element level. Operations run in order. Use this for fixes to an existing file instead of re-writing the whole piece. |
| musescore_joinA | Concatenate two or more scores that share the same part layout, e.g. to build a medley or append a second section. |
| musescore_openA | Open a score in the MuseScore desktop app so the user can look at or hand-edit it. |
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 11 tools
Each tool targets a clearly distinct action or lifecycle stage: check, reference, compose, inspect, render, view, transpose, extract, edit, join, and open. The closest overlap is render vs. view, but their outputs and purposes are explicitly differentiated (general export vs. page image inspection).
All tools share a consistent musescore_ prefix and are readable, mostly using verb-style names. A couple of tools are noun phrases (musescore_doctor, musescore_notation_reference), which is a minor deviation from the otherwise action-oriented pattern.
The server exposes 11 well-scoped tools, comfortably within the ideal range. Each tool covers a meaningful part of the MuseScore workflow without obvious redundancy.
The toolset covers the full practical lifecycle: setup check, notation guidance, composition, inspection, rendering, visual checking, transposition, part extraction, editing, joining, and opening in the desktop app. No significant operational gap is apparent for the stated purpose.