discorg-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DISCOGS_USERNAME | No | Only needed alongside the access token variables if the token's identity lookup should be skipped. | |
| DISCOGS_USER_AGENT | No | Overrides the User-Agent header. Defaults to discorg-mcp/<version> +<repo url>. | |
| DISCOGS_ACCESS_TOKEN | No | Skip the on-disk credential file and inject an access token directly (useful for CI/containers). Must be set together with DISCOGS_ACCESS_TOKEN_SECRET. | |
| DISCOGS_CONSUMER_KEY | Yes | Your registered Discogs application's consumer key. Required. | |
| DISCOGS_CONSUMER_SECRET | Yes | Your registered Discogs application's consumer secret. Required. | |
| DISCOGS_ACCESS_TOKEN_SECRET | No | Skip the on-disk credential file and inject an access token secret directly. Must be set together with DISCOGS_ACCESS_TOKEN. | |
| DISCORG_MCP_CREDENTIALS_PATH | No | Overrides where login reads/writes credentials. Defaults to ~/.config/discorg-mcp/credentials.json. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discogs_whoamiA | Return the Discogs identity (username, id, resource_url) of the currently authenticated user. |
| discogs_searchA | Search the Discogs database for releases, masters, artists, or labels. Supports free-text queries plus structured filters (artist, title, label, genre, style, year, format, country, barcode). |
| discogs_get_releaseA | Fetch full details for a single release by its Discogs release ID. |
| discogs_get_masterA | Fetch details for a master release (the abstract release grouping all its pressings/versions). |
| discogs_get_master_versionsA | List all known pressings/versions of a master release. |
| discogs_get_artistA | Fetch profile details for an artist by Discogs artist ID. |
| discogs_get_artist_releasesB | List releases and masters credited to an artist. |
| discogs_get_labelB | Fetch profile details for a record label by Discogs label ID. |
| discogs_get_label_releasesA | List releases put out on a record label. |
| discogs_list_collection_foldersA | List the authenticated user's collection folders (e.g. "All", "Uncategorized", custom folders). |
| discogs_get_collection_itemsA | List the releases in a collection folder, with sort and pagination options. |
| discogs_add_to_collectionB | Add a release to a collection folder. |
| discogs_remove_from_collectionA | Remove a specific instance of a release from a collection folder. Requires the instance_id returned by discogs_get_collection_items for that copy (a release can appear multiple times in a folder). |
| discogs_update_collection_itemB | Update the personal rating and/or notes fields on a specific collection item instance. |
| discogs_get_collection_valueA | Get the estimated minimum, median, and maximum marketplace value of the user's whole collection. |
| discogs_get_wantlistA | List releases on the authenticated user's wantlist. |
| discogs_add_to_wantlistB | Add a release to the authenticated user's wantlist, optionally with notes and a rating. |
| discogs_remove_from_wantlistB | Remove a release from the authenticated user's wantlist. |
| discogs_get_marketplace_statsB | Get the number of copies for sale and the lowest current price for a release. |
| discogs_get_price_suggestionsA | Get Discogs' suggested price per condition grade for a release, based on recent marketplace sales. Requires the authenticated user to have marketplace seller settings configured. |
| discogs_get_listingA | Fetch a single marketplace listing by its listing ID. |
| discogs_get_seller_inventoryB | List the marketplace listings for a given Discogs username (defaults to the authenticated user). |
| discogs_create_listingA | List a release for sale on the Discogs marketplace. This creates a real, publicly visible listing — confirm details with the user before calling. |
| discogs_update_listingA | Update an existing marketplace listing (price, condition, comments, status, etc). |
| discogs_delete_listingA | Remove a marketplace listing. This is irreversible — confirm with the user before calling. |
| discogs_list_ordersA | List the authenticated user's marketplace orders (as a seller), with optional status filter. |
| discogs_get_orderB | Fetch details for a single marketplace order. |
| discogs_update_orderA | Update a marketplace order's status, shipping price, or additional instructions. Changing status notifies the buyer — confirm with the user before calling. |
| discogs_list_order_messagesA | List the message/status-change history for a marketplace order. |
| discogs_add_order_messageA | Post a message to a marketplace order's message thread, optionally also changing its status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 30 tools
Each tool targets a distinct resource/action, and descriptions clearly clarify differences (e.g., release vs master, collection vs wantlist). The only mild overlap is between update_order and add_order_message, both of which can change order status, but their primary purposes differ.
Most tools follow a verb_noun pattern (get_release, create_listing, add_to_collection), but discogs_whoami and get_seller_inventory deviate slightly from the dominant verb_noun consistency.
With 30 tools, the set is on the heavy side, but each tool covers a distinct part of the Discogs API (database, collection, wantlist, marketplace, orders). While above the typical well-scoped range, the count is justified by the API's breadth, though it remains high.
The tool surface covers the main CRUD operations for collection, wantlist, listings, and orders, plus robust search and lookup. Missing operations like moving a collection item between folders or updating a wantlist item can be worked around (remove/add), so no critical dead ends.