Musescore Mcp

io.github.chrischallPublished by GitHub account chrischallv1.3.1Updated Nov 7, 2026

MuseScore for Claude — search sheet music and read score metadata via your signed-in browser

VerifiedSTDIODesktop onlyMedia & Design

Overview

AI-generated overview

A local MCP server that lets an assistant search sheet music and read score metadata through your signed-in browser.

What you can do
  • Search sheet music and retrieve score metadata through the user's signed-in browser session.
  • Write files only inside a configured output directory, with relative paths resolved against it.
  • Convert SVG output to PDF, reading only from that same output directory.
  • Connect to a local fetch proxy over a WebSocket port that can be overridden.
When to use it
Useful when you want an assistant to look up sheet music and pull score details while relying on an existing browser login instead of separate credentials.
Requirements
Runs as a local process on the user's machine via the npm package, so Node.js is needed; desktop only, no web executable. A signed-in browser session is used for access. Optional environment variables MUSESCORE_OUTPUT_DIR (defaults to the Downloads folder) and MUSESCORE_WS_PORT (default 37149).
Before you install
File-writing tools are restricted to MUSESCORE_OUTPUT_DIR, so point it at a directory you are comfortable having written to. Requests go through your signed-in browser session, so activity is tied to that account and may be visible to the site. The server declares no authentication of its own.

Installation

In SourceWeft

  1. Open Musescore Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

15
  1. v1.3.1LatestNov 7, 2026
  2. v1.3.0Nov 4, 2026
  3. v1.2.0Oct 20, 2026
  4. v1.1.9Oct 16, 2026
  5. v1.1.8Oct 10, 2026
  6. v1.1.7Oct 7, 2026
  7. v1.1.6Oct 5, 2026
  8. v1.1.5Oct 3, 2026
  9. v1.1.4Sep 28, 2026
  10. v1.1.3Sep 25, 2026
  11. v1.1.2Sep 23, 2026
  12. v1.1.1Sep 23, 2026
  13. v1.1.0Sep 20, 2026
  14. v1.0.0Sep 18, 2026
  15. v0.17.4Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.