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 VS Code Copilot 15 tools — connect in under 2 minutes

Name: MusicBrainz
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 15 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install MusicBrainz and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "musicbrainz": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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.

GitHub Copilot Agent mode brings MusicBrainz data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 15 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the MusicBrainz MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using MusicBrainz

Ask Copilot: "Using MusicBrainz, help me...". 15 tools available

Why Use VS Code Copilot with the MusicBrainz MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with MusicBrainz through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

MusicBrainz + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the MusicBrainz MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

MusicBrainz MCP Tools for VS Code Copilot (15)

These 15 tools become available when you connect MusicBrainz to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting MusicBrainz to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

MusicBrainz + VS Code Copilot FAQ

Common questions about integrating MusicBrainz MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.