How to Use the MusicBrainz MCP in CrewAI

Q: How can a CrewAI team collaborate on a single MusicBrainz research task?

You can have one agent perform a broad searchreleasegroups query. It then passes a list of promising MBIDs to a second agent, which performs a detailed getrelease on each one to gather specific tracklists and label info via the MCP connection.

Q: What if my CrewAI agent needs to find all versions of an album in MusicBrainz?

The agent should first use searchreleasegroups to find the main album entry. It then uses that group's ID with the getreleasegroup tool and includes the inc="releases" parameter to get a list of all associated editions.

Q: How do I find the geographic origin of a band?

Your agent would use the searchartists tool to get the artist's ID and basic info. This response often includes a country and an area ID. For more detail, it can then use that area ID with the searchareas tool.

Deploy autonomous agent crews to monitor and catalog the world of music. CrewAI uses MusicBrainz to build a complete picture of any artist.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect MusicBrainz MCP to CrewAI

Create your Vinkius account to connect MusicBrainz to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup MusicBrainz with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Assemble a Music Research Crew

Assign roles to a team of agents for deep music analysis. A 'Scout' agent can use `search_artists` and `search_labels` to discover new entries. It passes artist and label MBIDs to a 'Librarian' agent. The 'Librarian' agent then takes over, using the IDs to perform deep dives with `get_artist` and `browse_releases_by_label`. The agents work together using this MCP server, sharing context in CrewAI's shared memory.

Monitor a Genre Autonomously

Set up a crew to watch a specific music scene. One agent can periodically run `search_releases` with a query targeting a genre tag and recent dates. When it finds a new release, it triggers the next agent. A 'Profiler' agent then uses `get_release` and `get_artist` to build a profile of the new music. If the artist is new to your system, it can trigger a 'Cataloger' agent to pull their entire back-catalog. This is a true autonomous MCP operation.

Verify and Clean Metadata at Scale

Use a hierarchical crew to ensure data quality. A 'Validator' agent can scan your local database for entries missing an ISWC or ISRC. For each one, it dispatches a 'Fixer' sub-agent. The 'Fixer' agent uses `search_recordings` to find the track on MusicBrainz, then calls `get_recording` with `inc="isrcs"` to get the missing codes. It can also use `get_work` to find the ISWC. Once done, it reports back to the Validator, which moves to the next record.

Setup guide

Set up MusicBrainz MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke MusicBrainz tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="MusicBrainz Analyst",
    goal="Access and analyze MusicBrainz data via MCP.",
    backstory="Expert analyst with direct MusicBrainz access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent MusicBrainz transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="MusicBrainz Analyst",
        goal="Access and analyze MusicBrainz data via MCP.",
        backstory="Expert analyst with direct MusicBrainz access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent MusicBrainz transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

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

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect MusicBrainz now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about MusicBrainz MCP in CrewAI

You can have one agent perform a broad `search_release_groups` query. It then passes a list of promising MBIDs to a second agent, which performs a detailed `get_release` on each one to gather specific tracklists and label info via the MCP connection.

Yes, that's a perfect use case. This agent's primary tools would be `search_works` to find compositions by name and `get_work` to retrieve detailed writer and publisher information for a given musical work ID.

The agent should first use `search_release_groups` to find the main album entry. It then uses that group's ID with the `get_release_group` tool and includes the `inc="releases"` parameter to get a list of all associated editions.

Your agent would use the `search_artists` tool to get the artist's ID and basic info. This response often includes a country and an area ID. For more detail, it can then use that area ID with the `search_areas` tool.

Yes. The server only sees requests for public music metadata like work titles or release dates. Each request is handled in an ephemeral sandbox, and Vinkius ensures your MCP Server connection is isolated and secured. No query data is retained.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript