Search the Discogs release database and authenticate requests correctly

domain: discogs.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Choose an auth mode: Discogs Auth (key/secret or personal token) or full OAuth 1.0a for acting on behalf of a user
  2. For Discogs Auth, send credentials either as key/secret or token query parameters, or as an Authorization header (e.g. 'Authorization: Discogs token=...')
  3. Call GET https://api.discogs.com/database/search?q={query} with the required q parameter to search releases, masters, artists, and labels
  4. Note that the search response's community section includes want/have counts for releases and master releases
  5. Add authentication for any endpoint beyond basic search - collection, marketplace, and image data require an authenticated token

Known gotchas

Related routes

Authenticate with Discogs via OAuth 1.0a and read/manage an authenticated user's collection folders and wantlist
www.discogs.com · 6 steps · unrated
Create and manage Discogs Marketplace listings via the authenticated Discogs API
www.discogs.com · 6 steps · unrated
Search the Deezer catalog for tracks, albums, and artists without authentication
developers.deezer.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans