igdb

This MCP server provides access to the IGDB API through the Model Context Protocol, enabling you to perform searches, retrieve detailed game information, and run advanced Apicalypse queries with caching and token management. The server exposes pre-built tools like search_games, get_game_details, most_anticipated, and custom_query, which you can invoke from your MCP client configuration. Use the included environment variables (IGDB_CLIENT_ID and IGDB_CLIENT_SECRET) to authenticate with IGDB once you configure your client.

To use the server, connect via MCP using the igdb-mcp entry name (as configured in the mcp_config). You can start with common prompts such as searching for titles, fetching detailed data for a specific game, or listing upcoming releases. The Prompts and Tools sections in the README outline example prompts and the expected fields for each tool. The server also supports advanced queries using the Apicalypse syntax, allowing complex filters and field selections in a single request.

Prerequisites:

• Python 3.12 or newer (the IGDB MCP Server is compatible with Python-based environments)
• uv (uvx) installed as your MCP runtime tool
• Git access for cloning or installing from Git sources

Installation steps:

1. Install the uv tool if you don’t have it yet:
   • Follow instructions at the uv project page: https://github.com/astral-sh/uv
2. Install the IGDB MCP Server via uvx from GitHub:
   • uvx --from git+https://github.com/bielacki/igdb-mcp-server.git igdb-mcp-server
3. Configure your MCP client to point to the server using the provided mcp_config example (include IGDB_CLIENT_ID and IGDB_CLIENT_SECRET in the environment).
4. Start the MCP client and verify that the igdb-mcp server is reachable via the configured mcpServers entry.

If you prefer alternative installation paths, you can also install via Smithery (as shown in the README) or adjust the configuration to use the npx-based workflow if you later convert to a Node-based wrapper.

Tips and common considerations:

• Ensure you have valid IGDB credentials (Client ID and Client Secret) and set them in your MCP client environment variables to authenticate with IGDB.
• The server caches OAuth tokens to minimize authentication overhead; however, ensure token refresh is enabled and your secrets are kept secure.
• IGDB rate limits are not enforced by the server; design your prompts to minimize excessive requests (e.g., prefer field expansion and batch queries when supported).
• If you encounter authentication errors, double-check that IGDB_CLIENT_ID and IGDB_CLIENT_SECRET are correctly configured in your MCP client config.
• The Apicalypse query tool (custom_query) allows advanced, endpoint-based queries; refer to the IGDB Apicalypse syntax for building complex requests.
• The README provides example prompts and the core tools; you can extend the MCP client usage by composing multi-field queries and handling null fields gracefully in your application.