← Directory

cswkim/discogs-mcp-server

Open Source
• Updated Jun 4, 2026, 06:31 PM

The Discogs MCP Server is an open-source implementation of the Model Context Protocol (MCP) that enables AI assistants, such as Claude or other MCP-compatible clients, to interact with the Discogs music database API.

Use Cases ▼
01

Ask an AI assistant to fetch the tracklist, release date, and label for a specific album by artist and title.

02

Retrieve complete discography data for an artist, including main releases, appearances, and credits.

03

Search for vinyl releases of a particular genre within a given year, and compare marketplace prices.

04

Look up detailed information about a record label, including its most popular releases and sub-labels.

05

Integrate music metadata into a chatbot that helps users catalog their personal record collection or discover new music.

What Problem It Solves ▼

AI assistants and automated agents often need access to authoritative music metadata—such as release details, artist discographies, label information, and marketplace data—but lack a built-in capability to query specialized APIs like Discogs. This server solves that problem by providing a ready-to-use, MCP-compliant interface that enables AI models to programmatically retrieve and explore the vast Discogs database. It eliminates the need for developers to build custom integrations, handle authentication, or manage response formatting, thereby accelerating the development of music-aware AI applications.

Key Features ▼
✓

Simple setup with minimal configuration (only API credentials needed).

✓

Works out-of-the-box with MCP-compatible AI assistants.

✓

Covers essential Discogs API endpoints for music metadata retrieval.

✓

Open-source and actively maintained.

✓

Extensible – other Discogs endpoints can be added.

Overview

The Discogs MCP Server is an open-source implementation of the Model Context Protocol (MCP) that enables AI assistants, such as Claude or other MCP-compatible clients, to interact with the Discogs music database API. It acts as a bridge, translating natural language or structured queries from the AI into authenticated HTTP requests to the Discogs API, and returning the results in a format consumable by the assistant. The server exposes a set of tools (like search, get_release, get_artist, etc.) that map to the most commonly used Discogs API endpoints. It requires a valid Discogs API consumer key and secret, which are configured via environment variables. The server runs as a standalone Node.js process and communicates with the MCP client over standard I/O, making it easy to integrate into any MCP-compatible environment, including local development setups and cloud-hosted AI agents.

Pros & Cons

Pros

+

Simple setup with minimal configuration (only API credentials needed).

+

Works out-of-the-box with MCP-compatible AI assistants.

+

Covers essential Discogs API endpoints for music metadata retrieval.

+

Open-source and actively maintained.

+

Extensible – other Discogs endpoints can be added.

Cons

−

Limited to the scope of Discogs API; does not support other music databases like Spotify or MusicBrainz.

−

Subject to Discogs API rate limits and requires a stable internet connection.

−

Documentation may be sparse, relying on community contributions.

Similar Tools

discogs-client (direct Node.js library) spotify-mcp-server musicbrainz-mcp-server lastfm-api-client

More in Developer Tools