Discogs MCP Server

Created By
thesimsguya year ago
Overview

what is Discogs MCP Server?

Discogs MCP Server is a server application that interfaces with the Discogs API, enabling users to perform music catalog operations, search functionalities, and more.

how to use Discogs MCP Server?

To use the Discogs MCP Server, you need to have Node.js installed and a personal access token from Discogs. You can run the server locally or via Docker, and configure it to work with the Claude desktop app.

key features of Discogs MCP Server?

  • Integration with the Discogs API for music catalog management.
  • Support for local development and Docker deployment.
  • MCP Inspector for testing and inspecting the server.

use cases of Discogs MCP Server?

  1. Managing personal music collections through the Discogs API.
  2. Searching for music catalog entries efficiently.
  3. Developing applications that require music data from Discogs.

FAQ from Discogs MCP Server?

  • What is required to run the server?

You need Node.js and a Discogs personal access token.

  • Can I run it using Docker?

Yes, the server can be run using Docker for easier setup.

  • Is there support for OAuth?

OAuth support is planned for a future release.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
thesimsguy
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago