2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 13 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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·json
{
  "mcpServers": {
    "discogs": {
      "url": "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.

GitHub Copilot Agent mode brings Discogs data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 13 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

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

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Discogs

Ask Copilot: "Using Discogs, help me...". 13 tools available

Why Use VS Code Copilot with the Discogs MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Discogs through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Discogs + VS Code Copilot Use Cases

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

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Discogs MCP Tools for VS Code Copilot (13)

These 13 tools become available when you connect Discogs to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

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

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Discogs + VS Code Copilot FAQ

Common questions about integrating Discogs MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Discogs to VS Code Copilot

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