Musicbrainz Mcp
Query MusicBrainz for artists, releases, and cover art—and optionally submit tags, ratings, and collections when OAuth is configured.
Overview
musicbrainz-mcp is a MCP server for the Build phase that searches and browses MusicBrainz metadata and cover art, with optional OAuth-backed tag, rating, and collection writes.
What is this MCP server?
- Search and browse MusicBrainz entities from MCP tools
- Fetch cover art via MusicBrainz-related cover art flows
- Read-only tools work with optional MUSICBRAINZ_USER_AGENT override
- Write tools need OAuth client ID, secret, and refresh token (tag/rating/collection scopes)
- stdio npm musicbrainz-mcp v0.2.0
- Server version 0.2.0
- npm identifier musicbrainz-mcp with stdio transport
- Write tools gated on MusicBrainz OAuth refresh token scopes
What problem does it solve?
Hand-coding MusicBrainz search, browse, and cover art calls in every agent task wastes time and duplicates OAuth handling for writes.
Who is it for?
Indie devs building music apps, agents, or media catalogs who want MusicBrainz and cover art without maintaining custom API glue.
Skip if: Teams that need streaming rights data, commercial charts, or zero dependency on community-maintained metadata.
What do I get? / Deliverables
After registering the stdio server—and OAuth vars if you need writes—the agent returns structured music entities and can update your MusicBrainz profile data.
- Structured MusicBrainz search and browse results in the agent
- Cover art retrieval for releases
- Optional tag, rating, and collection submissions via OAuth
Recommended MCP Servers
Journey fit
Canonical music metadata belongs in the build phase when you wire discography, attribution, or artwork into an app, bot, or content pipeline. MusicBrainz is an external open database integration with optional OAuth write scopes, fitting agent-tooling and backend integrations.
How it compares
Open MusicBrainz MCP connector, not a commercial music recognition API or local MP3 tagger skill.
Common Questions / FAQ
Who is musicbrainz-mcp for?
It is for builders using Claude Code or Cursor who need MusicBrainz search, browse, cover art, and optional personal tag or collection updates.
When should I use musicbrainz-mcp?
Use it during build integrations when you are modeling artists, releases, or artwork, or curating collections on MusicBrainz with OAuth configured.
How do I add musicbrainz-mcp to my agent?
Install the npm package musicbrainz-mcp, add it as a stdio MCP server, set MUSICBRAINZ_USER_AGENT if needed, and for writes register an OAuth app and provide client ID, secret, and refresh token env vars.