# cswkim/discogs-mcp-server [Health: Active]

**Category:** 🎨 Art & Culture  
**Repository:** https://github.com/cswkim/discogs-mcp-server  
**GitHub Stars:** 131  
**npm Downloads (last month):** 470  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/cswkim-discogs-mcp-server

## Description
MCP server to interact with the Discogs API

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

**Requires environment variables:** `DISCOGS_PERSONAL_ACCESS_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/cswkim-discogs-mcp-server/readme_