videogame-encyclopedia

This MCP server provides a comprehensive set of tools to discover and enrich video game data by aggregating Steam metadata with SteamGridDB visual assets and, optionally, retro game data from ScreenScraper. Core capabilities include searching Steam catalogs, retrieving detailed game profiles (descriptions, genres, release dates, developers/publishers, pricing, and platform support), and fetching associated assets such as logos, box art, and hero images. It also exposes functions to obtain DLC lists, reviews summaries, news updates, and real-time player counts, as well as tools to browse top sellers or top games on Steam. The SteamGridDB integration enables access to high-quality visuals and multiple asset variations with metadata, while the ScreenScraper integration (if configured) supports retro gaming data like ROM information and media assets. The recommended entry point is game_get_full_profile, which aggregates metadata and assets into a single, rich response for a complete overview of a game.

Prerequisites:

• Node.js 18 or higher
• npm (or yarn)

Setup steps:

1. Clone or download the repository:

   • git clone https://github.com/<org>/<repository>.git
   • cd videogame-encyclopedia-mcp-server

2. Install dependencies:

   • npm install

3. Configure API keys:

   • Copy the example environment file: cp .env.example .env
   • Edit .env and add your API keys, notably STEAMGRIDDB_API_KEY for visuals: STEAMGRIDDB_API_KEY=your_steamgriddb_api_key_here

   Optional: configure ScreenScraper credentials if using retro data: SCREENSCRAPER_DEV_ID=your_dev_id_here SCREENSCRAPER_DEV_PASSWORD=your_dev_password_here SCREENSCRAPER_USER_ID=your_username_here SCREENSCRAPER_USER_PASSWORD=your_password_here

4. Build the project (produces dist/index.js): npm run build

5. Run the server locally for testing: node dist/index.js

6. (Optional) Integrate with MCP clients (e.g., Claude Desktop) using the provided mcp_config examples.

Environment variables and configuration tips:

• STEAMGRIDDB_API_KEY is required for high-quality assets (logos, grids, banners). Keep it secure and do not expose in public repositories.
• ScreenScraper credentials are optional and only needed if you plan to pull retro game data; ensure you have a valid developer account.
• When deploying to a server or container, ensure the environment variables are set in the deployment configuration (e.g., Docker env, cloud secrets).
• If you encounter issues with asset retrieval, verify API key validity and rate limits from SteamGridDB and ScreenScraper. Check logs for network errors or quota exceeded messages.
• The recommended way to fetch complete data is via game_get_full_profile, which aggregates Steam metadata with SteamGridDB assets.