IGDB MCP Server
Related Servers
Alternatives to IGDB MCP Server
No user-submitted related servers found.
Related Servers
- 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.4 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides comprehensive video game metadata and assets from Steam, SteamGridDB, and ScreenScraper, enabling game search, details, DLCs, reviews, player counts, and visual assets.9 npm3MIT
- AlicenseNot gradedqualityCmaintenanceWraps TheGamesDB API to enable game data queries via MCP. Part of Pipeworx gateway connecting AI agents to live data sources.5 npmMIT

aggrometerofficial
AlicenseNot gradedqualityCmaintenanceEnables querying live cross-platform gaming market data — Steam players, Twitch/YouTube viewership, prices, discounts, hype, and the aggro metric — through 8 read-only tools for summaries, rankings, genre rollups, game details, and search.MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to recommend Steam games from natural language by searching games, finding similar titles, filtering by tags and platform, and retrieving detailed game metadata.1MIT
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.