Cratedigger
Related Servers
Alternatives to Cratedigger
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceGives Claude full access to Discogs for database lookups, collection and wantlist management (with dry-run write safety), and marketplace pricing. It also syncs everything into a local SQLite cache for read-only SQL analysis and optional matching against a digital music library.35MIT
- AlicenseNot gradedqualityBmaintenanceSearch, rate and organise your Discogs collection, wantlist and folders from an AI assistant. Self-hosted: deploy your own copy to Cloudflare Workers with the Deploy to Cloudflare button in the README. Not affiliated with Discogs.20MIT
- 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.MIT
- AlicenseBqualityDmaintenanceA server that connects Claude with Spotify, allowing users to control playback, search content, get information about tracks/albums/artists/playlists, and manage the Spotify queue.5615MIT
- 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 gradedqualityCmaintenanceMCP server that enables AI assistants to interact with a personal Discogs music collection, supporting search, collection management, wantlist, folders, custom fields, and recommendations via Cloudflare Workers.MIT
TDQS
Scored across 11 tools
Each tool has a clearly distinct target: catalog search, release card, master pressings, marketplace prices, collection listing, wantlist listing, wantlist mutation, cross-source matching, and collection summary. Descriptions go further than most servers by naming the sibling tool to use instead ('Do not use it to find a Release by name (use discogs_search)', 'use discogs_wantlist_prices for what the Wants cost'), which removes the near-misses between get_prices / wantlist_prices and list_collection / match_collection / collection_summary.
All tools are snake_case with a uniform discogs_ prefix and mostly verb_noun order (get_release, list_collection, match_collection). A few deviate into noun-first compounds (discogs_wantlist_prices, discogs_wantlist_add, discogs_collection_summary) and get_prices sits alongside wantlist_prices, so the pattern is readable but not perfectly uniform.
Eleven tools is squarely in the well-scoped range, and each one covers a distinct read or write surface (search, release, master, prices, collection, wantlist x3, match, summary). Nothing looks like a redundant variant of another tool.
The read side is thorough, and the Wantlist has full add/remove lifecycle support, but the Collection is read-only: there is no way to add a Release to the collection, remove a copy, or edit folder/condition/rating, which is an asymmetric gap given wantlist_add/wantlist_remove exist. An agent asked to 'add this to my collection' hits a dead end.