Beatport MCP Server

MCP Server that connects an LLM to the Beatport API

Local serverstdio

What is the Beatport MCP server?

MCP Server that connects an LLM to the Beatport API. Exposed over MCP by the beatport mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

An MCP (Model Context Protocol) server that provides access to the Beatport API for music discovery and data retrieval.

  • Easy Authentication — Simple username/password authentication
  • Full Beatport API — Access to tracks, artists, labels, releases, charts, and more
  • Flexible Transport — Supports both stdio and HTTP transports
  • Built on OpenAPI — Leverages the official Beatport OpenAPI specification

Its toolset

Everything the assistant can do here goes through one of these:

  • Catalog — The Catalog tool exposed by this server

Adding it to your client

@ivotoby/beatport-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need 4 environment variables: BEATPORT_ACCESS_TOKEN, BEATPORT_USERNAME, BEATPORT_PASSWORD, BEATPORT_REFRESH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Beatport's toolset — Catalog — is a fair guide to whether it matches your workflow. It is maintained by ivo-toby; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the beatport mcp server does with a few real requests.

Available tools

ToolWhat it does
CatalogThe Catalog tool exposed by this server.

How to install the Beatport MCP server

{
  "mcpServers": {
    "beatport": {
      "command": "npx",
      "args": ["-y", "@ivotoby/beatport-mcp-server"],
      "env": {
        "BEATPORT_ACCESS_TOKEN": "your-value",
        "BEATPORT_USERNAME": "your-value",
        "BEATPORT_PASSWORD": "your-value",
        "BEATPORT_REFRESH_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
BEATPORT_ACCESS_TOKENCredential the server authenticates with.Yes
BEATPORT_USERNAMEConfiguration value read at startup.Optional
BEATPORT_PASSWORDConfiguration value read at startup.Optional
BEATPORT_REFRESH_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Beatport to Catalog.

Frequently asked questions

Run `node get-token.js` for detailed instructions, or email `engineering@beatport.com` to request OAuth2 credentials specifically for "Beatport MCP Server".