MusicBrainz Python API Docs | dltHub

Build a MusicBrainz-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

MusicBrainz is an open-source, community-maintained music metadata service that provides a REST API to query and submit information about entities like artists, releases, and recordings. The REST API base URL is https://musicbrainz.org/ws/2 and authentication is only required for data submission and user-specific endpoints via OAuth2 or HTTP Digest, but a custom User-Agent header is mandatory for all requests.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading MusicBrainz data in under 10 minutes.


What data can I load from MusicBrainz?

Here are some of the endpoints you can load from MusicBrainz:

ResourceEndpointMethodData selectorDescription
artist/artistGETSearch artists (requires query)
release/releaseGETSearch releases (requires query)
recording/recordingGETSearch recordings (requires query)
label/labelGETSearch labels (requires query)
genre/genre/allGETList all genres

How do I authenticate with the MusicBrainz API?

The service supports OAuth2 or HTTP Digest authentication for POST requests and user-specific data. Every request must include a custom, meaningful 'User-Agent' header to identify the application and contact information.

1. Get your credentials

MusicBrainz does not use traditional API keys for read access. For public, non-commercial read access, you only need to provide a meaningful User-Agent header in your requests. For data submission or access to private user information, you must use OAuth2. To obtain OAuth2 credentials, register your application on the MusicBrainz website via your user account profile settings, which will provide you with a Client ID and Client Secret.

2. Add them to .dlt/secrets.toml

[sources.musicbrainz_source] client_id = "REPLACE_ME"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the MusicBrainz API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python musicbrainz_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline musicbrainz_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset musicbrainz_data The duckdb destination used duckdb:/musicbrainz.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads lookup and browse from the MusicBrainz API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def musicbrainz_source(client_id=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://musicbrainz.org/ws/2", "auth": {"type": "bearer", "token": client_id}, }, "resources": [ {"name": "browse_entities", "endpoint": {"path": "/<RESULT_ENTITY_TYPE>?<BROWSING_ENTITY_TYPE>=<MBID>"}}, {"name": "search_entities", "endpoint": {"path": "/<ENTITY_TYPE>?query=<QUERY>"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="musicbrainz_pipeline", destination="duckdb", dataset_name="musicbrainz_data", ) load_info = pipeline.run(musicbrainz_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("musicbrainz_pipeline").dataset() sessions_df = data.browse_entities.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM musicbrainz_data.browse_entities LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("musicbrainz_pipeline").dataset() data.browse_entities.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load MusicBrainz data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for MusicBrainz?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines