Skip to main content
Glama
rianvdm
by rianvdm

๐ŸŽต Discogs MCP Server

Version License: MIT TypeScript Cloudflare Workers MCP

Deploy to Cloudflare

A powerful Model Context Protocol (MCP) server that enables AI assistants to interact with your personal Discogs music collection. Built on Cloudflare Workers using the official Cloudflare Agents SDK and @modelcontextprotocol/sdk.

โœจ Features

  • ๐Ÿ” Secure OAuth Authentication: Connect your Discogs account safely

  • ๐Ÿง  Intelligent Mood Mapping: Translate emotions into music ("mellow", "energetic", "Sunday evening vibes")

  • ๐Ÿ” Advanced Search Intelligence: Multi-strategy search with OR logic and relevance scoring

  • ๐Ÿ“Š Collection Analytics: Comprehensive statistics and insights about your music

  • ๐ŸŽฏ Context-Aware Recommendations: Smart suggestions based on mood, genre, and similarity

  • โšก Edge Computing: Global low-latency responses via Cloudflare Workers

  • ๐Ÿ—‚๏ธ Smart Caching: Intelligent KV-based caching for optimal performance

โš ๏ธ This Is Not a Shared Service

discogs-mcp.com is the maintainer's private instance. It's locked to a single Discogs account and will return a 403 for anyone else.

Why? The Discogs API rate limit (60 requests per minute, per registered app) is too tight to share across users. One active collection query from a single user can saturate it. Rather than run a broken multi-tenant service, each user deploys their own Worker with their own Discogs API credentials.

The good news: deploying your own copy is straightforward, runs on the Cloudflare Workers free tier, and takes about 10 minutes. See Self-Hosting below.

๐Ÿš€ Self-Hosting

The fastest path is the Deploy to Cloudflare button above. It clones this repo into your GitHub account, provisions the KV namespaces and Durable Object in your Cloudflare account, prompts you for the three secrets, and sets up Workers Builds so future pushes to your fork redeploy automatically.

1. Register a Discogs developer app

Go to discogs.com/settings/developers โ†’ Create an Application. Name it anything; the Callback URL can be a placeholder for now (you'll come back and set it after the Worker is deployed). Save the Consumer Key and Consumer Secret โ€” you'll paste them in next.

2. Click the button

Deploy to Cloudflare

When prompted, paste:

Secret

Value

DISCOGS_CONSUMER_KEY

from step 1

DISCOGS_CONSUMER_SECRET

from step 1

JWT_SECRET

any random string โ€” openssl rand -hex 32 works

After the deploy completes, Cloudflare shows your Worker URL โ€” something like https://discogs-mcp.<your-subdomain>.workers.dev. The MCP endpoint is /mcp.

3. Update your Discogs app callback URL

Go back to your Discogs app and set the Callback URL to:

https://discogs-mcp.<your-subdomain>.workers.dev/discogs-callback

By default, anyone who discovers your Worker URL can authenticate and consume your Discogs rate-limit budget. To restrict it, edit wrangler.toml in your fork and set ALLOWED_DISCOGS_USER_ID under [vars]:

[vars]
# Single user
ALLOWED_DISCOGS_USER_ID = "123456"

# Or a comma-separated list for multiple users
ALLOWED_DISCOGS_USER_ID = "123456,789012,345678"

Find your numeric ID by visiting https://api.discogs.com/users/<your-username> and looking at the id field. Push the change โ€” Workers Builds redeploys automatically.

5. Connect your MCP client

Replace https://your-worker.workers.dev below with your own URL.

Claude Desktop โ€” Settings โ†’ Integrations โ†’ Add Integration โ†’ https://your-worker.workers.dev/mcp

Claude Code:

claude mcp add --transport http discogs https://your-worker.workers.dev/mcp

Windsurf (~/.codeium/windsurf/mcp_config.json):

{
  "mcpServers": {
    "discogs": {
      "serverUrl": "https://your-worker.workers.dev/mcp"
    }
  }
}

Continue.dev / Zed / Generic:

{
  "mcpServers": {
    "discogs": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://your-worker.workers.dev/mcp"]
    }
  }
}

MCP Inspector (testing):

npx @modelcontextprotocol/inspector https://your-worker.workers.dev/mcp

Manual deploy (alternative)

If you'd rather skip the button โ€” for example, you want a fully local clone or you're on a Cloudflare account where the button doesn't work:

git clone https://github.com/rianvdm/discogs-mcp.git
cd discogs-mcp
npm install

# Create the two KV namespaces and copy the returned IDs into wrangler.toml
# (replace the empty `id = ""` values under the top-level [[kv_namespaces]] blocks)
wrangler kv namespace create MCP_SESSIONS
wrangler kv namespace create OAUTH_KV

# Set the three secrets
wrangler secret put DISCOGS_CONSUMER_KEY
wrangler secret put DISCOGS_CONSUMER_SECRET
wrangler secret put JWT_SECRET

# Deploy
npm run deploy

Then follow steps 3โ€“5 above (callback URL, optional allowlist, connect your MCP client).

๐Ÿ” Authentication

This server uses MCP OAuth 2.1 with Discogs as the identity provider. When you connect for the first time:

  1. Your MCP client automatically opens a browser window

  2. Authorize the application on Discogs

  3. You're redirected back and authenticated โ€” no copy-pasting required

  4. Your session persists for 7 days

๐Ÿ› ๏ธ Available Tools

๐Ÿ”“ Public Tools (No Authentication Required)

Tool

Description

ping

Test server connectivity

server_info

Get server information and capabilities

auth_status

Check authentication status and get login instructions

๐Ÿ” Authenticated Tools (Requires Login)

Search & discovery

Tool

Description

search_collection

Search your collection with explicit genre filters, mood-aware ranking, and master-level dedup

search_discogs

Search the Discogs-wide catalog (releases, masters, artists, labels) โ€” marks results you already own

get_release

Get detailed information about a specific release (tracklist, formats, labels)

get_collection_stats

View genre breakdown, decade analysis, format distribution, and ratings

get_recommendations

Get personalized recommendations by genre, decade, mood, or similarity

Collection management

Tool

Description

add_to_collection

Add a release to a folder (defaults to Uncategorized)

remove_from_collection

Remove a specific release instance from a folder

move_release

Move a release instance between folders

rate_release

Rate a release from 0 (no rating) to 5 stars

Folders

Tool

Description

list_folders

List all folders with release counts

create_folder

Create a new folder

edit_folder

Rename an existing folder (system folders excluded)

delete_folder

Delete an empty folder (system folders excluded)

Custom fields

Tool

Description

list_custom_fields

List all custom fields defined on your collection

edit_custom_field

Set a custom field value on a specific release instance

Diagnostics

Tool

Description

get_cache_stats

View cache performance (total entries, pending requests, breakdown)

๐Ÿ“š MCP Resources

Access Discogs data via standardized MCP resource URIs:

discogs://collection             # Complete collection (JSON)
discogs://release/{id}           # Specific release details
discogs://search?q={query}       # Search results

๐Ÿ—๏ธ Local Development

# Set dev secrets (same Discogs app is fine for dev)
wrangler secret put DISCOGS_CONSUMER_KEY
wrangler secret put DISCOGS_CONSUMER_SECRET
wrangler secret put JWT_SECRET

# Run the Worker locally
npm run dev

# Test with MCP Inspector
npx @modelcontextprotocol/inspector http://localhost:8787/mcp

The default [vars] block in wrangler.toml leaves ALLOWED_DISCOGS_USER_ID empty, so local dev is open to any Discogs account โ€” convenient for testing.

๐Ÿงช Testing

npm test              # Run all tests
npm test -- --watch  # Run tests in watch mode

๐Ÿค Contributing

  1. Fork the repository

  2. Create your feature branch (git checkout -b feature/amazing-feature)

  3. Commit your changes (git commit -m 'Add amazing feature')

  4. Push to the branch (git push origin feature/amazing-feature)

  5. Open a Pull Request

๐Ÿ“„ License

MIT License - see LICENSE file for details.

๐Ÿ™ Acknowledgments

A
license - permissive license
-
quality - not tested
B
maintenance

Maintenance

โ€“Maintainers
<1hResponse time
3wRelease cycle
15Releases (12mo)
Issues opened vs closed

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rianvdm/discogs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server