Log inSubmit server
Discogs MCP Server logo

Discogs MCP Server

by cswkim

Connects an MCP-compatible client to Discogs for catalog searches and collection operations.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Discogs MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "cswkim-discogs-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "discogs-mcp-server"
      ],
      "env": {
        "DISCOGS_PERSONAL_ACCESS_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y discogs-mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 25d ago.

Overview

The cswkim/discogs-mcp-server MCP server connects MCP clients to the Discogs API for music catalog operations, searches, and collection management. It uses a Discogs personal access token and can run through NPX, a local Node setup, Docker, or HTTP streaming mode. Reach for it when an agent needs to find Discogs data or modify collection records. Collection edits require care, and responses default to five items per page to limit client-side context.

Use cases

  • Search Discogs releases by natural-language criteria
  • Inspect music catalog information through an MCP client
  • Review or update records in a Discogs collection
  • Run Discogs queries from a local Docker deployment

Key features

  • Discogs API search
  • Music catalog operations
  • Discogs collection access and editing
  • NPX, local Node, and Docker execution
  • HTTP streaming mode
  • Configurable response page size

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

19/19 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · discogs-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars131Stargazers on the source repository.
npm downloads470Package downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Discogs MCP Server works

What cswkim/discogs-mcp-server MCP server does

The cswkim/discogs-mcp-server MCP server exposes Discogs API functionality to MCP-compatible clients. Its documented purpose covers music catalog operations, search, and interaction with a Discogs collection.

Collection access is not limited to read-only queries. The server supports editing data in a Discogs collection, so an agent can potentially make changes rather than only retrieve catalog information. Use confirmation and review steps before allowing write operations.

How it works

The server is implemented in TypeScript with FastMCP and authenticates against Discogs using a personal access token. An MCP client starts the server and presents its tools to an agent. The repository supports standard local execution and an HTTP streaming development mode. Docker can also be used for local deployment.

Discogs responses can be large. This project sets its default per_page value to 5, instead of relying on the Discogs API default of 50. Prompts may request larger result sets, but clients with limited context can have trouble processing them.

Setup and configuration

A Discogs personal access token is required. Create a .env file from .env.example and set DISCOGS_PERSONAL_ACCESS_TOKEN; the token is available from the Discogs developer settings page and should not be shared.

For the package-based route, an MCP client can launch npx -y discogs-mcp-server. The repository also documents local Node execution after pnpm install, plus a Docker workflow using an image built from the project. Claude Desktop, LibreChat, and LM Studio configuration examples are included in the README.

SERVER_HOST is optional and defaults to 0.0.0.0. Set it to 127.0.0.1 when the server should accept connections only from the local machine. The project also documents development, production, and HTTP streaming commands, along with MCP Inspector access at http://127.0.0.1:6274.

Tools and capabilities

The cswkim/discogs-mcp-server MCP server is intended for:

  • Searching Discogs data
  • Performing music catalog operations
  • Reading and editing Discogs collection data
  • Returning Discogs API results through MCP tools

Inventory uploading is listed as a missing capability in the project's TODO section.

Limitations and notes

Discogs API documentation contains incomplete or inconsistent endpoint details, and the project cannot verify type safety for every possible response type. Type-related issues may therefore occur for less common API responses.

OAuth support is not currently available; authentication uses a personal access token. Collection-editing tools can change remote data, so verify proposed actions before execution. The reduced default page size helps control response volume but does not prevent larger responses when explicitly requested.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Discogs MCP Server

cswkim/discogs-mcp-server is an MCP server that connects MCP-compatible clients to the Discogs API. Its main tools support music catalog operations, Discogs searches, and collection access, including collection editing. It authenticates with a Discogs personal access token and can be launched with NPX, locally, or through Docker.

Install it by launching the package with `npx -y discogs-mcp-server` or by cloning the repository and running `pnpm install`. Set `DISCOGS_PERSONAL_ACCESS_TOKEN` in the client configuration or a `.env` file. Docker is also documented as an alternative after building the image.

The required variable is `DISCOGS_PERSONAL_ACCESS_TOKEN`. It must contain a Discogs personal access token. `SERVER_HOST` is optional and controls the bind address, defaulting to `0.0.0.0`.

The project includes configuration examples for Claude Desktop, LibreChat, and LM Studio, and supports MCP transports and launch methods that may be usable with other clients.

Yes, it supports editing data in a Discogs collection. Review and confirm write actions before execution because they can modify remote Discogs data. Inventory uploading is listed as a capability that is still missing.

Related MCP servers

All in Art & Culture All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDiscogs MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/cswkim-discogs-mcp-server?style=directory)](https://allmcps.com/mcp/cswkim-discogs-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/cswkim-discogs-mcp-server"><img src="https://allmcps.com/api/badge/cswkim-discogs-mcp-server?style=directory" alt="Discogs MCP Server on AllMCPs" /></a>