musicbrainz-mcp
Related Servers
Alternatives to musicbrainz-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for querying the MusicBrainz database, providing tools to search for artists, releases, recordings, and browse music metadata.4MIT
- AlicenseNot gradedqualityAmaintenanceSearch artists, releases, recordings, works, and labels; traverse relationships; resolve ISRC/ISWC/barcode; fetch cover art via MCP. STDIO or Streamable HTTP.55 npm1Apache 2.0
- FlicenseNot gradedqualityBmaintenanceMCP server for DJs to scan music folders, validate and suggest metadata via MusicBrainz/iTunes/Spotify, and batch write metadata to audio files with confidence scoring.1-
- AlicenseAqualityAmaintenanceMCP server for Discogs that enables searching the catalog, managing collections and wantlists, and handling marketplace and orders via the Discogs API.304 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server for the Last.fm API, exposing artist, album, track, chart, and user data as read-only tools. Supports optional writes, auth, and experimental methods over stdio or HTTP.MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that enables searching books and authors, fetching editions, browsing subjects, and resolving cover images from Open Library.125 npm4Apache 2.0
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: search, lookup, browse, resolve, cover art, healthcheck, and three different write operations (tags, rating, collection). Search vs browse are explicitly differentiated as fuzzy ranked vs exact linked entities, so there is no real ambiguity.
All tools follow a consistent 'musicbrainz_' prefix with snake_case operation names (lookup, search, browse, resolve, submit_tags, etc.). The pattern is predictable and uniform across the set.
Nine tools is well-scoped for a MusicBrainz MCP server, covering the core read operations, healthcheck, and the most common authenticated write actions without unnecessary bloat.
The server covers lookup, search, browse, cover art, and user-contributed tags/ratings/collection modifications, which is strong for its domain. A minor gap is the lack of an endpoint to list a user's own collections to obtain their MBIDs, but this can be worked around from a collection URL.