home / mcp / igdb mcp server

IGDB MCP Server

MCP server providing seamless access to the IGDB (Internet Game Database) API for AI assistants. Search games, get detailed information, find trending titles, and execute custom queries through the Model Context Protocol.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "bielacki-igdb-mcp-server": {
      "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"
      }
    }
  }
}

You can access the IGDB data through the MCP protocol by running a dedicated IGDB MCP Server. This lets you search games, fetch detailed information, and explore trends using simple prompts, while benefiting from smart caching and type-safe data handling.

How to use

Install and run the IGDB MCP Server locally, then connect your MCP client to it. Use the pre-built prompts to search for games, view details, and discover trending titles. You can also perform advanced queries to filter by hype, rating, or developer. Your MCP client will send requests to the IGDB MCP Server and receive structured responses that include game metadata, release dates, platforms, and media.

How to install

Prerequisites you need on your machine include Node.js (for the Smithery installation path) and an MCP client that can consume MCP servers.

Option A: install via Smithery

npx -y @smithery/cli install @bielacki/igdb-mcp-server

Option B: install with uvx

If you prefer running a local MCP server with uvx, add this to your MCP client configuration.

{
  "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"
      }
    }
  }
}

Configuration and credentials

Set up your IGDB credentials in the environment so the server can authenticate to IGDB. You will need a Client ID and Client Secret from your IGDB/Twitch developer account.

Example credentials to place in your MCP client config or environment: IGDB_CLIENT_ID and IGDB_CLIENT_SECRET.

Security and access

Protect your IGDB credentials. Do not commit them to public repositories. Use per-project environment files or secret management in your deployment.

Notes on usage

The IGDB MCP Server supports full IGDB API access, fast searches, Apicalypse queries, and pre-built prompts. You can query for game details, compare platforms, and retrieve media assets. Ensure your MCP client handles API responses gracefully, as some fields may be null in IGDB data.

Troubleshooting

Authentication errors usually indicate missing or incorrect client credentials. If a token expires, the server will refresh automatically. Rate limiting from IGDB is 4 requests per second; to avoid throttling, combine requests when possible or use multi-query for batch operations.

Available tools

search_games

Search for games by name and return basic information or specified fields.

get_game_details

Fetch comprehensive information for a specific IGDB game by its ID, including ratings, platforms, and media.

get_most_anticipated_games

Find upcoming games by hype with optional field selections and limits.

custom_query

Execute Apicalypse queries against the IGDB endpoints to perform advanced searches.