[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Discogs API and MCP server

> 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.

Music database and marketplace: every release is catalogued, collectors keep a collection and a wantlist, and sellers list copies and ship orders.

## What is the Discogs API?

Cotlet's Discogs API exposes 13 endpoints for your own Discogs account: search releases, get release, list copies for sale of a release, list your inventory, list orders, get order, list your collection, list your wantlist, add release to collection, add release to wantlist, reprice a listing, update order status and message the buyer. The search_releases endpoint returns search the Discogs database by artist, title, catalog number or barcode. Each endpoint takes simple JSON inputs like page, release_id or status and works both as an operation of the discogs_read or discogs_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities.md)
- **Endpoints:** 13 (8 read, 5 write)
- **Updated:** 2026-10-20

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). Cotlet is a hosted MCP server and REST API for Discogs with 13 endpoints (8 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Discogs have an official 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.

| Task | Discogs official | Cotlet |
|---|---|---|
| Search releases and read release details | Yes: Database API; you wire the token and paging yourself | Yes |
| List the copies for sale of one release | No: API returns the number for sale and the lowest price, not the copies | Yes |
| List your inventory and change a listing price | Yes: Marketplace API with your token | Yes |
| List orders and read one order | Yes: Marketplace API, seller token required | Yes |
| Change an order status and write to the buyer | Yes: Marketplace API; no MCP server for agents | Yes |
| List your collection and add a release | Yes: Collection API | Yes |
| List your wantlist and add a release | Yes: Wantlist API | Yes |

Sources: [Discogs API documentation](https://www.discogs.com/developers), [Discogs API: Marketplace listing](https://www.discogs.com/developers/resources/marketplace/listing.html), [Discogs Help: Change Prices](https://support.discogs.com/hc/en-us/articles/48908115787021-Change-Prices), [Discogs Help: How can I update the status of an order?](https://support.discogs.com/hc/en-us/articles/360009082553-How-Can-I-Update-The-Status-Of-An-Order)

## For AI agents

```text
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.
Cotlet provides a hosted MCP server and REST API for Discogs: 13 tools (8 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=discogs, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    discogs_read, discogs_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/discogs, each operation at its own route, e.g. PATCH /api/v1/discogs/listings/{listing_id}/price
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   search_releases, get_release, list_release_listings, list_inventory, list_orders, get_order, list_collection, list_wantlist, add_to_collection, add_to_wantlist, update_listing_price, update_order_status, send_order_message
Confirm      update_listing_price, update_order_status, send_order_message (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/discogs-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=discogs, requests Discogs in the Cotlet console and creates an API key there.
2. The user signs in to Discogs once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Discogs for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Discogs server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Discogs MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Discogs in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Discogs only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Discogs login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Discogs's terms; Cotlet is not affiliated with Discogs.
```

## What can an AI agent do in Discogs?

Cotlet is best for record sellers and collectors who want an agent to reprice listings, ship orders and watch a wantlist without running or fixing a server.

- **[Reprice Discogs listings](https://cotlet.dev/integrations/discogs-api-mcp-server/reprice-listings.md)** (runs: weekly): "List my Discogs inventory. For every listing that is for sale and has been listed more than 90 days, check how many other copies of the release are for sale and the lowest price. Drop my price to match the lowest if the drop is under 10 percent, and list the rest for me." → `list_inventory`, `list_release_listings`, `update_listing_price`
- **[Update Discogs orders and tell buyers](https://cotlet.dev/integrations/discogs-api-mcp-server/update-orders-and-message-buyers.md)** (runs: daily): "List my Discogs orders in Payment Received. For each one that has a tracking number in my shipping sheet, set it to Shipped with the tracking number and a short message to the buyer. Tell me about orders older than 3 days without one." → `list_orders`, `get_order`, `update_order_status`, `send_order_message`
- **[Find wantlist records for sale](https://cotlet.dev/integrations/discogs-api-mcp-server/find-wantlist-records-for-sale.md)** (runs: weekly): "Go through my Discogs wantlist. For each release, list the copies for sale at or below 25 in Very Good Plus or better. Show me the five best deals and add nothing to any cart." → `list_wantlist`, `list_release_listings`, `get_release`
- **Catalogue records into a collection**: "Here are 30 records from my shelf with artist, title and catalog number. Find each release on Discogs, add it to my Discogs collection, and tell me which ones had more than one match so I can pick." → `search_releases`, `get_release`, `add_to_collection`
- **Check unanswered buyer messages** (runs: daily): "List my open Discogs orders and show me every buyer message I have not answered yet. Draft a reply to each and send nothing until I say so." → `list_orders`, `get_order`, `send_order_message`

## Can Discogs automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Discogs connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to reprice discogs listings, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/discogs/inventories. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/discogs/inventories with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 13 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Discogs.

### search_releases

Search the Discogs database by artist, title, catalog number or barcode. Access: read. REST: `GET /api/v1/discogs/releases/search`. MCP: `discogs_read → search_releases`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Free text, for example an artist and a title. |
| `catalog_number` | string | no | Catalog number as printed on the record. |
| `barcode` | string | no | Barcode from the sleeve. |
| `page` | integer | no | Page number, starting at 1. |

Returns matching releases with ID, title, year, format and label, Pass the ID to get_release. A catalog number or barcode narrows the result to the exact pressing, which a title search cannot do.

Example response:

```json
{
  "results": [
    {
      "release_id": 4417820,
      "title": "The Sample Quartet - Night Drive / Blue Room",
      "year": 1998,
      "format": "12\", 33 RPM",
      "label": "Example Records"
    }
  ],
  "page": 1,
  "pages": 1
}
```

### get_release

Read one release: tracklist, formats, labels, and how many copies are for sale. Access: read. REST: `GET /api/v1/discogs/releases/{release_id}`. MCP: `discogs_read → get_release`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `release_id` | integer | yes | Release ID from search_releases. The number in discogs.com/release/{id}. |

Returns the tracklist, formats, label and catalog number, plus the number of copies for sale and the lowest price. Use it to confirm the pressing before you add it to a collection or wantlist.

Example response:

```json
{
  "release_id": 4417820,
  "title": "Night Drive / Blue Room",
  "artist": "The Sample Quartet",
  "year": 1998,
  "labels": [
    {
      "name": "Example Records",
      "catalog_number": "EX-001"
    }
  ],
  "tracklist": [
    {
      "position": "A",
      "title": "Night Drive"
    },
    {
      "position": "B",
      "title": "Blue Room"
    }
  ],
  "num_for_sale": 6,
  "lowest_price": 12
}
```

### list_release_listings

List the copies of one release that sellers have for sale now. Access: read. REST: `GET /api/v1/discogs/release-listings`. MCP: `discogs_read → list_release_listings`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `release_id` | integer | yes | Release ID from search_releases. The number in discogs.com/release/{id}. |
| `max_price` | number | no | Only copies at or below this price. |
| `min_condition` | string | no | Lowest media condition to include, as Discogs names it, for example Very Good Plus (VG+). |
| `page` | integer | no | Page number, starting at 1. |

Returns each copy with seller, media and sleeve condition and price, as the release page shows it. The official API gives only the number for sale and the lowest price, so this is the one read that has no API route. It does not buy anything.

Example response:

```json
{
  "release_id": 4417820,
  "listings": [
    {
      "listing_id": 2290011,
      "seller": "vinylbarn",
      "media_condition": "Very Good Plus (VG+)",
      "sleeve_condition": "Very Good (VG)",
      "price": 14,
      "currency": "USD"
    },
    {
      "listing_id": 2290456,
      "seller": "deepcrates",
      "media_condition": "Near Mint (NM or M-)",
      "sleeve_condition": "Near Mint (NM or M-)",
      "price": 21.5,
      "currency": "USD"
    }
  ],
  "page": 1,
  "pages": 1
}
```

### list_inventory

List your own marketplace listings with price, status and release. Access: read. REST: `GET /api/v1/discogs/inventories`. MCP: `discogs_read → list_inventory`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | Listing status as Discogs names it, for example For Sale. |
| `page` | integer | no | Page number, starting at 1. |

Returns your listings with listing ID, release, condition, price and status. Pass a listing ID to update_listing_price. Needs a seller account with listings.

Example response:

```json
{
  "listings": [
    {
      "listing_id": 1829374650,
      "release_id": 4417820,
      "title": "Night Drive / Blue Room",
      "media_condition": "Very Good Plus (VG+)",
      "price": 22,
      "currency": "USD",
      "status": "For Sale"
    }
  ],
  "page": 1,
  "pages": 1
}
```

### list_orders

List the orders you sold, filtered by status. Access: read. REST: `GET /api/v1/discogs/orders`. MCP: `discogs_read → list_orders`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | Order status as Discogs names it, for example Payment Received, In Progress or Shipped. |
| `page` | integer | no | Page number, starting at 1. |

Returns your orders with order ID, buyer name, status, item count and date. Pass an order ID to get_order. Only seller accounts have orders.

Example response:

```json
{
  "orders": [
    {
      "order_id": "1234567-89",
      "status": "Payment Received",
      "buyer": "sample_buyer",
      "items": 2,
      "created": "2026-10-14T09:12:00Z"
    }
  ],
  "page": 1,
  "pages": 1
}
```

### get_order

Read one order: items, status, shipping and the message thread with the buyer. Access: read. REST: `GET /api/v1/discogs/orders/{order_id}`. MCP: `discogs_read → get_order`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | string | yes | Order ID from list_orders, e.g. '1234567-89'. |

Returns the items, current status, shipping details and the buyer messages in order. Use it before changing a status, because a status cannot move back to an earlier one.

Example response:

```json
{
  "order_id": "1234567-89",
  "status": "Payment Received",
  "items": [
    {
      "release_id": 4417820,
      "title": "Night Drive / Blue Room"
    }
  ],
  "messages": [
    {
      "from": "sample_buyer",
      "text": "Can you ship this week?",
      "at": "2026-10-14T10:02:00Z"
    }
  ]
}
```

### list_collection

List the releases in your Discogs collection, with folder. Access: read. REST: `GET /api/v1/discogs/collections`. MCP: `discogs_read → list_collection`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `folder` | string | no | Folder name. Leave out for all folders. |
| `page` | integer | no | Page number, starting at 1. |

Returns collection items with release, folder and the date added. Use it to check whether a release is already in your collection before you add it.

Example response:

```json
{
  "items": [
    {
      "release_id": 4417820,
      "title": "Night Drive / Blue Room",
      "folder": "Uncategorized",
      "added": "2026-09-02"
    }
  ],
  "page": 1,
  "pages": 1
}
```

### list_wantlist

List the releases on your Discogs wantlist. Access: read. REST: `GET /api/v1/discogs/wantlists`. MCP: `discogs_read → list_wantlist`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `page` | integer | no | Page number, starting at 1. |

Returns the releases you want, with release ID, title and the date added. Pair it with list_release_listings to see what is for sale now.

Example response:

```json
{
  "wants": [
    {
      "release_id": 4417820,
      "title": "Night Drive / Blue Room",
      "added": "2026-08-11"
    }
  ],
  "page": 1,
  "pages": 1
}
```

### add_to_collection

Add a release to a folder of your collection. Access: write. REST: `POST /api/v1/discogs/releases/{release_id}/collections`. MCP: `discogs_write → add_to_collection`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `release_id` | integer | yes | Release ID from search_releases. The number in discogs.com/release/{id}. |
| `folder` | string | no | Folder name. Leave out for the default folder. |

Adds the release to your collection and returns the new item. It reaches no one and you can remove the item again, so it asks for no confirmation. A collection item is added from a release, not from a master page.

Example response:

```json
{
  "release_id": 4417820,
  "folder": "Uncategorized",
  "added": true
}
```

### add_to_wantlist

Add a release to your Discogs wantlist. Access: write. REST: `POST /api/v1/discogs/releases/{release_id}/wantlists`. MCP: `discogs_write → add_to_wantlist`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `release_id` | integer | yes | Release ID from search_releases. The number in discogs.com/release/{id}. |
| `notes` | string | no | Your own note on the wantlist item. |

Adds the release to your wantlist and returns the item. It reaches no one and you can remove it again, so it asks for no confirmation.

Example response:

```json
{
  "release_id": 4417820,
  "added": true
}
```

### update_listing_price

Change the price of one of your marketplace listings. Access: write, asks the user first. REST: `PATCH /api/v1/discogs/listings/{listing_id}/price`. MCP: `discogs_write → update_listing_price`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `listing_id` | integer | yes | Listing ID from list_inventory. |
| `price` | number | yes | New price in the currency of your listing. |

Sets the new price and returns the old and the new one. Buyers see the new price at once, so the call changes what people pay. Other fields of the listing stay as they were. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "listing_id": 1829374650,
  "previous_price": 22,
  "price": 18.5,
  "currency": "USD",
  "status": "For Sale"
}
```

### update_order_status

Move one of your orders to the next status and tell the buyer. Access: write, asks the user first. REST: `PATCH /api/v1/discogs/orders/{order_id}/status`. MCP: `discogs_write → update_order_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | string | yes | Order ID from list_orders, e.g. '1234567-89'. |
| `status` | string | yes | In Progress or Shipped. A status cannot go back. |
| `tracking_number` | string | no | Tracking number, for Shipped. |
| `message` | string | no | Message shown to the buyer with the change. |

Changes the order status, adds the tracking number and sends the message with it. Only the seller can change a status, and Discogs allows it for 90 days. The buyer is notified. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "order_id": "1234567-89",
  "previous_status": "Payment Received",
  "status": "Shipped",
  "tracking_number": "RB123456789GB",
  "message_sent": true
}
```

### send_order_message

Send a message to the buyer on an order. Access: write, asks the user first. REST: `POST /api/v1/discogs/orders/{order_id}/message`. MCP: `discogs_write → send_order_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | string | yes | Order ID from list_orders, e.g. '1234567-89'. |
| `text` | string | yes | Message text. |

Posts the message on the order page, where both you and the buyer see it, and returns the thread length. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "order_id": "1234567-89",
  "sent": true,
  "messages_in_thread": 2
}
```

## How do I connect Discogs to Claude Code, Codex or Cursor?

Connecting Discogs takes three steps: sign up, sign in to Discogs once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Discogs to your agent.

1. **Create an account** Sign up and add Discogs in the console. Your API key is there too.

2. **Sign in to Discogs in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Discogs there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   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"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Discogs tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
List my Discogs inventory. For every listing that is for sale and has been listed more than 90 days, check how many other copies of the release are for sale and the lowest price. Drop my price to match the lowest if the drop is under 10 percent, and list the rest for me.
```

### Call Discogs from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/discogs with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X PATCH https://cotlet.dev/api/v1/discogs/listings/1829374650/price \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"price":18.5}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "listing_id": 1829374650,
  "previous_price": 22,
  "price": 18.5,
  "currency": "USD",
  "status": "For Sale"
}
```

## Why use Cotlet for Discogs?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Discogs yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Discogs changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Discogs to Cotlet?

Yes. You sign in to Discogs yourself, in your own Cloud Browser, and we never save your password. Your agents only get Discogs once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**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 this an official Discogs integration?**

No, Cotlet is independent of Discogs. Discogs's own API is too limited for this work. Cotlet works through your own Discogs account, the way you use Discogs in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Discogs in your console: your agents lose access at once and you stay signed in. Signing out of Discogs in the browser works too, and Reset browser deletes the whole profile.

## Is there a Discogs MCP server on GitHub?

Yes. Community Discogs MCP servers exist on GitHub, usually maintained by one person. You install one yourself, create a token or OAuth app, and fix it when something changes. Cotlet hosts the same kind of server for you, signs in as you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, create a personal access token or OAuth app in Discogs, store it, add the server to each MCP client | Sign up, sign in to Discogs once, add one MCP server or API key |
| When Discogs changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Discogs session | A token in a file or environment variable on your computer, readable by any program you run | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | Tools fail until you create or renew the token | Your Cloud Browser keeps you signed in; if Discogs logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself, and throttle it to the 60 requests per minute | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Discogs changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Discogs API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Discogs API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| 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. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Discogs account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Discogs yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Discogs only after you enable it. When Discogs signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Discogs, sign out of Discogs in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Discogs's terms:** You use your own Discogs account and stay responsible for following Discogs's terms. Cotlet is independent and not affiliated with Discogs. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Discogs in the console and press Request access. Then you create your API key and connect Discogs there.

**Do I need to be technical?**

No. You sign in to Discogs once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Discogs to Cotlet?**

Yes. You sign in to Discogs yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Discogs once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Discogs sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Discogs cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Discogs's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Discogs sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Discogs login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Discogs offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**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.

**Can my agent post or send messages in Discogs without asking me?**

No. Every call to update_listing_price, update_order_status or send_order_message waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_to_collection, add_to_wantlist runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Discogs API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/discogs from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.