Purpose: An MCP server that connects to the Discogs API, supporting music catalog operations, search, and other features, callable by MCP clients.
Main capabilities: Provides operations such as editing Discogs collection data and searching; see the project's TOOLS.md for the tool list. The built-in discogs.config.defaultPerPage defaults to 5 (the Discogs API default is 50); more data can be requested in prompts.
Usage: Requires Node.js (tested on 20.x; 18.x also works) and a Discogs personal access token. After cloning the repository, create .env based on .env.example and set DISCOGS_PERSONAL_ACCESS_TOKEN (obtained in Discogs Settings > Developers; never share it). Optional variable SERVER_HOST (default 0.0.0.0). Local development: pnpm install; commands such as pnpm run dev, pnpm run build, pnpm run start, and pnpm run inspect are available. Docker: docker build -t discogs-mcp-server:latest ., docker run --env-file .env discogs-mcp-server:latest; for HTTP stream mode add -p 3001:3001 … stream. Client configuration supports Claude Desktop (NPX/local Node/Docker), LibreChat, and LM Studio.
Limitations: The Discogs API documentation is incomplete; some endpoints are not fully documented or are inconsistent, so type-safe validation cannot be performed for all responses; this server can edit Discogs collection data, so operate with caution; OAuth support will be added in a future version; inventory upload tools are missing; large responses may exceed the processing capacity of some clients; after local code changes, Claude must be restarted, and tool calls require manual confirmation.
