home / mcp / discogs mcp server
MCP Server for Discogs
Configuration
View docs{
"mcpServers": {
"cswkim-discogs-mcp-server": {
"command": "npx",
"args": [
"-y",
"discogs-mcp-server"
],
"env": {
"DISCOGS_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
}
}
}
}You run a dedicated MCP server that exposes Discogs data and operations to compatible MCP clients. It lets you query your Discogs catalog, search, and perform actions through trusted MCP clients, with local testing via an inspector tool for quick validation.
You connect an MCP client to the Discogs MCP Server to perform catalog operations, search, and other Discogs API-based tasks. Start a local server or run it via Docker, then point your MCP client to the local endpoint or the Docker container. Use the built-in MCP Inspector to verify the server is responding and to interact with available endpoints. When you first access a new tool from Claude, LibreChat, or LM Studio, you will be prompted for permission to run that tool; grant it once per tool per chat as needed.
Prerequisites: Install Node.js (the setup is tested with Node.js 20.x; Node 18.x should work). Ensure you have Docker if you plan to run a containerized instance.
Follow these steps to install and run the Discogs MCP Server locally or via Docker.
Configuration notes: You must provide your Discogs personal access token to enable API access. The server binds by default to 0.0.0.0, allowing connections from external hosts unless you override with localhost. The default per-page setting in responses is small to keep payloads manageable; you can request more data in prompts, but large responses may be heavy for some clients.
Launches a local inspection endpoint to test and interact with your MCP server at http://127.0.0.1:6274. Use it to verify server health and available endpoints.