ScanSing: sheet music to MusicXML vs MusicXML Synthesizer
ScanSing: sheet music to MusicXML is an MCP server published by scansing.app. Marketplaces we read that list it: 1 (Official MCP Registry). MusicXML Synthesizer is an MCP server published by raulkivi. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  ScanSing: sheet music to MusicXML |  MusicXML Synthesizer |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 No figure published Not marked · First seen |
Listed Version: 0.2.3 Downloads/month (PyPI): 252 Downloads/week (PyPI): 190 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.2.3 Downloads/month (PyPI): 252 Downloads/week (PyPI): 190 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ScanSing: sheet music to MusicXML | MusicXML Synthesizer |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | Remote server (mcp.scansing.app/mcp) | On your machine (synth-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/friofry/music_recognition_api | github.com/raulkivi/sheet-music-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago, requires a key | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
ScanSing: sheet music to MusicXML
Sheet music (PDF, photo, scan) to MusicXML: recognise, describe, extract parts, transpose, MIDI.
MusicXML Synthesizer
Synthesizes audio from MusicXML, with voice-part selection and tempo control
How to run each
ScanSing: sheet music to MusicXML As a remote MCP server
claude mcp add --transport http scansing https://mcp.scansing.app/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
MusicXML Synthesizer As a local MCP server: PyPI package
claude mcp add --env "SYNTH_SOUNDFONT_PATH=<YOUR_SYNTH_SOUNDFONT_PATH>" --transport stdio synth-mcp -- uvx synth-mcpRequires: SYNTH_SOUNDFONT_PATH
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only ScanSing: sheet music to MusicXML has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of ScanSing: sheet music to MusicXML publish no settings it asks for, so we do not compare settings.
What it can do: ScanSing: sheet music to MusicXML · What it can do: MusicXML Synthesizer · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.