MusicBrainz MCP By UnClick
Let your coding agent query MusicBrainz for canonical artist, release, and recording metadata while you build music apps, playlists, or catalog features without hand-wrangling IDs.
Overview
MusicBrainz MCP by UnClick is an MCP server for the Build phase that queries open MusicBrainz metadata for artists, releases, and recordings through your agent.
What is this MCP server?
- Search and resolve artists, releases, and recordings from open MusicBrainz data
- No MusicBrainz API key required for typical read/metadata use
- Shipped as @unclick/musicbrainz-mcp with stdio transport and npx install
- Version 0.1.0 in the official MCP server schema (2025-12-11)
- Maintained by UnClick alongside other standalone UnClick MCP packages
- Server version 0.1.0 per MCP server.schema.json
- npm package @unclick/musicbrainz-mcp with stdio transport
- Catalog description states no API key required for MusicBrainz access
Community signal: 4 GitHub stars.
What problem does it solve?
Building anything music-related without canonical artist and release IDs leads to duplicate entries, broken search, and hours of manual cleanup.
Who is it for?
Indie builders shipping music catalogs, discovery UIs, or agent workflows that need free, keyless read access to MusicBrainz.
Skip if: Teams that need licensed audio streaming, chart rankings, or guaranteed commercial SLA APIs instead of community metadata.
What do I get? / Deliverables
After you add the stdio server, your agent can fetch structured MusicBrainz entities on demand so features and content reference consistent metadata.
- Registered stdio MCP server pointing at @unclick/musicbrainz-mcp
- Agent-callable lookups for artists, releases, and recordings
- Structured metadata you can paste into app models or content pipelines
Recommended MCP Servers
Journey fit
External metadata APIs are wired during product build when agents and apps need live music entities, not during launch or ops tuning. This server is an MCP bridge to MusicBrainz—classic third-party integration work for agent-assisted backends and content tooling.
How it compares
MCP integration to MusicBrainz, not an agent skill or a hosted music streaming API.
Common Questions / FAQ
Who is MusicBrainz MCP By UnClick for?
Solo and indie developers using AI coding agents who want MusicBrainz artist, release, and recording data without building a custom API client themselves.
When should I use MusicBrainz MCP By UnClick?
Use it during build when you are implementing search, tagging, playlists, or CMS fields that must map to real-world music entities from MusicBrainz.
How do I add MusicBrainz MCP By UnClick to my agent?
Install @unclick/musicbrainz-mcp (npx / stdio per server.json), add the MCP server entry in Claude Code, Cursor, or your client’s MCP config, and restart the agent session.