Back to MCP Directory
Discogs
Model Context Protocol moderate risk

Discogs

MCP server for Discogs API, enabling music catalog management, search, and data manipulation with caution due to potential data editing capabilities.

Connections & Capabilities

Connects To

GitHubDocker

Capabilities

readwriteexec

Quickstart

Config

{
  "mcpServers": {
    "discogs": {
      "command": "npx",
      "args": [
        "-y",
        "discogs-mcp-server"
      ],
      "env": {
        "DISCOGS_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

Exposed MCP Tools (6)

safe
search

Searches the Discogs database for releases, artists, labels, etc.

Read-only operation, no data modification.

safe
getRelease

Retrieves detailed information about a specific release.

Read-only operation, no data modification.

safe
getArtist

Retrieves detailed information about a specific artist.

Read-only operation, no data modification.

moderate
addToCollection

Adds a release to the user's Discogs collection.

Adds data to the user's collection, but does not modify existing data.

high
removeFromCollection

Removes a release from the user's Discogs collection.

Deletes data from the user's collection.

high
updateCollectionItem

Updates information about a specific item in the user's collection.

Modifies existing data in the user's collection.

Safety Assessment

This MCP server offers powerful tools for interacting with the Discogs API, but it also carries the risk of unintended data modification. It is safe to use for read-only operations and exploration, but users should exercise caution and verify actions before executing any write operations. The use of a personal access token adds a layer of security, but the token itself must be protected.

  • Requires a personal access token for authentication.
  • Uses FastMCP framework, providing a level of structure and security.
  • Includes a default `per_page` limit to reduce data processing load.
  • Allows inspection via MCP Inspector for testing and validation.
  • Provides options for local development and Docker deployment.
  • Allows for editing data in your Discogs collection, posing a risk of unintended changes.
  • Relies on the Discogs API, which may have undocumented or inconsistent endpoints.
  • Type safety for all possible API responses is not fully verified.
  • Requires careful handling of the Discogs personal access token.
  • Potential for large API responses if `per_page` is increased.