MusicBrainz MCP

Purpose: Accessing MusicBrainz music metadata from AI assistants and MCP-compatible applications without managing API keys.

Inferred · not functionally tested

Audience: developers building AI assistants and music metadata tools

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: CLI, WEB · deployment: browser, cli, self_hosted, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

In the Frameworks & runtimes space, MusicBrainz MCP takes a focused approach. Inferred · not functionally tested: It focuses on accessing MusicBrainz music metadata from AI assistants and MCP-compatible applications without managing API keys. Inferred · not functionally tested: MusicBrainz MCP is an open-source project aimed at developers building AI assistants and music metadata tools. Basis unknown · not verified: MusicBrainz MCP is open source under the Open Source license. Basis unknown · not verified: It runs on the web, the command line, and API, and it can be self-hosted.

It is developed by mrfentmen. Inferred · not functionally tested: Among its 6 catalogued features are music metadata access, keyless operation, and MCP server. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.