4,500+ servers built on MCP Fusion
Vinkius

MusicBrainz Alternative MCP. Query structured metadata using ISRC, ISWC, and advanced search.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MusicBrainz Alternative MCP on Cursor AI Code Editor MCP Client MusicBrainz Alternative MCP on Claude Desktop App MCP Integration MusicBrainz Alternative MCP on OpenAI Agents SDK MCP Compatible MusicBrainz Alternative MCP on Visual Studio Code MCP Extension Client MusicBrainz Alternative MCP on GitHub Copilot AI Agent MCP Integration MusicBrainz Alternative MCP on Google Gemini AI MCP Integration MusicBrainz Alternative MCP on Lovable AI Development MCP Client MusicBrainz Alternative MCP on Mistral AI Agents MCP Compatible MusicBrainz Alternative MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

MusicBrainz Alternative connects your AI agent directly to a structured music encyclopedia database. You can look up recordings using ISRC, find works by ISWC, or search artists across millions of records using Lucene query syntax.

It also lets you manage personal collections—adding tags, ratings, and items.

What your AI agents can do

Add collection items

Adds a music item to your personal collection (requires authentication).

Browse entities

Lists all related entities (like releases) connected to one primary entity.

Lookup discid

Finds metadata for a CD using its specific DiscID number.

+ 7 more capabilities included
Search by Unique ID

Finds a specific entity (artist or release) using its unique MusicBrainz Identifier (MBID).

Lookup via Industry Standards

Retrieves full metadata for recordings using an ISRC code, or finds works using an ISWC code.

Advanced Entity Search

Runs complex searches across the entire database using Lucene query syntax (e.g., combining keywords and fields).

Browse Linked Records

Lists all associated releases or recordings linked to a primary entity, like an artist.

Manage Collections

Adds items, submits tags, or updates ratings for a user's personal music collection (requires authentication).

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

MusicBrainz Alternative: 10 Tools for Music Data Management

These tools let you query, search, and modify structured music metadata using industry standards like ISRC and ISWC.

add019e5d38

add collection items

Adds a music item to your personal collection (requires authentication).

browse019e5d38

browse entities

Lists all related entities (like releases) connected to one primary entity.

lookup019e5d38

lookup discid

Finds metadata for a CD using its specific DiscID number.

lookup019e5d38

lookup entity

Retrieves all details for any MusicBrainz entity given its unique MBID.

lookup019e5d38

lookup isrc

Looks up a recording's metadata using its International Standard Recording Code (ISRC).

lookup019e5d38

lookup iswc

Retrieves details about a musical work using its International Standard Musical Work Code (ISWC).

remove019e5d38

remove collection item

Deletes an item from your personal collection (requires authentication).

search019e5d38

search entities

Searches for any entity using advanced Lucene query syntax, allowing complex filtering.

submit019e5d38

submit ratings

Submits a rating for an item in your collection (requires authentication).

submit019e5d38

submit tags

Adds descriptive tags to an item in your collection (requires authentication).

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
Start building

Make Your AI Do More

Start with MusicBrainz Alternative, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ 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

What you can do with this MCP connector

This server connects your AI agent right into a massive, structured music encyclopedia database. You don't just query it; you use it like a deep-dive research tool for anything related to recorded sound or musical works.

When you're trying to find something specific, you’ve got three main ways to kick off the search. First, you can run complex queries across the entire catalog using search_entities. This lets your agent combine keywords and fields—you can filter records down to a precise combination of terms, making sure you hit exactly what you're looking for.

If you know the unique identifier, things get faster. Use lookup_entity with a MusicBrainz Identifier (MBID) to pull every single detail about any entity—whether it’s an artist, album, or label. For records connected by industry standards, you got specific tools too. You can run lookup_isrc using an International Standard Recording Code (ISRC) to get all the metadata for a recording.

If you're tracking down the original composition, use lookup_iswc with an International Standard Musical Work Code (ISWC). For physical media checks, lookup_discid finds the full details on a CD using its specific DiscID number.

Once you find one entity—say, a primary artist or a release—you don't stop there. You can use browse_entities to list every single associated record or release linked back to that main entry. This builds out a whole relationship map for your agent.

If the data is good, you need to manage it in your own workspace. The server gives you tools to handle personal collections. If you're authenticated, your agent can use add_collection_items to drop an item into your list. You can also mark items with descriptive tags using submit_tags, or grade them by running submit_ratings.

When the item is wrong or outdated, you can clean things up with remove_collection_item.

When your agent performs these actions—retrieving data via unique IDs, executing complex Lucene searches, fetching metadata through ISRC/ISWC codes, listing related releases, or managing your personal collection records—it’s giving you structured data. It's not just a list of facts; it's actionable intelligence about the music world.

How MusicBrainz Alternative MCP Works

  1. 1 First, subscribe to the server and provide your required User Agent string. You might also need an Access Token if you plan on modifying data.
  2. 2 Next, direct your AI client to use a specific tool—for example, running lookup_isrc with a code or using search_entities with Lucene syntax.
  3. 3 The server returns clean, structured JSON metadata that your agent can read and act on. You're done.

The bottom line is: it turns complex database queries into simple function calls for your AI client.

Who Is MusicBrainz Alternative MCP For?

Music researchers, data scientists, and content curators who need precise metadata. If you're tired of manually cross-referencing release dates or struggling to link an obscure track back to its original work ID, this is for you. You get structured data without manual scraping.

Music Journalist

Verifies historical album credits and precise release dates when writing about niche artists.

Data Scientist

Queries structured music data using ISRC or ISWC codes to build training sets for classification models.

Archivist/Curator

Manages and tags large digital collections, submitting ratings and metadata directly from an agent workflow.

What Changes When You Connect

  • Precision lookups are instant. Instead of relying on vague web searches, you use lookup_isrc or lookup_iswc to pull hard data based on industry-standard codes.
  • You can map relationships easily. Use browse_entities to list every known release associated with a specific artist's MBID—no manual browsing required.
  • Complex searching is simple. The search_entities tool lets you combine multiple criteria (like 'Daft Punk' AND 'French') using Lucene syntax, getting highly filtered results right away.
  • Manage your data workflow end-to-end. Beyond just reading, authenticated tools like submit_tags and submit_ratings let your agent manage a personal library.
  • Cross-reference records easily. If you have an album's DiscID but need the artist's full profile, use lookup_discid to get the necessary link data.

Real-World Use Cases

01

Verifying Artist Credits for a Historical Article

A journalist needs to confirm the exact release date and primary label for an obscure 1980s recording. They use lookup_isrc with the known ISRC code, which immediately returns the album details, confirming the date without needing to guess which database is right.

02

Building a Catalog of Related Works

A developer needs to build an application that lists all recordings tied to one specific record label. They use browse_entities on the label's MBID, automatically generating a list of every associated artist and album for their database.

03

Cleaning Up Personal Music Libraries

A collector wants to tag hundreds of records with genre notes. They run an agent that iterates through items and uses submit_tags and submit_ratings, making the whole process automated instead of tedious manual entry.

04

Finding a Record When Only the CD ID is Known

You only have a physical CD with a DiscID. Instead of searching by name, you run lookup_discid. The tool pulls up all the necessary metadata—artist, title, and release year—in one clean action.

The Tradeoffs

Searching for everything with general keywords

Just asking the agent: 'Tell me about French electronic music.' This is too vague; it'll give a huge list of possibilities and you won't know where to start.

Use search_entities and refine your query. Try something structured like: "electronic AND France AND genre:house". That forces the database to filter correctly.

Confusing entity lookup with browsing

Trying to find a specific album using only lookup_entity when you actually only know the artist's name. You might get too much data or the wrong record.

If you know the unique ID (MBID), use lookup_entity. If you have an entity and want all related releases, always start with browse_entities.

Manually linking data points

Copying a release date from one website and then trying to paste it into another system. This is slow and prone to human error.

Use the server's tools. Pull everything you need—the ISRC, the release date, the artist MBID—in structured JSON output using multiple calls in sequence.

When It Fits, When It Doesn't

Use this MCP Server if your workflow requires absolute precision and structured data types. You need to look up records based on industry standards like ISRC or ISWC, or you need to perform highly filtered searches using Lucene syntax. If you're working with collections, the tools for tagging (submit_tags) and rating are essential.

Don't use this if all you want is a general overview of an artist. A simple web search will provide that. You only come here when you need to prove a specific data point—like confirming a release date or finding all related works for an MBID. If your task can be solved by simply reading text, don't use the server. Use it only when you must query structured metadata.

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

How we secure it →

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 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

add_collection_items browse_entities lookup_discid lookup_entity lookup_isrc lookup_iswc remove_collection_item search_entities submit_ratings submit_tags

Finding core music details shouldn't feel like pulling teeth.

Right now, if a journalist needs to verify an obscure track's release information, they open five different websites. They copy the title from one, the artist name from another, and the date from a third. Then they spend 20 minutes cross-referencing multiple APIs just to get three data points. It's slow, messy, and you lose context in all the copy/paste tabs.

With this MCP server, that whole process collapses. You give your agent the ISRC or the MBID. The tool runs the query against the central database, returning a clean, structured JSON object with every single metadata point—release date, label, artist ID, etc.—in seconds.

MusicBrainz Alternative MCP Server: Structured Metadata Access

Before this, finding a record's full context meant guessing which identifier was right. Did they list it by DiscID? Or maybe the ISWC? You had to manually check multiple endpoints and hope you didn't miss a link.

Now, your agent can run `lookup_discid` or `lookup_iswc`, knowing that no matter which industry standard you start with, you get the full entity context. It’s reliable. Period.

Common Questions About MusicBrainz Alternative MCP

How do I find an artist's MBID using MusicBrainz Alternative? +

You can use search_entities and specify the artist name along with a search filter for 'artist'. The tool will return the unique MBID if it exists in the database.

Can I add tags to my collection using MusicBrainz Alternative? +

Yes, you can use submit_tags. Just remember this requires authentication and you'll need to pass the specific item ID along with your tags via XML POST.

What is the difference between lookup_entity and browse_entities? +

lookup_entity gives you one big data dump on a single entity using its MBID. browse_entities, however, lists all related entities—like showing every release attached to that main artist.

Is ISRC the same as ISWC in MusicBrainz Alternative? +

No, they track different things. ISRC is for a specific recording (the master file). ISWC tracks the underlying musical work itself—like the sheet music or composition.

What do I need to use write tools like `submit_tags` or `add_collection_items`? +

You must authenticate with a valid MusicBrainz Access Token. Write operations require this token for validation. Without it, the agent cannot modify your personal data.

How does the `search_entities` tool handle complex queries using Lucene syntax? +

The search_entities tool processes queries by combining specific fields and terms with boolean operators (AND/OR). You must specify the field prefix, like 'arid:...' for artist identifiers.

If I know an entity's MBID, how should I use `browse_entities` to find its related releases? +

You pass the known MBID and specify the relationship type you want to explore. This function maps relationships—for example, finding all associated records or labels.

What happens if I provide an invalid identifier when calling `lookup_isrc`? +

The agent will return a specific error indicating the provided code does not match any record in the database. Always verify your ISRC format before querying.

How do I search for a specific artist if I don't have their MBID? +

Use the search_entities tool. Set the entity_type to 'artist' and provide the name in the query field. The agent will return a list of matches with their respective MBIDs.

Can I see all the recordings (songs) on a specific album? +

Yes! Use the lookup_entity tool with the release MBID and include 'recordings' in the inc parameter. This will fetch the full tracklist and metadata for that release.

Do I need an account to search the database? +

No. Searching and looking up data only requires a MUSICBRAINZ_USER_AGENT. An Access Token is only needed for actions like submit_tags, submit_ratings, or add_collection_items.

More in this category

You might also like

Built & Managed by Vinkius 30s setup 10 tools

We've already built the connector for MusicBrainz Alternative. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.