Skip to main content
Glama
README.md
# Discogs MCP server for ChatGPT and Claude

Discogs has an API covering its database, collections, wantlists, marketplace inventory and orders. The source page reports no official MCP server, checked 17 October 2026.
Cotlet.dev connects ChatGPT, Claude and other AI agents to your own signed-in Discogs account.

Source: [Discogs integration page](https://cotlet.dev/integrations/discogs-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=discogs).

## What can your agent do?

The live page describes 13 hosted business tools: 8 reads and 5 writes.
MCP routes reads through `discogs_read` and writes through `discogs_write`.

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

Three writes ask for confirmation by default: changing a listing price, updating an order status and sending an order message. Approvals can be configured per tool.
Adding a release to a collection or wantlist runs without asking first.
Seller tools need a seller account with inventory or orders. Collection, wantlist and release tools work on any account.
Order status changes notify the buyer and cannot move back to an earlier status. Only the seller can change an order status, within the 90-day window described on the source page.

## Example requests

> List my marketplace inventory and prices.

> Find copies of records on my wantlist under $25 in VG+ condition.

> Show my sold orders and their current status.

> Show my collection before adding this release.

## Connect ChatGPT and Claude

1. [Get access to Discogs](https://cotlet.dev/signup?app=discogs).
2. Sign in to your own Discogs account in the Cotlet.dev Cloud Browser and enable Discogs for agents.
3. In ChatGPT, use Settings > Apps & Connectors > Create with `https://cotlet.dev/mcp/v1/connect` and OAuth.
4. In Claude, use Settings > Connectors > Add custom connector with the same URL.

## Connect Codex and Claude Code

Create an API key in the Cotlet.dev console and set `COTLET_API_KEY` in your environment.

Codex:

```toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

Claude Code:

```bash
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"
```

## Optional local MCP wrapper

Python 3.10+, standard library only. This repository provides seven generic browser helpers over Cotlet.dev: `discogs_guide`, `discogs_status`, `discogs_open`, `discogs_read`, `discogs_click`, `discogs_type`, `discogs_close`.
These local helpers are separate from the hosted business tools and routes above. Listing helpers needs no key; calling them requires `COTLET_API_KEY`.

```bash
export COTLET_API_KEY="your-key"
python3 discogs_agent.py serve
```

For a local MCP client:

```json
{"mcpServers":{"discogs":{"command":"python3","args":["/absolute/path/to/discogs_agent.py","serve"],"env":{"COTLET_API_KEY":"your-key"}}}}
```

Other commands: `connect`, `status`, `guide`, `read`, `tools`.
The read command opens the browser, reads the page and closes the browser session.

## Access and independence

Use your own Discogs account. You complete sign-in and any verification yourself.
Disable Discogs for agents, reset the browser or delete the API key to revoke access.
Cotlet.dev is independent and is not affiliated with, endorsed by or sponsored by Discogs.

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation4/5

The core browser primitives (open, read, click, type, close) are clearly distinct and map to different actions. The only mild overlap is between discogs_guide and discogs_status, since both are setup-oriented tools, but their purposes remain distinguishable.

Naming Consistency5/5

All tools use the same discogs_ prefix followed by a short lowercase snake_case action or label. The naming is highly predictable and internally consistent.

Tool Count5/5

Seven tools is well-scoped for a browser-driven Discogs automation server. Each tool has a clear role in the session lifecycle or interaction model.

Completeness4/5

The set covers the essential browser lifecycle: guidance, status, open, inspect, click, type, and close. Minor gaps exist for common browser actions like scrolling, going back, selecting dropdowns, or waiting, but most Discogs workflows can likely be handled through the provided primitives.