Bielacki Igdb MCP Server

What bielacki-igdb-mcp-server MCP server does

The bielacki-igdb-mcp-server MCP server provides MCP access to the Internet Game Database (IGDB) API. It is intended for agents that need to find games, inspect records, compare titles, or run more specialized queries against IGDB data.

The server can retrieve common game information such as titles, descriptions, ratings, release dates, platforms, developers, publishers, genres, themes, game modes, hype values, cover art, and other media. The exact fields returned depend on the request and the fields selected for the tool call.

It also exposes two MCP resources. igdb://endpoints describes available IGDB API endpoints, while igdb://query-syntax provides a reference for the Apicalypse query language. Three pre-built prompts support formatted game searches, comprehensive game details, and lists of anticipated upcoming games.

How it works

The bielacki-igdb-mcp-server MCP server authenticates with IGDB using a Twitch application client ID and client secret. OAuth tokens are cached to reduce repeated authentication work, and the server handles token refresh when required.

Agents can use the higher-level tools for common operations or call custom_query when they need query behavior beyond the built-in searches. IGDB requests are made through the API, so field selection and Apicalypse syntax affect the returned data. The server is built with FastMCP and uses Pydantic for data validation.

IGDB permits four requests per second. The server does not implement its own rate limiter, so clients should avoid rapid repeated calls, request expanded fields instead of making unnecessary follow-up calls, and consider multi-query techniques for batch operations where appropriate.

Setup and configuration

Create a Twitch account if necessary, register an application in the Twitch Developer Console, and obtain an IGDB client ID and client secret. The required environment variables are IGDB_CLIENT_ID and IGDB_CLIENT_SECRET.

Installation is documented through either Smithery or uvx. Smithery installation uses the Smithery CLI. For a direct MCP client configuration, run the package from the Git repository with uvx:

{
  "mcpServers": {
    "igdb-mcp": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/bielacki/igdb-mcp-server.git", "igdb-mcp-server"],
      "env": {
        "IGDB_CLIENT_ID": "your_client_id",
        "IGDB_CLIENT_SECRET": "your_secret"
      }
    }
  }
}

The README specifies Python 3.12 or newer and uses uv as the package manager. Authentication failures usually indicate missing or incorrect credentials; an expired token is refreshed by the server.

Tools and capabilities

Available MCP tools include:

• search_games: searches for games by name, with optional field selection and a result limit from 1 to 500.
• get_game_details: retrieves extensive information for a specified IGDB game ID, with optional field selection.
• get_most_anticipated_games: returns upcoming games ordered by hype-related criteria, with configurable fields, result limit, and minimum hype count.
• custom_query: sends an Apicalypse query to a specified IGDB endpoint.

The server is suitable for prompts such as finding games by a title, listing games from a developer, checking platform availability, discovering upcoming releases, or filtering games by rating. Results may contain null fields because not every IGDB record has complete information.

Limitations and notes

This server depends on valid IGDB access credentials and the availability of the IGDB API. Query spelling and syntax affect results: broadening a search may help when no records are returned, and Apicalypse queries must use valid syntax, including required semicolons where applicable.

The server does not add rate limiting beyond the underlying service's documented allowance. Clients should handle empty or partially populated fields and avoid sending rapid repeated requests. The project is released under the MIT License.