2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 13 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Discogs as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to Discogs. "
            "You have 13 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in Discogs?"
    )
    print(response)

asyncio.run(main())
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.

LlamaIndex agents combine Discogs tool responses with indexed documents for comprehensive, grounded answers. Connect 13 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

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 LlamaIndex 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 LlamaIndex via MCP

Follow these steps to integrate the Discogs MCP Server with LlamaIndex.

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 13 tools from Discogs

Why Use LlamaIndex with the Discogs MCP Server

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

01

Data-first architecture: LlamaIndex agents combine Discogs tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain Discogs tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query Discogs, a vector store, and a SQL database in a single turn and synthesize results

04

Observability integrations show exactly what Discogs tools were called, what data was returned, and how it influenced the final answer

Discogs + LlamaIndex Use Cases

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

01

Hybrid search: combine Discogs real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query Discogs to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Discogs for fresh data

04

Analytical workflows: chain Discogs queries with LlamaIndex's data connectors to build multi-source analytical reports

Discogs MCP Tools for LlamaIndex (13)

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

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

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

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Discogs + LlamaIndex FAQ

Common questions about integrating Discogs MCP Server with LlamaIndex.

01

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
02

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query Discogs tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Connect Discogs to LlamaIndex

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