Skip to content
Back to search

discogs-mcp-server

MCP Server for Discogs

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/cswkim--discogs-mcp-server/badge.svg)](/listings/cswkim--discogs-mcp-server)

HTML

<a href="/listings/cswkim--discogs-mcp-server"><img src="/api/listings/cswkim--discogs-mcp-server/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

If you just want to get started immediately using this MCP Server with the [Claude](https://claude.ai) desktop app and don't care about development or running the server yourself, then make sure you have [Node.js](https://nodejs.org/en) installed and your Discogs personal access token ready and skip straight to the [Claude configuration section](#claude-desktop-configuration). Use the `NPX` method from that section.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 237 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. [![License](https://img.shields.io/github/license/cswkim/discogs-mcp-server)](LICENSE)
  2. [![GitHub Release](https://img.shields.io/github/v/release/cswkim/discogs-mcp-server)](https://github.com/cswkim/discogs-mcp-server/releases)
  3. [![GitHub Actions Workflow Status](https://img.shields.io/github/actions/workflow/status/cswkim/discogs-mcp-server/.github%2Fworkflows%2Fcheck-pr.yml)](https://github.com/cswkim/discogs-mcp-server/actions/workflows/check-pr.yml)
  4. [![NPM Downloads](https://img.shields.io/npm/d18m/discogs-mcp-server)](https://www.npmjs.com/package/discogs-mcp-server)
  5. [![Sponsor](https://img.shields.io/static/v1?label=sponsor&message=%E2%9D%A4&logo=GitHub&color=ff69b4)](https://github.com/sponsors/cswkim)
  6. # Discogs MCP Server
  7. MCP Server for the Discogs API, enabling music catalog operations, search functionality, and more.
  8. ## Quickstart
  9. If you just want to get started immediately using this MCP Server with the [Claude](https://claude.ai) desktop app and don't care about development or running the server yourself, then make sure you have [Node.js](https://nodejs.org/en) installed and your Discogs personal access token ready and skip straight to the [Claude configuration section](#claude-desktop-configuration). Use the `NPX` method from that section.
  10. ## Table of Contents
  11. - [Acknowledgements](#acknowledgements)
  12. - [Available Tools](#available-tools)
  13. - [Caveats](#caveats)
  14. - [Prerequisites](#prerequisites)
  15. - [Setup](#setup)
  16. - [Running the Server](#running-the-server-locally)
  17. - [Option 1: Local Development](#option-1-local-development)
  18. - [Option 2: Docker](#option-2-docker)
  19. - [Inspection](#inspection)
  20. - [MCP Clients](#mcp-clients)
  21. - [Claude Desktop Configuration](#claude-desktop-configuration)
  22. - [NPX](#npx)
  23. - [Local Node](#local-node)
  24. - [Docker](#docker)
  25. - [LibreChat](#librechat)
  26. - [LM Studio](#lm-studio)
  27. - [TODO](#todo)
  28. - [License](#license)
  29. ## Acknowledgements
  30. This MCP server is built using [FastMCP](https://github.com/punkpeye/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](https://github.com/punkpeye/fastmcp/blob/main/README.md) and the [official MCP documentation](https://modelcontextprotocol.io).
  31. ## Available Tools
  32. Check out the list of available tools: [TOOLS.md](TOOLS.md)
  33. ## Caveats
  34. - The [Discogs API documentation](https://www.discogs.com/developers) is not perfect and some endpoints may not be fully documented or may have inconsistencies.
  35. - 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.
  36. - This MCP server allows for editing data in your Discogs collection. Please use with caution and verify your actions before executing them.
  37. - 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.
  38. ## Prerequisites
  39. - Node.js (tested with Node.js `20.x.x`, but `18.x.x` should work as well)
  40. - Check your Node.js version with: `node --version`
  41. - Docker (optional, for running a local docker image without having to deal with Node or dependencies)
  42. ## Setup
  43. 1. Clone the repository
  44. 2. Create a `.env` file in the root directory based on `.env.example`
  45. 3. Set the following required environment variables in your `.env`:
  46. - `DISCOGS_PERSONAL_ACCESS_TOKEN`: Your Discogs personal access token
  47. To get your Discogs personal access token, go to your [Discogs Settings > Developers](https://www.discogs.com/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.
  48. 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.
  49. - `SERVER_HOST`: The host address to bind the server to (default: `0.0.0.0`). Set to `0.0.0.0` to allow connections from outside the container/machine, or `127.0.0.1` to restrict to localhost only.
  50. ## Running the Server Locally
  51. ### Option 1: Local Development
  52. 1. Install dependencies:
  53. ```bash
  54. pnpm install
  55. ```
  56. 2. Available commands:
  57. - `pnpm run dev`: Start the development server with hot reloading
  58. - `pnpm run dev:stream`: Start the development server with hot reloading in HTTP streaming mode
  59. - `pnpm run build`: Build the production version
  60. - `pnpm run start`: Run the production build
  61. - `pnpm run inspect`: Run the MCP Inspector (see [Inspection](#inspection) section)
  62. - `pnpm run format`: Check code formatting (prettier)
  63. - `pnpm run lint`: Run linter (eslint)
  64. - `pnpm run test`: Run vitest
  65. - `pnpm run test:coverage`: Run vitest v8 coverage
  66. - `pnpm run version:check`: Checks that the package.json version and src/version.ts match
  67. ### Option 2: Docker
  68. 1. Build the Docker image:
  69. ```bash
  70. docker build -t discogs-mcp-server:latest .
  71. ```
  72. 2. Run the container:
  73. ```bash
  74. docker run --env-file .env discogs-mcp-server:latest
  75. ```
  76. For HTTP Streaming transport mode:
  77. ```bash
  78. # The port should match what is in your .env file
  79. # By default, the server listens on 0.0.0.0, allowing connections from outside the container
  80. docker run --env-file .env -p 3001:3001 discogs-mcp-server:latest stream
  81. ```
  82. ## Inspection
  83. Run the MCP Inspector to test your local MCP server:
  84. ```bash
  85. pnpm run inspect
  86. ```
  87. 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.
  88. For more information about the MCP Inspector, visit [the official documentation](https://modelcontextprotocol.io/docs/tools/inspector).
  89. ## MCP Clients
  90. More client examples will be added in the future. If you'd like configuration for a specific client, either
  91. request it by opening a new issue or creating the pull request to edit this section of the README yourself.
  92. ### Claude Desktop Configuration
  93. 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:
  94. #### NPX
  95. Running it straight from the npm registry.
  96. ```json
  97. {
  98. "mcpServers": {
  99. "discogs": {
  100. "command": "npx",
  101. "args": [
  102. "-y",
  103. "discogs-mcp-server"
  104. ],
  105. "env": {
  106. "DISCOGS_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
  107. }
  108. }
  109. }
  110. }
  111. ```
  112. #### Local Node
  113. Dependencies should have been installed before you use this method (`pnpm install`).
  114. ```json
  115. {
  116. "mcpServers": {
  117. "discogs": {
  118. "command": "npx",
  119. "args": [
  120. "tsx",
  121. "/PATH/TO/YOUR/PROJECT/FOLDER/src/index.ts"
  122. ],
  123. "env": {
  124. "DISCOGS_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
  125. }
  126. }
  127. }
  128. }
  129. ```
  130. #### Docker
  131. The docker image should have been built before using this method.
  132. ```json
  133. {
  134. "mcpServers": {
  135. "discogs": {
  136. "command": "docker",
  137. "args": [
  138. "run",
  139. "--rm",
  140. "-i",
  141. "--env-file",
  142. "/PATH/TO/YOUR/PROJECT/FOLDER/.env",
  143. "discogs-mcp-server:latest"
  144. ]
  145. }
  146. }
  147. }
  148. ```
  149. 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._
  150. ### LibreChat
  151. In the `librechat.yaml` configuration file, add this under the `mcpServers` section:
  152. ```yaml
  153. discogs:
  154. type: stdio
  155. command: npx
  156. args: ["-y", "discogs-mcp-server"]
  157. env:
  158. DISCOGS_PERSONAL_ACCESS_TOKEN: YOUR_TOKEN_GOES_HERE
  159. ```
  160. ### LM Studio
  161. 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:
  162. ```json
  163. "discogs": {
  164. "command": "npx",
  165. "args": [
  166. "-y",
  167. "discogs-mcp-server"
  168. ],
  169. "env": {
  170. "DISCOGS_PERSONAL_ACCESS_TOKEN": "YOUR_TOKEN_GOES_HERE"
  171. }
  172. }
  173. ```
  174. 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.
  175. ## TODO
  176. - OAuth support
  177. - Missing tools:
  178. - Inventory uploading
  179. ## License
  180. 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.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.