Discogs logo discogs.com

Live

Discogs API and MCP server

Discogs' API gives a release only the number of copies for sale and the lowest price, not the copies themselves. Sign in to Discogs once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with Discogs.

Discogs has no API for this. So we run one for you.

Discogs's own API, a GitHub MCP server and Cotlet compared
What you need Discogs's APIGitHub MCP serverCotlet
Copies for sale of a release No Partly Yes, 13 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Discogs changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 17, 2026. Sources: Discogs API documentation · Discogs API: Marketplace listing · Discogs Help: Change Prices · Discogs Help: How can I update the status of an order?

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Discogs in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Discogs to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 13 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Discogs and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
    Codex
    # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/discogs with its own method and path, such as PATCH /api/v1/discogs/listings/{listing_id}/price, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Discogs API and MCP server do?

13 tools on your own Discogs account. Agents call them as operations of the MCP tools discogs_read and discogs_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
Discogs tools in Cotlet's MCP server and REST API
Tool What it does Access
search_releases Search the Discogs database by artist, title, catalog number or barcode. read
get_release Read one release: tracklist, formats, labels, and how many copies are for sale. read
list_release_listings List the copies of one release that sellers have for sale now. read
list_inventory List your own marketplace listings with price, status and release. read
list_orders List the orders you sold, filtered by status. read
get_order Read one order: items, status, shipping and the message thread with the buyer. read
list_collection List the releases in your Discogs collection, with folder. read
list_wantlist List the releases on your Discogs wantlist. read
add_to_collection Add a release to a folder of your collection. write
add_to_wantlist Add a release to your Discogs wantlist. write
update_listing_price Change the price of one of your marketplace listings. writeasks first
update_order_status Move one of your orders to the next status and tell the buyer. writeasks first
send_order_message Send a message to the buyer on an order. writeasks first

Scroll the table for all 13 tools.

Ask in plain words. Your agent does the rest.

All Discogs use cases

Is it safe to connect Discogs?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the Discogs API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Discogs is enabled for agents, so 20 calls a day come to 550 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 25 credits each
Credits Price, one time Calls at 25 credits Per 1,000 credits
5,000 $29 200 $5.80
15,000 $79 600 $5.27
32,000 $149 1,280 $4.66
60,000 $249 2,400 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does Discogs have an API?

Discogs has a full REST API, version 2, that covers the database, collections, wantlists, marketplace inventory and orders, but no official MCP server (checked 17 Oct 2026). Authenticated requests are limited to 60 per minute and unauthenticated ones to 25. For orders and private inventory data you need a personal access token or an OAuth app.

How do I get access?

Sign up free, open Discogs under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 13 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Discogs yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Discogs sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: update_listing_price, update_order_status, send_order_message wait for your OK by default. You can switch that off per tool for scheduled runs.

Do I need a seller account for the order and listing tools?

Yes. Orders and inventory exist only on a Discogs account that sells. The collection, wantlist and release tools work on any account. Only the seller can change the status of an order (Discogs Help, checked 17 Oct 2026).

Does the 60 requests per minute limit apply to Cotlet?

Discogs limits authenticated API requests to 60 per minute and unauthenticated ones to 25 (Discogs API documentation, checked 17 Oct 2026). A script on the API has to throttle itself. Cotlet works in your signed-in Discogs session instead of through your own API token. Long runs over thousands of listings still take time.

Should I use a Discogs MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Discogs changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with Discogs?

No. Cotlet is independent and not affiliated with Discogs.

Give your agent access to Discogs.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free