IGDB MCP Server
Related Servers
Alternatives to IGDB MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and retrieve video game information from the IGDB catalog, including games, platforms, companies, release dates, ratings, and cover art.18 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides direct access to the RAWG gaming database, allowing users to search for games, retrieve detailed metadata, and explore genres within Claude. It streamlines game research by offering information on ratings, platforms, and release dates through natural language queries.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables users to search and retrieve board game data via the Board Game Atlas API, including game details, ratings, and availability.8 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search a video game database by name, genre, or platform, retrieve detailed game records, and list genres/platforms with game counts. It exposes these capabilities as MCP tools for ratings, Metacritic scores, release dates, developers, publishers, ESRB ratings, and playtime.19 npmMIT
- AlicenseAqualityCmaintenanceProvides comprehensive video game metadata and assets from Steam, SteamGridDB, and ScreenScraper, enabling game search, details, DLCs, reviews, player counts, and visual assets.1618 npm3MIT
- AlicenseNot gradedqualityBmaintenanceWraps TheGamesDB API to enable game data queries via MCP. Part of Pipeworx gateway connecting AI agents to live data sources.31 npmMIT
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.