2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 13 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect Discogs through Vinkius and Mastra agents discover all tools automatically. type-safe, streaming-ready, and deployable anywhere Node.js runs.

Vinkius supports streamable HTTP and SSE.

typescript
import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

async function main() {
  // Your Vinkius token. get it at cloud.vinkius.com
  const mcpClient = await createMCPClient({
    servers: {
      "discogs": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "Discogs Agent",
    instructions:
      "You help users interact with Discogs " +
      "using 13 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with Discogs?"
  );
  console.log(result.text);
}

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.

Mastra's agent abstraction provides a clean separation between LLM logic and Discogs tool infrastructure. Connect 13 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.

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 Mastra AI 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 Mastra AI via MCP

Follow these steps to integrate the Discogs MCP Server with Mastra AI.

01

Install dependencies

Run npm install @mastra/core @mastra/mcp @ai-sdk/openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.ts and run with npx tsx agent.ts

04

Explore tools

Mastra discovers 13 tools from Discogs via MCP

Why Use Mastra AI with the Discogs MCP Server

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

01

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add Discogs without touching business code

02

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

03

TypeScript-native: full type inference for every Discogs tool response with IDE autocomplete and compile-time checks

04

One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure

Discogs + Mastra AI Use Cases

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

01

Automated workflows: build multi-step agents that query Discogs, process results, and trigger downstream actions in a typed pipeline

02

SaaS integrations: embed Discogs as a first-class tool in your product's AI features with Mastra's clean agent API

03

Background jobs: schedule Mastra agents to query Discogs on a cron and store results in your database automatically

04

Multi-agent systems: create specialist agents that collaborate using Discogs tools alongside other MCP servers

Discogs MCP Tools for Mastra AI (13)

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

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

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

01

createMCPClient not exported

Install: npm install @mastra/mcp

Discogs + Mastra AI FAQ

Common questions about integrating Discogs MCP Server with Mastra AI.

01

How does Mastra AI connect to MCP servers?

Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
02

Can Mastra agents use tools from multiple servers?

Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
03

Does Mastra support workflow orchestration?

Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.

Connect Discogs to Mastra AI

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