A
licenseNot graded
qualityC
maintenanceA comprehensive MCP server for querying the MusicBrainz database, providing tools to search for artists, releases, recordings, and browse music metadata.
4
MIT
musicbrainz-mcp
by chrischall
Related Servers
Alternatives to musicbrainz-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceSearch artists, releases, recordings, works, and labels; traverse relationships; resolve ISRC/ISWC/barcode; fetch cover art via MCP. STDIO or Streamable HTTP.474 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-
- AlicenseAqualityDmaintenanceMCP server for Discogs that enables searching the catalog, managing collections and wantlists, and handling marketplace and orders via the Discogs API.3016 npmMIT
- AlicenseNot gradedqualityAmaintenanceAn 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.587 npm4Apache 2.0
TDQS
A4.3/5.0
Scored across 9 tools
Disambiguation4/5
Each tool has a distinct purpose: lookup (single entity by MBID), browse (paged linked entities), search (Lucene ranking), resolve (URL parsing), cover_art, three OAuth writes, and healthcheck. There is mild overlap between lookup and resolve (resolve is essentially URL-extraction + lookup) and between browse and search, but descriptions clearly differentiate ranked-fuzzy vs complete-paged semantics.
Naming Consistency4/5
All tools use a consistent musicbrainz_ prefix and snake_case, which is highly predictable. The verb portion mixes styles slightly (submit_tags, submit_rating, modify_collection vs noun-ish lookup, browse, search, resolve, healthcheck), but this is readable and largely intuitive.
Tool Count5/5
Nine tools is well-scoped for a MusicBrainz client covering reads, search, resolution, cover art, and the three OAuth write paths. No tool feels redundant or gratuitous, and nothing is obviously missing from the count.
Completeness4/5
The surface covers the core read lifecycle (search, lookup, browse, resolve, cover art) plus the realistic write operations MusicBrainz allows via OAuth (tags, ratings, collections) and a healthcheck. Minor gaps remain (e.g. no explicit release-group or genre-centric browse helper), but agents can work around them with lookup/browse and inc.
Maintenance
ActivityActive
ResponsivenessSyncing