MusicBrainz MCP. Catalog every detail of an artist's discography.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
MusicBrainz connects your AI client directly to the world's largest open music database. Use it to search and catalog artists, albums, tracks, labels, and musical compositions by running natural language queries through specific tools.
No API key is required; just talk to your agent about music metadata.
What your AI agents can do
Browse releases by artist
Lists all album releases for a specific artist, showing titles, dates, countries, and labels.
Browse releases by label
Lists all album releases from a specific record label, detailing artists, dates, and countries.
Get artist
Retrieves detailed information for an artist by their unique MBID, including aliases and related works.
Get detailed profiles for artists, including their type, country of origin, active date range, and aliases.
Search for specific album versions, returning the title, release date, label name, and track count.
Pull metadata on a single track recording, including its duration, ISRC code, and which albums it belongs to.
Get detailed information about record labels, including their founding date and country of operation.
Find the metadata for a composition itself (the 'work'), separate from any recorded version.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
MusicBrainz MCP Server: 15 Tools for Music Data
Use these specialized tools to search every aspect of the music encyclopedia—from individual recordings to entire record label histories.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using MusicBrainz on Vinkius019d845bbrowse releases by artist
Lists all album releases for a specific artist, showing titles, dates, countries, and labels.
019d845bbrowse releases by label
Lists all album releases from a specific record label, detailing artists, dates, and countries.
019d845bget artist
Retrieves detailed information for an artist by their unique MBID, including aliases and related works.
019d845bget label
Gets detailed info about a record label using its MBID, including its founding date and type.
019d845bget recording
Retrieves data for an individual track recording by MBID, including ISRCs and the albums it appears on.
019d845bget release
Gets detailed information about a specific album release by MBID, listing tracks, labels, and artists.
019d845bget release group
Retrieves info for canonical groups of albums or singles using an MBID, useful for tracking EPs.
019d845bget work
Gets details on a musical composition itself by MBID, identifying the original writers and ISWC code.
019d845bsearch areas
Searches for geographic areas—like countries or cities—to get their official IDs for filtering other searches.
019d845bsearch artists
Finds music artists using advanced search queries, returning names, types, and active dates (max 100 results).
019d845bsearch labels
Searches for record labels by name or type, providing country details and founding dates.
019d845bsearch recordings
Finds individual track recordings using keywords, returning titles, artists, durations, and ISRCs (max 100 results).
019d845bsearch release groups
Searches for canonical album or single groups by title and artist to find the official version.
019d845bsearch releases
Finds specific album releases using filters like country, label, or status (official/bootleg).
019d845bsearch works
Searches for musical compositions (the 'work') by title or writer, separate from any recording.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with MusicBrainz, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by MusicBrainz. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 15 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Manually tracking an artist's discography is a nightmare of spreadsheets and copy-pasting.
Today, if you're archiving music for a client, you spend hours jumping between different databases. You find Artist A on one site, their albums are listed with dates, but the label information is missing. Then you have to open another tab to check the label, only to realize the data formats don't match up.
With this MCP server, your agent handles the jumps. You tell it which artist and timeframe you care about. It runs `browse_releases_by_artist`, grabs all the album titles, dates, and labels into one structured response. You just get clean, machine-readable data.
MusicBrainz MCP Server: Get complete metadata on artists.
The biggest time sinks are cross-referencing works versus recordings. Some databases treat a 'work' (the original song) and a 'recording' (a specific studio version) as two separate things, forcing you to check multiple endpoints just to link them up.
This server handles the distinction automatically. You can find the core composition using `search_works` and then trace every single recorded instance of it using its associated data points. It’s a complete picture.
What you can do with this MCP connector
Listen up. This server connects your AI client right to MusicBrainz, which is basically the world’s biggest open database for music metadata. You ain't gotta mess with any API keys or nothing—you just talk to your agent about music, and it handles the rest.
Identifying Artists & Works
Ya can get detailed profiles on artists using get_artist if you feed it their unique MBID; this pulls up aliases and all their related works. Need to track down a band? Use search_artists with advanced queries, which returns names, types, and even active date ranges—you'll get up to 100 results.
If you’re hunting for the original composition itself—the actual 'work,' separate from any recording—run search_works; this lets you find details by title or writer, giving you the ISWC code and identifying the original writers.
Tracking Releases & Recordings
To scope out an album version, start with search_releases, which lets you filter albums using criteria like country, label name, or if it's marked as official or a bootleg. Once you have a specific album MBID, get_release pulls all the deep details: track listings, labels involved, and artists credited. You can also use search_recordings to find individual tracks using keywords; this returns titles, artists, durations, and ISRCs, capped at 100 results.
For a single recording's full data dump—including its ISRC codes and which albums it belongs to—use get_recording with the MBID. If you wanna track down EPs or singles that span multiple releases, check out get_release_group, which uses an MBID to get info on canonical groups of albums or singles.
Mapping Labels & Sources
Need to know about a record company? search_labels lets you hunt for labels by name or type, spitting out country details and founding dates. If you have the label’s unique MBID, get_label gives you detailed info, including its type and when it was founded. For finding specific album versions from a source, run browse_releases_by_label, which lists all releases tied to that record company, detailing artists, dates, and countries.
Conversely, if an artist is the focus, use browse_releases_by_artist to list every single album release for them, showing titles, dates, countries, and labels.
Pinpointing Locations & Groups
If you gotta filter your searches by geography, run search_areas; this pulls up official IDs for places like countries or cities that you can then feed into other searches. To find the definitive version of an album group—say, a canonical single or EP—use search_release_groups with just the title and artist name.
How Ya Use It
You don't gotta build complex queries. You just tell your agent what you need. For example, if you ask it to 'find all Pink Floyd albums from 1973,' your AI client runs search_releases through the right filters and spits out structured data directly in the chat. If you wanna know about a track's history, you just say, 'what are the details for this recording MBID?' and it hits the database.
It’s all about natural language input; the agent handles the metadata lookup.
019d845b-fc8c-71f5-bb7c-d7853b5f2cd0 
How MusicBrainz MCP Works
- 1 Subscribe to this server. No API key setup is needed.
- 2 Ask your AI client a natural language query, like "Show me all albums for The Beatles in the UK."
- 3 The agent selects and runs the appropriate tool (e.g.,
search_releases), delivering structured results directly into your chat.
The bottom line is you get clean, structured music data from a massive global encyclopedia without writing complex API calls.
Who Is MusicBrainz MCP For?
Music curators, archivers, and metadata analysts. If your job involves tracking discographies or cataloging media history, this server is for you. Stop manually cross-referencing Discogs pages; let your agent handle the heavy lifting.
Use search_artists and get_artist to build structured artist records, ensuring every alias and country detail is captured for a database upload.
Pull release data using browse_releases_by_artist or search_releases to document an artist’s complete discography timeline, from early EPs to modern reissues.
Use the server to verify facts about musical works or labels. For example, checking a label's founding date via get_label before writing an article.
What Changes When You Connect
- Deep Artist Profiles: Use
get_artistto pull comprehensive data on any musician, including all known aliases and their full life span. You don't have to piece together these facts manually. - Discography Mapping: Need a complete list of an artist’s works? Running
browse_releases_by_artistprovides every album release across multiple countries and labels in one go. - Composition vs. Recording: The server separates the 'work' from the recording via
get_work. This lets you track the original composition (like a symphony) even if the specific recordings change. - Targeted Searching: Don't sift through junk data. Use
search_recordingsorsearch_releasesto filter results immediately by ISRC, country, or status (e.g., only bootlegs). - Label Context: Quickly establish a label’s history and scope using
get_label. You find the founding date and type without leaving your chat window. - Structured Discovery: The tools allow you to map out complex relationships—for instance, finding an album group via
search_release_groupsbefore pulling specific release details withget_release.
Real-World Use Cases
Verifying a Band's Full History
A music journalist is writing about the evolution of a group. They ask their agent to run search_artists for 'The Who.' The agent returns the MBID and basic stats, which they then feed into browse_releases_by_artist. This gives them a chronological list of every release date and label, ensuring no album is missed.
Cataloging Rare Tracks
A collector finds an obscure track. Instead of searching general forums, they use search_recordings with the song title and approximate duration. The agent returns the ISRC code, which can then be used to run get_release for all known parent albums.
Building a Label Profile
You need data on an indie label's history. You use search_labels to verify the official name and founding date. Then, you run browse_releases_by_label to pull every artist associated with that label into one document.
Tracking Original Compositions
You are researching a composer's body of work. You use search_works first, which identifies the composition itself (the 'work'). This lets you track the original notes and writers without getting confused by hundreds of different recorded versions.
The Tradeoffs
Searching only by name
Asking the agent, "Show me all albums for Pink Floyd." This is too vague; it might pull results from multiple sources or fail if they have aliases.
→
First, run search_artists for 'Pink Floyd' to confirm the correct MBID. Then, use that specific ID with browse_releases_by_artist. Always start by identifying the core entity.
Assuming one tool covers everything
Trying to find a track’s label just by searching for the song title in general. You might get unrelated results.
→
Use search_recordings first to pinpoint the specific recording and its MBID. Then, use that record's ID with get_release or get_recording to pull accurate parent label data.
Ignoring geographical context
Querying for a release without specifying the country, potentially mixing up different versions (e.g., US vs. UK vinyl).
→
Always run search_areas if geography matters. Then, include the specific area ID in your search query (search_releases) to narrow down results immediately.
When It Fits, When It Doesn't
Use this server when you need structured, verifiable metadata about recorded music—anything from a band's full discography to a label's history. If your goal is simply general web research or finding out who played at a concert last night, use Google. Use this if you need specific relationships: e.g., 'What track belongs to which album?' (Use get_release). Don't rely on one single search tool; the best approach is always layered: start with search_artists or search_releases for discovery, and then use a detailed lookup tool like get_artist to nail down the final data points. This combination ensures you mitigate ambiguity while maintaining precision.
Common Questions About MusicBrainz MCP
How do I search for an artist's discography using the get_artist tool? +
The get_artist tool provides comprehensive details, but to see all their albums, you should pair it with browse_releases_by_artist. This combination gives you a full list of releases and labels.
Is there a way to find an album group without knowing the exact release ID? +
Yes. Use search_release_groups first. It helps you locate the canonical or official grouping for albums, singles, or EPs before you look up specific releases.
Can I search by label name and get all associated artists? +
Yes, run search_labels to find the correct label ID. Then use that ID with browse_releases_by_label to pull every artist linked to that record label.
What is the difference between search_works and get_work? +
The search_works tool finds potential works based on titles or writers. The get_work tool requires you to provide a specific MBID so it can retrieve all confirmed details for that single composition.
Do I need an API key or special credentials when calling `search_artists`? +
Nope, you don't need any keys. Vinkius handles authentication for the whole server. Just connect your AI client and start using the tool; it works immediately.
If I use `search_releases`, how do I handle pagination when I expect more than 100 results? +
The tools return a maximum of 100 records per call. You'll need to run the tool multiple times, using the provided offset or next page ID from the response payload each time.
What is the best way to find a specific track version using `search_recordings`? +
You should use the ISRC (International Standard Recording Code) as your primary search parameter. This lets you pinpoint an exact recording, regardless of which album it appears on.
What's the difference between running `search_artists` and calling `get_artist`? +
search_artists finds candidates using keywords, returning a list of potential IDs. Use get_artist when you already have an Artist MBID; it pulls all detailed data for that single ID.
Do I need an API key? +
No! MusicBrainz is completely free and open. No authentication required. Just subscribe and start searching. Rate limit is 1 request per second.
What is an MBID? +
MBID stands for MusicBrainz Identifier — a unique UUID assigned to every entity in the database (artists, releases, recordings, labels, works). Use search tools to find MBIDs, then use get_* tools with the MBID for detailed info.
What's the difference between a release and a release group? +
A release is a specific physical or digital version of an album (e.g. the 2012 remastered CD). A release group groups all versions of the same album together (e.g. "The Dark Side of the Moon" as a canonical work). Use release groups for finding the canonical album.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.