Сервер Model Context Protocol (MCP), обеспечивающий программное управление MuseScore через систему плагинов на базе WebSocket. Это позволяет AI-ассистентам, таким как Claude, сочинять музыку, добавлять тексты, перемещаться по партитурам и управлять MuseScore напрямую.

Предварительные требования

• MuseScore 3.x или 4.x
• Python 3.13+
• Claude Desktop или совместимый клиент MCP

Подготовка

1. Установите плагин MuseScore

Во-первых, сохраните код плагина QML в папку плагинов MuseScore:

macOS: ~/Documents/MuseScore4/Plugins/musescore-mcp-websocket.qml Windows: %USERPROFILE%\Documents\MuseScore4\Plugins\musescore-mcp-websocket.qml Linux: ~/Documents/MuseScore4/Plugins/musescore-mcp-websocket.qml

2. Включите плагин в MuseScore

1. Открыть MuseScore
2. Перейдите в Плагины → Менеджер плагинов
3. Найдите «MuseScore API Server» и отметьте галочку для его включения
4. Нажмите OK

3. Наладить Claude Desktop (с помощью uv)

Установите uv. Он создаёт и кэширует среду Python при первом запуске, так что управлять venv нет, и конфигурации не требуется путь .venv.

Самый быстрый способ — позволить FastMCP написать для вас конфигурацию Claude Desktop:

MuseScore MCP Server

A Model Context Protocol (MCP) server that provides programmatic control over MuseScore, via a WebSocket-based plugin system. This allows AI assistants like Claude to compose music, add lyrics, navigate and analyse scores, restructure them with repeats, and mark them up with colors and highlights, directly in MuseScore.

What you can do

Ask Claude in plain language; it picks the tools. For example:

• Compose and edit: “Write a C major arpeggio in bar 3”, “Add the lyrics ‘Twin-kle twin-kle’ from bar 1”, “Set the tempo to 90 at bar 17”.
• Read large scores: the score is read 16 bars at a time as compact LilyPond, optionally only some staves, so even a 20-staff score fits.
• Compress a score with repeats: “Find the repeated passages and put them between repeat barlines”. The server finds bars and passages that repeat, adds repeat barlines, 1st/2nd endings and play counts, and removes the duplicate bars.
• Build drum charts: “Map the sections of the drum part” gives a road map (groove bar, exact and near copies, fills, and where the crashes fall). “Turn the copies into repeat signs” writes 1-, 2- or 4-bar measure-repeat signs automatically. “Make a drums-only chart with the groove written once and a 7x count” copies the score, keeps only the drums and collapses each run of identical bars. With the drum-chart skill, “make a drum chart from the open score” runs the whole workflow (see the example use case).
• Keep the song’s bar numbers: “Number the bars as played” makes the displayed numbers count repeated bars, so a compact chart still matches the original song.
• Highlight and color: “Highlight the crash hits”, “Box the dynamics”, “Highlight the repeat signs and time signatures in light blue”, “Color the fill on beats 3-4 of bar 13 green”, “Label bar 6 ‘Groove x7’”, “Add these cues in small grey italics at the start of each section: …”.
• Finish the page: “Tidy the title and call it a drum chart” cleans up the title frame; “Print what changed at the end” adds a summary of the differences from the original after the last bar, so it ends up in the PDF.
• Iterate: everything the tools add can be removed again (“remove the ** marks”, “clear the crash highlights”, “reset the bar numbers”), so you can refine the result step by step.

Requirements

• MuseScore 4.7 or newer. See Version requirements.
• uv, which installs Python 3.13 or newer for you. Without uv you need Python 3.13+ and pip; see Setup and running.
• An MCP client, such as Claude Desktop or Claude Code.

Quick start

1. Get the code and its dependencies (uv also installs a matching Python if needed):

   git clone https://github.com/ghchen99/mcp-musescore.git
   cd mcp-musescore
   uv sync