Gamedb Port

io.github.CloudCorpRecords由 GitHub 账号 CloudCorpRecords 发布v0.1.0更新于 Nov 3, 2026

IGDB游戏数据库：搜索游戏、游戏详情、预期发行作品以及自定义查询。

AI 翻译由 AI 模型根据下方的原文描述翻译，可能有误。

原文描述

IGDB game database: search games, game details, anticipated releases, and custom queries.

发布方自己的服务：Port

已验证STDIO仅桌面数据库

服务详情

标识符: io.github.CloudCorpRecords/gamedb-port
传输: STDIO
运行时: Desktop only
信任: Verified
发布于: Nov 3, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此条目所属的 GitHub 账号 CloudCorpRecords。这并不表明该账号就是产品方。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.CloudCorpRecords%2Fgamedb-port.svg)](https://sourceweft.com/mcp/io.github.CloudCorpRecords%2Fgamedb-port?utm_source=readme&utm_medium=badge)

概览

Gamedb Port 的本地 MCP 服务；无需登录；STDIO。

暂无 AI 概览：以下信息来自注册中心条目和服务本身。

安装

在 SourceWeft 中

打开控制台中的 Gamedb Port，将其添加到工作区。
为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照仓库中的启动说明。

README

gamedb-port

gamedb-port queries the IGDB video-game database: search games by name, pull the full record for one game, list the most anticipated upcoming releases ranked by hype, or send a raw Apicalypse query to any IGDB endpoint. One binary serves a command-line interface and a stdio MCP server.

Access uses the documented IGDB contract. IGDB is authenticated through Twitch OAuth: set IGDB_CLIENT_ID and IGDB_CLIENT_SECRET to your Twitch application credentials. The tool exchanges them for a client-credentials access token, caches it in-process, and sends it with a Client-ID header on every call. If either variable is missing, commands fail before any request is made.

Install

Or run the container image:

bash

docker run -i -e IGDB_CLIENT_ID=... -e IGDB_CLIENT_SECRET=... ghcr.io/cloudcorprecords/gamedb-port

docker run -i -e IGDB_CLIENT_ID=... -e IGDB_CLIENT_SECRET=... ghcr.io/cloudcorprecords/gamedb-port

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

bash

gamedb-port search zelda --limit 5gamedb-port search "final fantasy" --fields name,rating --limit 20gamedb-port details 1942gamedb-port details 1942 --fields name,summary,genres.namegamedb-port anticipatedgamedb-port anticipated --limit 10 --min-hypes 50gamedb-port query genres "fields name,slug; limit 5;"
gamedb-port --version

gamedb-port search zelda --limit 5gamedb-port search "final fantasy" --fields name,rating --limit 20gamedb-port details 1942gamedb-port details 1942 --fields name,summary,genres.namegamedb-port anticipatedgamedb-port anticipated --limit 10 --min-hypes 50gamedb-port query genres "fields name,slug; limit 5;"
gamedb-port --version

Commands print the upstream JSON payload. Exit codes: 0 on success, 1 when a call fails (missing credentials, an upstream API error, or invalid argument values), 2 for usage errors.

When no --fields is given, queries request a default field set: name,cover.url,first_release_date,genres.name,platforms.name,rating,summary.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

MCP client configuration:

json

{  "mcpServers": {    "gamedb-port": {      "command": "npx",      "args": ["-y", "@reneturcios/gamedb-port", "mcp"],      "env": {        "IGDB_CLIENT_ID": "your-twitch-client-id",        "IGDB_CLIENT_SECRET": "your-twitch-client-secret"      }    }  }}

{  "mcpServers": {    "gamedb-port": {      "command": "npx",      "args": ["-y", "@reneturcios/gamedb-port", "mcp"],      "env": {        "IGDB_CLIENT_ID": "your-twitch-client-id",        "IGDB_CLIENT_SECRET": "your-twitch-client-secret"      }    }  }}

Tools

Tool	Input	What it returns
`search_games`	`query` (required), `fields`, `limit` (1–500, default 10)	Games matching the name search.
`get_game_details`	`game_id` (required), `fields`	The full IGDB record for one game.
`get_most_anticipated_games`	`fields`, `limit` (1–500, default 25), `min_hypes` (default 25)	Upcoming games with a future release date, sorted by hype descending.
`custom_query`	`endpoint`, `query` (both required)	Whatever the caller's Apicalypse query returns from that endpoint.

The three shaped tools build their Apicalypse bodies for you: search_games becomes search "<query>"; fields ...; limit ...;, get_game_details becomes fields ...; where id = <game_id>;, and get_most_anticipated_games filters first_release_date > now & hypes >= <min_hypes> and sorts by hypes desc. custom_query sends its query body verbatim to https://api.igdb.com/v4/<endpoint>.

Development

bash

npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no network (fake fetch fixtures)npm run dev     # run the CLI from source via tsx

npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no network (fake fetch fixtures)npm run dev     # run the CLI from source via tsx