Beatport MCP

Sign in to this service

The account page reports that sign-in setup is pending at publication time. Once available, use an allowed email; access is invitation-only unless the account page explicitly offers open signup.

Connect your Beatport account

The account page currently reports that new Beatport connections are unavailable. There is no self-service Beatport API token for you to create. The hosted service operator must first have an authorized Beatport application and complete the provider setup. Until then, do not continue to MCP-token creation: new tokens are not usable without a connected account.

Configure your MCP client

After signing in, connecting your own Beatport account, and creating a personal token in Access tokens, use remote Streamable HTTP at:

Set Authorization: Bearer <YOUR_PERSONAL_MCP_TOKEN>. Claude Code:

claude mcp add --transport http beatport https://beatport-mcp.sherwoodcallaway.com/mcp --header "Authorization: Bearer <YOUR_PERSONAL_MCP_TOKEN>"

Other clients need remote Streamable HTTP plus the same bearer header. Never use an operator’s shared server token. MCP Gateway is optional.

Verify and manage access

Reload tools and call search for account_status, then execute it. Confirm your Beatport account is connected before catalog or playlist operations.

• Sign-in setup pending: hosted identity/email or Google sign-in is not configured yet.
• Beatport connection pending: the hosted provider application is not enabled; this is an operator-side blocker, not a token issue.
• 401 Unauthorized: check your personal MCP token and bearer header; replace a token only after account access is enabled.
• Provider authorization error: retry account connection; if it persists, the hosted Beatport app integration must be fixed.

When the service is available, disconnect Beatport and revoke MCP tokens from the account page. Revoke provider access in Beatport if that control is offered for the authorized application.