Discogs MCP Server

What is Discogs MCP Server about?

Wraps the Discogs API as an MCP server, allowing AI assistants and other MCP‑compatible tools to query and modify a user's Discogs collection, perform searches, and retrieve detailed release information.

How to use Discogs MCP Server?

1. Prerequisites – Install Node.js (v18‑v20) or Docker.
2. Configure – Create a .env file from .env.example and set DISCOGS_PERSONAL_ACCESS_TOKEN with your personal access token.
3. Start the server
   • Local development: pnpm install && pnpm run dev (or dev:stream for HTTP streaming).
   • Docker: docker build -t discogs-mcp-server . then docker run --env-file .env discogs-mcp-server (add -p 3001:3001 and stream argument for streaming mode).
4. Connect a client – Add the MCP server configuration to Claude Desktop, LibreChat, LM Studio, or any MCP‑compatible client.

Key features of Discogs MCP Server

• Search releases, artists, labels, and collections via MCP calls.
• Retrieve detailed metadata, tracklists, and images.
• Edit and manage your Discogs collection (add/remove releases, update folders, etc.).
• Configurable per_page default (5) to keep responses lightweight.
• Supports both STDIO and HTTP streaming transports.
• Ready‑to‑run via npx, local Node, or Docker.

Use cases of Discogs MCP Server

• Enabling AI assistants (e.g., Claude) to answer music‑related queries using a user’s personal Discogs library.
• Building custom chatbot tools that recommend albums or track down rare releases.
• Automating bulk collection updates or inventory uploads (future OAuth support).
• Integrating Discogs data into personal dashboards or music recommendation engines.

FAQ from the Discogs MCP Server

Q: Do I need to share my Discogs token? A: No. Set it only in your local .env file; never commit or share the token.

Q: Why is the default per_page set to 5? A: To avoid overwhelming MCP clients with large payloads; you can request more items in prompts when needed.

Q: Can I use OAuth instead of a personal token? A: OAuth support is planned for a future release.

Q: Which transport should I choose? A: Use STDIO (pnpm run dev) for local development; use HTTP streaming (dev:stream or Docker stream) for clients that require a persistent HTTP connection.

Q: How do I test the server locally? A: Run pnpm run inspect to launch the MCP Inspector at http://127.0.0.1:6274.

Discogs MCP Server

MCP Server for the Discogs API, enabling music catalog operations, search functionality, and more.

Quickstart

If you just want to get started immediately using this MCP Server with the Claude desktop app and don't care about development or running the server yourself, then make sure you have Node.js installed and your Discogs personal access token ready and skip straight to the Claude configuration section. Use the NPX method from that section.

Table of Contents

• Acknowledgements
• Available Tools
• Caveats
• Prerequisites
• Setup
• Running the Server
  • Option 1: Local Development
  • Option 2: Docker
• Inspection
• MCP Clients
  • Claude Desktop Configuration
    • NPX
    • Local Node
    • Docker
  • LibreChat
  • LM Studio
• TODO
• License

Acknowledgements

This MCP server is built using FastMCP, a typescript framework for building MCP servers. For more information about MCP and how to use MCP servers, please refer to the FastMCP documentation and the official MCP documentation.

Available Tools

Check out the list of available tools: TOOLS.md

Caveats

• The Discogs API documentation is not perfect and some endpoints may not be fully documented or may have inconsistencies.
• Due to the vast number of API endpoints and response types, it's not feasible to verify type safety for every possible response. Please report any type-related issues you encounter.
• This MCP server allows for editing data in your Discogs collection. Please use with caution and verify your actions before executing them.
• The Discogs API per_page default is 50, which can be too much data for some clients to process effectively, so within this project a discogs.config.defaultPerPage value has been set to 5. You can request more data in your prompts, but be aware that some clients may struggle with larger responses.

Prerequisites

• Node.js (tested with Node.js 20.x.x, but 18.x.x should work as well)
  • Check your Node.js version with: node --version
• Docker (optional, for running a local docker image without having to deal with Node or dependencies)

Setup

1. Clone the repository
2. Create a .env file in the root directory based on .env.example
3. Set the following required environment variables in your .env:
   • DISCOGS_PERSONAL_ACCESS_TOKEN: Your Discogs personal access token

To get your Discogs personal access token, go to your Discogs Settings > Developers page and find your token or generate a new one. DO NOT SHARE YOUR TOKEN. OAuth support will be added in a future release.

The other environment variables in .env.example are optional and have sensible defaults, so you don't need to set them unless you have specific requirements.

Running the Server Locally

Option 1: Local Development

1. Install dependencies:

   pnpm install
   

2. Available commands:

   • pnpm run dev: Start the development server with hot reloading
   • pnpm run dev:stream: Start the development server with hot reloading in HTTP streaming mode
   • pnpm run build: Build the production version
   • pnpm run start: Run the production build
   • pnpm run inspect: Run the MCP Inspector (see Inspection section)
   • pnpm run format: Check code formatting (prettier)
   • pnpm run lint: Run linter (eslint)
   • pnpm run test: Run vitest
   • pnpm run test:coverage: Run vitest v8 coverage
   • pnpm run version:check: Checks that the package.json version and src/version.ts match

Option 2: Docker

1. Build the Docker image:

   docker build -t discogs-mcp-server:latest .
   

2. Run the container:

   docker run --env-file .env discogs-mcp-server:latest
   

   For HTTP Streaming transport mode:

   # The port should match what is in your .env file
   docker run --env-file .env -p 3001:3001 discogs-mcp-server:latest stream
   

Inspection

Run the MCP Inspector to test your local MCP server:

pnpm run inspect

This will start the MCP Inspector at http://127.0.0.1:6274. Visit this URL in your browser to interact with your local MCP server.

For more information about the MCP Inspector, visit the official documentation.

MCP Clients

More client examples will be added in the future. If you'd like configuration for a specific client, either request it by opening a new issue or creating the pull request to edit this section of the README yourself.

Claude Desktop Configuration

Find your claude_desktop_config.json at Claude > Settings > Developer > Edit Config and depending on which option you'd like, add JUST ONE of the following:

NPX

Running it straight from the npm registry.

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

Local Node

Dependencies should have been installed before you use this method (pnpm install).

{
  "mcpServers": {
    "discogs": {
      "command": "npx",
      "args": [
        "tsx",
        "/PATH/TO/YOUR/PROJECT/FOLDER/src/index.ts"
      ],
      "env": {
        "DISCOGS_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

Docker

The docker image should have been built before using this method.

{
  "mcpServers": {
    "discogs": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "--env-file",
        "/PATH/TO/YOUR/PROJECT/FOLDER/.env",
        "discogs-mcp-server:latest"
      ]
    }
  }
}

Any changes to local code will require Claude to be restarted to take effect. Also, Claude requires human-in-the-loop interaction to allow an MCP tool to be run, so everytime a new tool is accessed Claude will ask for permission. You usually only have to do this once per tool per chat. If using the free version, long chats may result in more frequent errors trying to run tools as Claude limits the amount of context within a single chat.

LibreChat

In the librechat.yaml configuration file, add this under the mcpServers section:

discogs:
  type: stdio
  command: npx
  args: ["-y", "discogs-mcp-server"]
  env:
    DISCOGS_PERSONAL_ACCESS_TOKEN: YOUR_TOKEN_GOES_HERE

LM Studio

Get to the Chat Settings. In the Program tab there will be a dropdown with a default of Install. Select Edit mcp.json. Add this under the mcpServers section:

"discogs": {
  "command": "npx",
  "args": [
    "-y",
    "discogs-mcp-server"
  ],
  "env": {
    "DISCOGS_PERSONAL_ACCESS_TOKEN": "YOUR_TOKEN_GOES_HERE"
  }
}

After you Save, in the Program tab there should now be an mcp/discogs toggle to enable the server. Within every chat box there is an Integrations menu where you can also enable mcp servers.

TODO

• OAuth support
• Missing tools:
  • Inventory uploading

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.