Skip to main content
Glama
hlights33

discogs-mcp

by hlights33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to discogs-mcp

No user-submitted related servers found.

    Related Servers

    • Discogs MCP Server

      donnatto
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search, manage, and analyze personal Discogs music collections with features like mood-based recommendations, advanced search, and collection analytics.
      15 npm
      MIT

    • Discogs MCP

      andreakofman-ui
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    • Discogs MCP Server

      DirtyDimmy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with your personal Discogs music collection, including search, mood-aware recommendations, collection analytics, and more.
      15 npm
      MIT

    • Discogs MCP Server

      cswkim
      A
      license
      C
      quality
      A
      maintenance
      Enables interactions with the Discogs API for music catalog operations and search functionality, allowing users to manage their Discogs collections through natural language.
      53
      181 npm
      132
      MIT

    • spotify-mcp

      Stipe15
      A
      license
      B
      quality
      B
      maintenance
      Enables Claude to manage Spotify playlists and analyze personal listening history, including account reads, playlist writes, local analytics from data exports, and building playlists from track lists.
      35
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 35 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources