beatport

MCP Server that connects an LLM to the Beatport API

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio ivo-toby-beatport-mcp-server npx -y @ivotoby/beatport-mcp-server \
  --env BEATPORT_PASSWORD="Beatport password (optional if using token flow)" \
  --env BEATPORT_USERNAME="Beatport username/email (optional if using token flow)" \
  --env BEATPORT_ACCESS_TOKEN="Bearer token for OAuth2 access (optional if using get-token flow)" \
  --env BEATPORT_REFRESH_TOKEN="OAuth2 refresh token (optional)"

How to use

This MCP server provides a bridge to Beatport's API via the Model Context Protocol. It can authenticate with Beatport either by a manually retrieved OAuth2 access token or by username/password (though the latter may not function due to Beatport's API limitations). The server dynamically generates MCP tools from the Beatport OpenAPI endpoints, enabling discovery of artists, tracks, labels, releases, charts, and more through the MCP interface. It supports both standard input/output (stdio) and HTTP transports, so you can either connect to it locally in a CLI workflow or expose it as an HTTP service for integration with other applications. Typical workflows involve querying catalog data (artists, tracks, releases, labels, genres), browsing charts and playlists, and performing refined searches with filters like genre, BPM, key, and release date. Tools are auto-generated for endpoints such as catalog-artists-list, catalog-tracks-list, catalog-releases-list, catalog-labels-list, catalog-charts-list, and catalog-playlists-list, with pagination and rich metadata available for tracks and releases. To operate, run the server, authenticate via a token or credentials if supported, and invoke the generated MCP tools from your MCP client or host environment.

How to install

Prerequisites:

Node.js (LTS version) and npm installed on your system
Access to the Beatport MCP package (the server is published as @ivotoby/beatport-mcp-server)

Installation steps:

Install the MCP server globally (as recommended in the README):

npm install -g @ivotoby/beatport-mcp-server

Verify installation by running the command (or using npx as configured in the MCP config):

beatport-mcp-server --version

(Optional) If you prefer not to install globally, you can use npx directly:

npx -y @ivotoby/beatport-mcp-server

Prepare authentication:

Option A: Obtain an OAuth2 access token using the recommended manual flow (see get-token.js guidance in the repo) and set BEATPORT_ACCESS_TOKEN.
Option B: If supported, set BEATPORT_USERNAME and BEATPORT_PASSWORD and launch the server to attempt password-based authentication.

Run the server with the desired transport (stdio or http).

# Example for HTTP transport on port 3000
beatport-mcp-server --transport http --port 3000

Notes:

If using the HTTP transport, configure host and path as needed with --host and --path.
You can customize the server name and version with --name and --version.

Additional notes

Tips and known considerations:

Beatport API requires OAuth2 credentials; this MCP server can handle a token-based flow but may not fully support password-based authentication due to API limitations.
Environment variables can be supplied in your deployment environment or via your MCP runtime configuration.
Transport flexibility (stdio vs http) enables both local development and integration into larger workflows.
When using HTTP transport, ensure the port is exposed in your environment and that firewall rules permit incoming connections if needed.
The server auto-generates a large set of tools from the Beatport OpenAPI; if you only need specific tools, consider using --tools or --tool to limit/import only certain endpoints.
If you encounter token expiration, rely on BEATPORT_REFRESH_TOKEN if supported to refresh tokens automatically.