SuperAPI AI Directory

discogs

General & other

View repository

Updated 10-16 07:16

About this skill

Unbrowse for Discogs (discogs.com)

Discogs as tools for your agent. Unofficial: not affiliated with or endorsed by discogs.com. Unbrowse compiled these from discogs.com's own requests: each call replays the site's first-party API server-side and returns a verified result. No scraping of rendered pages, no browser on your side, no discogs.com API key.

Connect the discogs.com MCP

This server is a tool scope holding only discogs.com: its compiled tools plus the Unbrowse tools that run them, so the agent's tool list stays small and every call stays on discogs.com.

claude mcp add --transport http discogs https://unbrowse.ai/mcp/discogs.com
codex mcp add discogs --url https://unbrowse.ai/mcp/discogs.com && codex mcp login discogs
{"mcpServers":{"discogs":{"url":"https://unbrowse.ai/mcp/discogs.com"}}}

The first connect signs in to Unbrowse with OAuth (free tier, only verified results count). For scripts, send Authorization: Bearer $UNBROWSE_API_KEY (key from https://unbrowse.ai/app/keys; keep it in a secret manager, never in config you commit).

If none of the tools below are in this session's tool list, the server is not connected or not signed in: say so and stop. Do not fetch discogs.com some other way and present it as this skill's result.

Tools

discogs_com__get_search — Search discogs

Search discogs. Inputs: query. Returns the page's title, readable text and links. Read-only on discogs.com.

  • query (string, required) — query (typed during “fill Search artists, albums and more...”)
  • type (string) — optional, e.g. "all"
  • select (array) — Keep only these parts of the result: dots walk keys, [] maps over a list, a final {a,b} keeps several keys (e.g. "results[].{title,url}"). Unmatched paths come back in selectMissing.
{"query":"<query>"}

Always there too: unbrowse.run (a task on discogs.com in plain words), unbrowse.inspect, unbrowse.resume, unbrowse.scrape and unbrowse.map (any page on discogs.com), and the recorded cloud browser unbrowse.browse.open → unbrowse.browse.act → unbrowse.browse.finish. Hosts that reject dotted names show them with _ (unbrowse_run).

How to call

  1. Pick the tool whose title matches the job and pass its inputs. Leave the site's recorded parameters out unless the user asked for something they control.
  2. Read status. succeeded carries the verified result. input_required is not a failure: answer the open fields with unbrowse.resume {runId, answers} on the same run.
  3. No tool fits: unbrowse.run {task}. It fails with no_capability when nothing is compiled for that yet: do it once with unbrowse.browse.open on discogs.com → unbrowse.browse.act → unbrowse.browse.finish, which compiles a new tool this server lists next time. Anything off discogs.com is refused here (not_in_scope): use the general Unbrowse server for that.
  4. Signing in: never ask the user for a password. unbrowse.browse.act with action: "autofill" fills discogs.com's login from their Unbrowse password manager.
  5. Report only what a succeeded result says. outcome_unknown means a change may have happened: check before retrying. Posting, buying, sending or deleting needs the user's go-ahead.

Without MCP

Every tool is also a REST call:

curl -s https://unbrowse.ai/api/v1/sites/discogs.com/call/discogs_com__get_search \
  -H "authorization: Bearer $UNBROWSE_API_KEY" -H "content-type: application/json" \
  -d '{"query":"<query>"}'

OpenAPI: https://unbrowse.ai/api/v1/sites/discogs.com/openapi.json. Every other site: the general Unbrowse skill (https://github.com/unbrowse-ai/unbrowse) and https://unbrowse.ai/mcp.