2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 15 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add MusicBrainz as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to MusicBrainz. "
            "You have 15 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in MusicBrainz?"
    )
    print(response)

asyncio.run(main())
MusicBrainz
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.

LlamaIndex agents combine MusicBrainz tool responses with indexed documents for comprehensive, grounded answers. Connect 15 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

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 LlamaIndex 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 LlamaIndex via MCP

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

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 15 tools from MusicBrainz

Why Use LlamaIndex with the MusicBrainz MCP Server

LlamaIndex provides unique advantages when paired with MusicBrainz through the Model Context Protocol.

01

Data-first architecture: LlamaIndex agents combine MusicBrainz tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain MusicBrainz tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query MusicBrainz, a vector store, and a SQL database in a single turn and synthesize results

04

Observability integrations show exactly what MusicBrainz tools were called, what data was returned, and how it influenced the final answer

MusicBrainz + LlamaIndex Use Cases

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

01

Hybrid search: combine MusicBrainz real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query MusicBrainz to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying MusicBrainz for fresh data

04

Analytical workflows: chain MusicBrainz queries with LlamaIndex's data connectors to build multi-source analytical reports

MusicBrainz MCP Tools for LlamaIndex (15)

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

01

browse_releases_by_artist

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

02

browse_releases_by_label

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

03

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

04

get_label

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

05

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

06

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

07

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

08

get_work

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

09

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)

10

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

11

search_labels

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

12

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

13

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)

14

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

15

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 LlamaIndex

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

01

"Search for the band Radiohead."

02

"Show me all albums by Miles Davis."

03

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

Troubleshooting MusicBrainz MCP Server with LlamaIndex

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

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

MusicBrainz + LlamaIndex FAQ

Common questions about integrating MusicBrainz MCP Server with LlamaIndex.

01

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
02

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query MusicBrainz tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Connect MusicBrainz to LlamaIndex

Get your token, paste the configuration, and start using 15 tools in under 2 minutes. No API key management needed.