music-metadata-mcp vs Suno by Ace Data Cloud
music-metadata-mcp is an MCP server published by stevebirring-star. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Suno by Ace Data Cloud is an MCP server published by AceDataCloud. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-11. 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 |  music-metadata-mcp |   Suno by Ace Data Cloud |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 2.20.2 Downloads/month (npm): 1 517 Downloads/week (npm): 344 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2026.11.9.0 Downloads/month (PyPI): 6 639 Downloads/week (PyPI): 769 Forks (GitHub): 19 Stars (GitHub): 73 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 2026.11.9.0 Downloads/month (PyPI): 6 639 Downloads/week (PyPI): 769 Forks (GitHub): 19 Stars (GitHub): 73 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 | music-metadata-mcp | Suno by Ace Data Cloud |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 3 (worse) | 73 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 19 (better) |
| Last release (differs) | 2026-11-09 (worse) | 2026-11-10 (better) |
| Where it runs (differs) | On your machine (music-metadata-mcp) | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/stevebirring-star/music-metadata-mcp | github.com/acedatacloud/sunomcp |
| Changes in the last 7 days (differs) | 5 | 4 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 8 h ago, requires authentication |
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
music-metadata-mcp
MCP server for the FreqBlog Music API — 25 tools covering audio features, plain-language search by description, seedless discovery by tempo/key/genre/year, similar-sounding tracks from several seeds, honestly-labelled tags, recommendations (Spotify /recom
Suno by Ace Data Cloud
Create Suno music, lyrics and covers with Ace Data Cloud; retrieve the same task for results.
How to run each
music-metadata-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Suno by Ace Data Cloud As a remote MCP server
claude mcp add --transport http mcp-suno https://suno.mcp.acedata.cloud/mcpRequires: ACEDATACLOUD_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Suno by Ace Data Cloud 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 music-metadata-mcp publish no settings it asks for, so we do not compare settings.
What it can do: music-metadata-mcp · What it can do: Suno by Ace Data Cloud · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). 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.