Access the IGDB (Internet Game Database) API through Model Context Protocol (MCP)
Access the IGDB (Internet Game Database) API through Model Context Protocol (MCP). Exposed over MCP by the igdb mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
The IGDB MCP Server provides seamless access to the Internet Game Database (IGDB) through the Model Context Protocol. IGDB is a comprehensive database containing information about video games, including:
Everything the assistant can do here goes through one of these:
search_games — Search for games by nameget_game_details — Get comprehensive game informationget_most_anticipated_games — Find upcoming games by hypecustom_query — Execute Apicalypse queriesTools — The Tools tool exposed by this serverResources — The Resources tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 2 environment variables: IGDB_CLIENT_ID, IGDB_CLIENT_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. IGDB's toolset — search_games, get_game_details, get_most_anticipated_games and 3 more — is a fair guide to whether it matches your workflow.
This entry was verified against IGDB's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| search_games | Search for games by name |
| get_game_details | Get comprehensive game information |
| get_most_anticipated_games | Find upcoming games by hype |
| custom_query | Execute Apicalypse queries |
| Tools | The Tools tool exposed by this server. |
| Resources | The Resources tool exposed by this server. |
{
"mcpServers": {
"github-com-bielacki-igdb": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"IGDB_CLIENT_ID": "your-value",
"IGDB_CLIENT_SECRET": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| IGDB_CLIENT_ID | Configuration value read at startup. | Optional |
| IGDB_CLIENT_SECRET | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.