discogs-mcp
Related Servers
Alternatives to discogs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to query and manage a Discogs music collection in natural language, including collection and catalog search, statistics, recommendations, wantlist and folder updates, ratings, and custom fields. It authenticates with Discogs via OAuth and caches a collection snapshot to answer many queries quickly.13 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search and manage a user's Discogs music collection, wantlist, and folders through natural language, including catalog lookups, recommendations, collection statistics, and administrative actions.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to search, manage, and analyze personal Discogs music collections with features like mood-based recommendations, advanced search, and collection analytics.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search and explore your Discogs music collection in natural language, covering releases, artists, labels, and masters, with recommendations by genre, decade, or mood. It also handles day-to-day collection admin such as adding and moving releases, rating them, managing wantlists, and creating or renaming folders.13 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to search, browse, and update a user's music collection, wantlist, folders, ratings, and custom fields, plus retrieve collection statistics and recommendations through natural-language tools.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with your personal Discogs music collection, including search, mood-aware recommendations, collection analytics, and more.13 npmMIT
TDQS
Scored across 35 tools
Most tools target a distinct resource+action, and descriptions actively disambiguate the riskiest overlaps (e.g. get_collection vs query_collection vs collection_summary vs find_in_collection, and get_release vs get_master vs get_master_versions). A few read paths (collection_summary, query_collection, get_collection) still crowd the same 'read my collection' purpose, but the guidance on when to use each keeps confusion low.
The dominant convention is a clean verb_noun pattern (add_to_collection, remove_from_wantlist, sync_release_details, get_artist_releases, delete_folder, create_folder). A handful of outliers (search, whoami, collection_summary, find_in_collection) break the pattern slightly but remain readable and intuitive.
At 35 tools this is heavy and sits above the comfortable 3-15 range, but the server covers several genuinely distinct domains: collection/folder CRUD, wantlist management, sync/cache, catalog lookup, and marketplace pricing. Nearly every tool has a defensible role, so the count is defensible yet still on the bulky side.
Coverage is broad and well-rounded: full CRUD for collection items and folders, wantlist add/remove/get, sync plus cached querying/export, and lookups for release, master, artist and label with marketplace stats. Only minor gaps exist (e.g. no first-class edit of existing wantlist/list entries beyond the add tool's upsert behavior, limited write surface for user lists).