Search, details and anticipated-games cover most questions; `custom_query` plus the two syntax resources is what lets an agent answer things like "RPGs rated above 90" without waiting for a new tool. One caution the README states plainly: IGDB allows four requests per second and this server does not rate-limit, so rapid-fire querying is on you.
A FastMCP server over the IGDB API v4. It handles the Twitch OAuth exchange and caches the token, so you work in games rather than in authentication, and it leaves the full Apicalypse query language available when the shaped tools are not enough.
- Games searched by name, with the fields and result count you ask for, from 1 to 500 — `search_games`
- Full detail on one title by its IGDB id, covering ratings, platforms, developers and DLC — `get_game_details`
- Upcoming games ranked by hype, with a `min_hypes` floor — `get_most_anticipated_games`
- Any IGDB endpoint queried directly in Apicalypse, for filters the shaped tools do not cover — `custom_query`
- Two reference resources for writing those queries: `igdb://endpoints` and `igdb://query-syntax`
- Three ready-made prompts: `search_game`, `game_details`, `most_anticipated`
A Twitch account and an application registered in the Twitch Developer Console, giving you `IGDB_CLIENT_ID` and `IGDB_CLIENT_SECRET`. Python 3.12 or newer, run through uvx straight from the repository, or installed via Smithery. Token refresh is handled for you.
One command plus a key — npx -y @smithery/cli install @bielacki/igdb-mcp-server, then supply credentials