Ext Ops Panel
Open dashboard
Comparison

Gameye vs Igdb

Gameye is an MCP server published by Gameye. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Igdb is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-06. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceGameyeIgdb
Official MCP Registry Listed
Version: 0.4.0
Downloads/month (npm): 1 498
Downloads/week (npm): 140
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.1
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
npm registry (MCP servers) Listed
Version: 0.4.0
Downloads/month (npm): 1 498
Downloads/week (npm): 140
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Gameye vs Igdb
FactGameyeIgdb
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)2026-10-25 (worse)2026-11-02 (better)
Where it runs (differs)On your machine (gameye-mcp)Remote server (gateway.pipeworx.io/igdb/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/gameye/gameye-mcpgithub.com/pipeworx-io/mcp-igdb
Changes in the last 7 days11
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 16 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Gameye

In its own words, on Official MCP Registry:

Launch, inspect and stop multiplayer game server sessions on Gameye from any MCP client.

Igdb

In its own words, on Official MCP Registry:

IGDB — the Internet Game Database (Twitch/Amazon), the reference catalogue for video games.

How to run each

Gameye As a local MCP server: npm package

Claude Code
claude mcp add --env "GAMEYE_API_TOKEN=<YOUR_GAMEYE_API_TOKEN>" --transport stdio gameye-mcp -- npx -y gameye-mcp

Requires: GAMEYE_API_TOKEN (secret)

Igdb As a remote MCP server

Claude Code
claude mcp add --transport http igdb https://gateway.pipeworx.io/igdb/mcp

Requires: PIPEWORX_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Igdb has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only Gameye asks for

  • GAMEYE_API_TOKEN (secret)
  • GAMEYE_ENV

Only Igdb asks for

  • PIPEWORX_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Gameye · What it can do: Igdb · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built