IGDB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IGDB_CLIENT_ID | Yes | Your IGDB Client ID from Twitch Developer Console | |
| IGDB_CLIENT_SECRET | Yes | Your IGDB Client Secret from Twitch Developer Console |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_gamesB | Search for games in the IGDB database |
| get_game_detailsB | Retrieve detailed information about a specific game from IGDB |
| get_most_anticipated_gamesB | Fetch upcoming games sorted by hype count, filtered for future or TBA releases |
| custom_queryB | Run a custom Apicalypse query against any IGDB API endpoint |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| search_game | Search for a game by name and present top 5 results |
| game_details | Get comprehensive details for a game by name |
| most_anticipated | Find the most anticipated upcoming games based on user hypes on IGDB |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_endpoints | List of available IGDB API endpoints and their descriptions |
| get_query_syntax | Guide to the IGDB Apicalypse query language with examples |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: custom_query is for raw API queries, get_game_details retrieves specific game info, get_most_anticipated_games fetches upcoming games by hype, and search_games performs general searches. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (e.g., custom_query, get_game_details, get_most_anticipated_games, search_games). The naming is uniform and predictable, using snake_case throughout with clear action descriptors.
With only 4 tools, the server feels slightly thin for interacting with a comprehensive database like IGDB. While the tools cover key operations, more specialized functions (e.g., filtering by genre, platform, or date) might be missing, making the count borderline for the domain's scope.
The tools provide basic search and retrieval capabilities but lack full CRUD/lifecycle coverage typical of a database API. There are notable gaps, such as no update or delete operations (though IGDB might be read-only), and limited filtering options beyond hype-based sorting, which could hinder complex agent workflows.