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.

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.

MusicBrainz MCP Server for CrewAI 15 tools — connect in under 2 minutes

Name: MusicBrainz
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 15 Tools Framework

Connect your CrewAI agents to MusicBrainz through Vinkius, pass the Edge URL in the `mcps` parameter and every MusicBrainz tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="MusicBrainz Specialist",
    goal="Help users interact with MusicBrainz effectively",
    backstory=(
        "You are an expert at leveraging MusicBrainz tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in MusicBrainz "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 15 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About MusicBrainz MCP Server

Connect to MusicBrainz, the world's largest open music database, and explore music metadata through natural conversation — no API key needed.

When paired with CrewAI, MusicBrainz becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call MusicBrainz tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Artist Search — Find musicians, bands, orchestras and composers with types, countries and active dates
Release Search — Search album releases with artists, dates, countries, labels and track counts
Track Search — Find individual recordings with durations, ISRCs and album info
Release Groups — Browse canonical albums and singles grouped across different releases
Label Search — Find record labels and publishers
Work Search — Search musical compositions distinct from recordings
Browse — Get all releases by a specific artist or label

The MusicBrainz MCP Server exposes 15 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect MusicBrainz to CrewAI via MCP

Follow these steps to integrate the MusicBrainz MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 15 tools from MusicBrainz

Why Use CrewAI with the MusicBrainz MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with MusicBrainz through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

MusicBrainz + CrewAI Use Cases

Practical scenarios where CrewAI combined with the MusicBrainz MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries MusicBrainz for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries MusicBrainz, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain MusicBrainz tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries MusicBrainz against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

MusicBrainz MCP Tools for CrewAI (15)

These 15 tools become available when you connect MusicBrainz to CrewAI via MCP:

browse_releases_by_artist

Returns release titles, dates, countries and labels. Pagination: max 100 results per request. Browse all releases by a specific artist

browse_releases_by_label

Returns release titles, artists, dates and countries. Pagination: max 100 results. Browse all releases by a specific record label

get_artist

Returns name, type, country, life span, disambiguation and more. Optionally include related data with inc parameter: "releases", "release-groups", "recordings", "works", "aliases". Get detailed info for a specific artist by MBID

get_label

Returns label name, type, country, founding date and more. Get detailed info for a specific record label by MBID

get_recording

Returns title, artist, duration, ISRCs, releases it appears on and more. Optionally include: "artists", "isrcs", "releases", "aliases". Get detailed info for a specific recording by MBID

get_release

Returns title, artist, date, country, label, barcode, track listing and more. Optionally include: "artists", "labels", "recordings", "discids", "isrcs", "media". Get detailed info for a specific release by MBID

get_release_group

Returns title, artist, primary type, first release date and more. Optionally include: "artists", "releases", "aliases". Get detailed info for a specific release group by MBID

get_work

Returns work title, writers, type, ISWC, languages and more. Get detailed info for a specific musical work by MBID

search_areas

Returns area names, types (country, city, subdivision, etc.) and ISO codes. Useful for finding area IDs to use in other searches. Search for geographic areas (countries, cities, regions)

search_artists

). Returns artist names, IDs, types (person, group, orchestra, etc.), countries, active dates and disambiguation info. Supports Lucene query syntax for advanced searches. Pagination: max 100 results per request. Search for music artists

search_labels

Returns label names, types (original production, reissue, etc.), countries and founding dates. Pagination: max 100 results. Search for record labels

search_recordings

Returns recording titles, artists, durations, album names and ISRCs. Useful for finding specific track versions and metadata. Pagination: max 100 results. Search for individual track recordings

search_release_groups

Returns titles, artists, primary types (album, single, EP, etc.) and dates. Useful for finding the canonical album/single version. Pagination: max 100 results. Search for release groups (albums, singles, EPs)

search_releases

Returns release titles, artists, dates, countries, labels and track counts. Supports filtering by status (official, promotion, bootleg). Pagination: max 100 results. Search for album releases

search_works

Returns work titles, writers, types (song, opera, symphony, etc.) and ISWCs. Useful for finding composition metadata separate from specific recordings. Pagination: max 100 results. Search for musical works (compositions)

Example Prompts for MusicBrainz in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with MusicBrainz immediately.

"Search for the band Radiohead."

"Show me all albums by Miles Davis."

"Search for the recording of 'Bohemian Rhapsody' by Queen."

Troubleshooting MusicBrainz MCP Server with CrewAI

Common issues when connecting MusicBrainz to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

MusicBrainz + CrewAI FAQ

Common questions about integrating MusicBrainz MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.