discogs

This MCP server provides an interface to manage and query your Discogs collection via the Model Context Protocol. It runs as a Cloudflare Worker-backed MCP, exposing both public tools (no authentication required) and authenticated tools (requiring you to log in with Discogs OAuth 1.0a). Public tools include ping, server_info, and auth_status to verify connectivity and login state. Authenticated tools let you search your collection with mood and genre mapping, fetch detailed release data, view collection statistics, get personalized recommendations, and monitor cache stats during development. To use the server, you can connect via standard MCP clients or the provided Inspector tool to validate responses against the MCP protocol. The workflow typically involves authenticating with Discogs once, after which your session persists for seven days with cross-origin support, enabling seamless usage of the protected tools.

Prerequisites:

• Node.js 18+
• Cloudflare account for deploying Workers
• Discogs Developer Account (for API keys)

Local setup:

1. Clone the repository and install dependencies:

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

2. Configure environment secrets for Discogs and JWT:

# Set your Discogs API credentials and a JWT secret
wrangler secret put DISCOGS_CONSUMER_KEY
wrangler secret put DISCOGS_CONSUMER_SECRET
wrangler secret put JWT_SECRET

3. Start the development server:

npm run dev

4. Test with MCP Inspector during development:

npx @modelcontextprotocol/inspector http://localhost:8787/mcp

Deployment:

1. Create KV namespaces if required by your deployment workflow:

npm run setup:prod

2. Set production secrets with Wrangler:

wrangler secret put DISCOGS_CONSUMER_KEY --env production
wrangler secret put DISCOGS_CONSUMER_SECRET --env production
wrangler secret put JWT_SECRET --env production

3. Deploy the Worker:

npm run deploy:prod

Tips and considerations:

• Ensure your Discogs credentials are kept secure; use Wrangler secrets for production deployments.
• The Discogs OAuth flow is used for authentication; initial login will generate a unique URL you must open to authorize the application.
• Sessions last 7 days and support cross-origin requests, which is important for multi-client workflows.
• For testing and development, the MCP Inspector can be used to validate calls against http://localhost:8787/mcp or your deployed Worker URL.
• If you encounter authentication errors, verify that your DISCOGS_CONSUMER_KEY and DISCOS_CONSUMER_SECRET are correct and that your JWT_SECRET is properly set.
• The server exposes both public tools (ping, server_info, auth_status) and authenticated tools (search_collection, get_release, get_collection_stats, get_recommendations, get_cache_stats). Plan client interactions accordingly.