Loading...
MCP server for Discogs API, enabling music catalog management, search, and data manipulation with caution due to potential data editing capabilities.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
MCP server for Discogs API, enabling music catalog management, search, and data manipulation with caution due to potential data editing capabilities.
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.
Performance is largely dependent on the Discogs API response times and the client's ability to process data. Consider implementing caching mechanisms to improve performance for frequently accessed data.
Cost is primarily related to Discogs API usage. Be mindful of API rate limits and usage quotas to avoid unexpected charges or service disruptions.
{
"mcpServers": {
"discogs": {
"command": "npx",
"args": [
"-y",
"discogs-mcp-server"
],
"env": {
"DISCOGS_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
}
}
}
}searchSearches the Discogs database for releases, artists, labels, etc.
Read-only operation, no data modification.
getReleaseRetrieves detailed information about a specific release.
Read-only operation, no data modification.
getArtistRetrieves detailed information about a specific artist.
Read-only operation, no data modification.
addToCollectionAdds a release to the user's Discogs collection.
Adds data to the user's collection, but does not modify existing data.
removeFromCollectionRemoves a release from the user's Discogs collection.
Deletes data from the user's collection.
updateCollectionItemUpdates information about a specific item in the user's collection.
Modifies existing data in the user's collection.
API Key
hybrid
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.
Autonomy should be carefully managed due to the presence of tools that can modify or delete data in the user's Discogs collection. Consider implementing safeguards and confirmation steps to prevent unintended actions.
Production Tip
Monitor API usage and error rates to ensure the server is functioning correctly and not exceeding Discogs API rate limits.
A Discogs personal access token is a credential that allows the MCP server to access your Discogs account on your behalf. You need it to authenticate with the Discogs API and perform actions such as adding releases to your collection.
You can generate a personal access token on the Discogs Settings > Developers page. Make sure to keep your token secret and do not share it with anyone.
The main risks are accidental modification or deletion of your Discogs collection data, and exposure of your Discogs personal access token if not handled securely.
Be careful when executing write operations, verify your actions before confirming them, and protect your Discogs personal access token.
The server is known to be compatible with Claude Desktop, and may be compatible with other MCP clients such as Cursor, Windsurf, and VS Code (Copilot), but these have not been fully tested.
Yes, you can use this MCP server to automate tasks such as adding releases to your collection, removing releases, and updating information about items in your collection.
The error handling depends on the underlying Discogs API and the FastMCP framework. Check the server logs and the Discogs API documentation for more information.