A
licenseNot graded
qualityD
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.292 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.307 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.283 npm4Apache 2.0
TDQS
A4.4/5.0
Scored across 9 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: search, lookup by MBID, browse relationships, resolve URLs, cover art, health check, and three separate write operations (tags, rating, collections). No two tools overlap in function.
Naming Consistency4/5
All tools share the 'musicbrainz_' prefix and snake_case, and most are verb-led (browse, lookup, search, resolve, submit_tags, submit_rating, modify_collection). 'cover_art' and 'healthcheck' are nouns, creating a minor deviation from the verb-first pattern.
Tool Count5/5
Nine tools is well-scoped for a MusicBrainz client, covering read operations (search, lookup, browse, resolve, cover art, health check) and user-modifying operations (tags, ratings, collections) without unnecessary bloat.
Completeness4/5
The core read workflows and common user write actions are covered. Minor gaps include no way to list a user's own collections and no entity creation/editing, but these are edge use cases for a typical music lookup agent.
Maintenance
ActivityActive
ResponsivenessUnresponsive