2,500+ MCP servers ready to use
Vinkius

Discogs MCP Server for Claude Code 13 tools — connect in under 2 minutes

Built by Vinkius GDPR 13 Tools CLI

Claude Code is Anthropic's agentic CLI for terminal-first development. Add Discogs as an MCP server in one command and Claude Code will discover every tool at runtime. ideal for automation pipelines, CI/CD integration, and headless workflows via Vinkius.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Discogs and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·bash
# Your Vinkius token. get it at cloud.vinkius.com
claude mcp add discogs --transport http "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
Discogs
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Discogs MCP Server

Unlock the power of the Discogs music database — the most comprehensive catalog of music recordings, releases, and marketplace data. Connect Discogs to your AI agent to instantly search artists, explore complete discographies, examine release details, research labels, browse marketplace listings, and analyze collector statistics — all through natural conversation.

Claude Code registers Discogs as an MCP server in a single terminal command. Once connected, Claude Code discovers all 13 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Discogs data drives decisions without human intervention.

What you can do

  • Database Search — Free-text search across artists, releases, labels, and tracks with filters for genre, style, year, country, and format.
  • Artist Profiles — Retrieve complete artist information including biography, members, and full discography.
  • Release Details — Get comprehensive metadata for any release including tracklists, formats, credits, and release history.
  • Master Releases — Understand the canonical version of a release and explore all pressings and variants.
  • Label Research — Explore record label catalogs, corporate structures, sublabels, and complete release histories.
  • Marketplace Intelligence — Browse active listings, compare prices, check conditions, and find the best deals.
  • Collector Statistics — Access community data on release popularity, wantlist counts, and sale price history.
  • User Collections — View public collections and wantlists to understand what collectors value.

The Discogs MCP Server exposes 13 tools through the Vinkius. Connect it to Claude Code in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Discogs to Claude Code via MCP

Follow these steps to integrate the Discogs MCP Server with Claude Code.

01

Install Claude Code

Run npm install -g @anthropic-ai/claude-code if not already installed

02

Add the MCP Server

Run the command above in your terminal

03

Verify the connection

Run claude mcp to list connected servers, or type /mcp inside a session

04

Start using Discogs

Ask Claude: "Using Discogs, show me...". 13 tools are ready

Why Use Claude Code with the Discogs MCP Server

Claude Code provides unique advantages when paired with Discogs through the Model Context Protocol.

01

Single-command setup: `claude mcp add` registers the server instantly. no config files to edit or applications to restart

02

Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks

03

Claude Code runs headlessly, enabling unattended batch processing using Discogs tools in cron jobs or deployment scripts

04

Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

Discogs + Claude Code Use Cases

Practical scenarios where Claude Code combined with the Discogs MCP Server delivers measurable value.

01

CI/CD integration: embed Discogs tool calls in your deployment pipeline to validate configurations or fetch secrets before shipping

02

Headless batch processing: schedule Claude Code to query Discogs nightly and generate reports without human intervention

03

Shell scripting: pipe Discogs outputs into other CLI tools for data transformation, filtering, and aggregation

04

Infrastructure monitoring: run Claude Code in a cron job to query Discogs status endpoints and alert on anomalies

Discogs MCP Tools for Claude Code (13)

These 13 tools become available when you connect Discogs to Claude Code via MCP:

01

database_search

Use the query parameter for free-text search across artists, releases, labels, and tracks. Refine results by type (artist, release, master, label, genre) and filters like genre, style, year, or country. Returns paginated results with basic metadata. Use this as the starting point for most queries. Type parameter accepts: artist, release, master, label, genre. Search the Discogs database for artists, releases, labels, and more

02

get_artist

Returns the artist name, real name, profile/biography, members (for groups), URLs, and images. Use this after identifying an artist ID from search results. Get detailed information about a specific artist

03

get_artist_releases

Includes albums, singles, compilations, and credits on other releases. Results are sorted by year and include format, label, and track count. Use pagination to navigate large discographies. Returns a comprehensive overview of an artist's recorded output. Get the complete discography of an artist

04

get_label

Returns the label name, profile/description, parent label, sublabels, contact info, and associated releases. Use this to research label history, corporate structures, and catalog organization. Get information about a record label

05

get_label_releases

Returns release titles, artists, formats, catalog numbers, and release dates. Useful for researching a label's catalog, identifying rare pressings, or exploring a label's musical output. Use pagination to navigate large catalogs. Get releases published by a specific label

06

get_marketplace_listings

Returns seller information, price, currency, condition (media and sleeve), comments, and shipping location. Useful for finding the best deals, comparing conditions, or understanding market value. Sort by price, condition, or country. Filter by minimum/maximum condition. Get marketplace listings for a specific release

07

get_master_release

A master release represents the "canonical" version of a release, grouping together all individual pressings and variants. Returns the main artist, title, year, genres, styles, tracklist, and notes. Use this to understand the core creative work independent of specific pressings. Get information about a master release

08

get_master_release_versions

Each version represents a different pressing, reissue, or format of the same core release. Returns details including country, year, format, label, and catalog number for each version. Useful for collectors comparing different pressings or finding specific editions. Get all versions (pressings) of a master release

09

get_release

Returns the release title, artist, tracklist, formats, labels, catalog numbers, release date, country, genres, styles, credits, notes, and marketplace data. This is the most detailed view of a specific physical or digital release. Use this to get complete metadata for cataloging or research. Get detailed information about a specific release

10

get_release_stats

Returns the lowest, median, and highest sale prices, as well as the number of active listings. Useful for understanding rarity, market demand, and fair pricing for collectors. Get community statistics and marketplace data for a release

11

get_user_collection

Returns each release with basic metadata including artist, title, year, and format. Note: only the collection owner can see detailed information including condition, notes, and custom fields. Public collections show limited data. Use pagination to navigate large collections. Get a user's collection of releases

12

get_user_profile

Returns the user's location, homepage, bio, member since date, number of contributions, and collection/wantlist counts. Use this to verify user identity or get an overview of a collector's activity on the platform. Get a Discogs user's public profile

13

get_user_wantlist

Returns each release with basic metadata. Only the wantlist owner can see this data unless they've made it public. Useful for tracking what collectors are seeking. Get a user's wantlist of desired releases

Example Prompts for Discogs in Claude Code

Ready-to-use prompts you can give your Claude Code agent to start working with Discogs immediately.

01

"Search for Pink Floyd's 'The Dark Side of the Moon' and show me all vinyl pressings."

02

"Show me the complete discography of Daft Punk."

03

"What's the market value of the original 1969 Beatles 'Abbey Road' vinyl in good condition?"

Troubleshooting Discogs MCP Server with Claude Code

Common issues when connecting Discogs to Claude Code through the Vinkius, and how to resolve them.

01

Command not found: claude

Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
02

Connection timeout

Check your internet connection and verify the Edge URL is reachable

Discogs + Claude Code FAQ

Common questions about integrating Discogs MCP Server with Claude Code.

01

How do I add an MCP server to Claude Code?

Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
02

Can Claude Code run MCP tools in headless mode?

Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
03

How do I list all connected MCP servers?

Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.

Connect Discogs to Claude Code

Get your token, paste the configuration, and start using 13 tools in under 2 minutes. No API key management needed.