Information
- OpenAPI version:
3.1.0
Overview
Retro Game Gather REST API 2.2.0
Section titled “Retro Game Gather REST API 2.2.0”Same tools as the RGG MCP server, called with an API key. Schemas are based on the PREMIUM plan; lower-plan differences are in x-rgg-plan-differences.
- Responses are the tool result JSON itself; there is no MCP envelope.
- externalLinks / supportGenre / ASIN are omitted even when requested in fields. Allowed raw external ids are returned instead.
- igdbSlug builds the IGDB page URL (https://www.igdb.com/games/{igdbSlug}). igdbCoverId is an IGDB image id (https://images.igdb.com/igdb/image/upload/t_cover_big/{igdbCoverId}.jpg). IGDB’s own terms apply to its pages and images.
- Reads accept GET query or POST JSON; writes and delete confirmations use POST JSON. GET arrays are comma-separated and query values must be percent-encoded, so Japanese titles and labels are easier to send as POST JSON.
- Deletes are two-step: call once without confirmToken to get the preview, then call again with the same arguments plus confirmToken.
- For physical copies, reuse a successful write’s revision on the next add, or on an update that accepts revision. removePhysicalCopy does not take revision; start a preview so the server can bind the current revision into confirmToken.
- limit above the tool maximum is reduced, and the response reports effectiveLimit / limitReduced / limitReason.
Authentication
Section titled “ Authentication ”apiKey
Section titled “apiKey”API key issued in RGG settings (Authorization: Bearer
Security scheme type: http