Musescore Mcp
Search MuseScore and pull score metadata into your agent session using the browser session you already signed in with.
Overview
musescore-mcp is a MCP server for the Build phase that searches MuseScore and reads score metadata through your signed-in browser via fetchproxy.
What is this MCP server?
- Search sheet music on MuseScore from MCP tools
- Read score metadata via your signed-in browser session
- stdio npm package @chrischall/musescore-mcp (v0.9.0)
- Optional MUSESCORE_WS_PORT override (default fetchproxy port 37149)
- Depends on fetchproxy browser extension for authenticated requests
- Package version 0.9.0
- Default MUSESCORE_WS_PORT 37149 when overridden
- Transport: stdio npm @chrischall/musescore-mcp
What problem does it solve?
Agents cannot legally or reliably scrape MuseScore without your login, and manual copy-paste of score details slows music-related builds.
Who is it for?
Solo builders making music content, education tools, or arrangement assistants who already use MuseScore in the browser.
Skip if: Production backends that need stable server-side APIs, offline catalogs, or teams unwilling to run a browser bridge.
What do I get? / Deliverables
With the MCP server and fetchproxy extension running, the agent returns MuseScore search results and metadata aligned with your browser session.
- Agent-driven MuseScore search results
- Score metadata pulled from your authenticated session
- Configurable WebSocket port for fetchproxy (default 37149)
Recommended MCP Servers
Journey fit
Music catalog lookup is integration work while building content products, tutorials, or tools that reference sheet music—not launch or growth analytics. The server bridges MuseScore through a fetchproxy browser WebSocket rather than a standalone public API key flow, which is classic third-party integration plumbing.
How it compares
Browser-session MuseScore bridge, not the official MuseScore desktop API or a hosted sheet-music database.
Common Questions / FAQ
Who is musescore-mcp for?
It is for developers and creators using Claude or Cursor who need MuseScore search and metadata inside the agent while logged into MuseScore in the browser.
When should I use musescore-mcp?
Use it while building music-related features or content when fetchproxy can mirror your authenticated MuseScore session.
How do I add musescore-mcp to my agent?
Install @chrischall/musescore-mcp, configure the stdio MCP entry in your client, sign into MuseScore in the browser with fetchproxy enabled, and set MUSESCORE_WS_PORT only if needed.