Summary
The collection, the wantlist and the shop counter answer in one place.
Search reaches the fields that identify a physical copy — barcode, catalogue number, credit, track — so pinning down which pressing you are holding is a call rather than a scroll through versions. Collection, wantlist and marketplace tools all key off the same username, which makes "do I already own this, and what is it going for" answerable without switching context.
What it is
A client for the Discogs API: 53 tools spanning the catalogue (releases, masters, artists, labels), a user's collection and wantlist, and the marketplace — listings, orders and order messages.
What you get
- Catalogue search by barcode, catalogue number, credit, track, contributor, format, style, country and year, as well as free text
- A release and its master, plus every version of that master filtered by country, label, format and release year
- An artist's releases and a label's releases, paged and sorted
- A collection organised in folders: releases added, moved between folders, rated, and removed by instance
- User-defined collection notes fields read per user and written per release
- The minimum, median and maximum value of a collection
- A wantlist with notes and a rating on each entry
- Marketplace listings created, updated and deleted with condition, sleeve condition, price, location and whether offers are allowed
- Orders listed and edited, with an order's message log read and appended to
- Marketplace statistics for a release, and an inventory export requested as CSV then listed and downloaded
Requirements
A Discogs account and a personal access token in DISCOGS_PERSONAL_ACCESS_TOKEN, plus npx on your PATH.
Setup effort
One command plus a key — npx -y discogs-mcp-server, then supply credentials