Giantbomb

io.github.pipeworx-ioPublished by GitHub account pipeworx-iov0.1.1Updated Oct 24, 2026

Giant Bomb MCP.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryMedia & Design

Overview

AI-generated overview

Remote MCP endpoint exposing Giant Bomb's video-game catalog so an assistant can search and look up games, characters, companies, platforms and releases.

What you can do
Search across all Giant Bomb resources with one query tool, with optional resource, limit and page controls. Retrieve a single game record or list and filter games with sorting and paging. Look up individual characters. List and filter companies, releases and platforms. On the gateway endpoint, also use shared Pipeworx meta-tools such as ask_pipeworx, discover_tools, search_within and remember/recall.
When to use it
Useful when an assistant needs factual video-game reference data — titles, platforms, release information, companies, characters or reviews — for research, catalog building or answering game questions, without writing Giant Bomb API calls by hand.
Requirements
A remote streamable HTTP endpoint at the Pipeworx gateway; no local runtime needed for that route. A free Giant Bomb API key is required, supplied as the PLATFORM_GIANTBOMB_KEY setting or as an _apiKey query parameter. A local stdio variant is offered via npx for use without a gateway account. Network access to the gateway and the Giant Bomb API.
Before you install
The Giant Bomb API key is a credential; keep it out of shared configs and logs, especially when passed as a query parameter. The gateway endpoint also lists roughly 30 shared Pipeworx meta-tools beyond this pack, which consume context and route questions across the wider catalog. Read-only lookups, but data comes from third parties.

Installation

In SourceWeft

  1. Open Giantbomb in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.pipeworx-io%2Fgiantbomb/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "giantbomb": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/giantbomb/mcp"
    }
  }
}

README

@pipeworx/giantbomb

Giant Bomb MCP — extensive video-game catalog (games, characters, companies, platforms, releases, reviews). Free API key required.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Auth

  • Platform: PLATFORM_GIANTBOMB_KEY. BYO: ?_apiKey=….

Tools

  • search(query, resources?, limit?, page?) — search across all resources
  • game(guid_or_id) — single game record
  • games(filter?, sort?, limit?, offset?) — list/filter games
  • character(guid_or_id) — single character
  • companies(filter?, limit?, offset?) — companies
  • releases(filter?, limit?, offset?) — releases
  • platforms(filter?, limit?, offset?) — platforms

Data source

https://www.giantbomb.com/api/

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

json
{  "mcpServers": {    "giantbomb": {      "url": "https://gateway.pipeworx.io/giantbomb/mcp"    }  }}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/giantbomb/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

json
{  "mcpServers": {    "pipeworx": {      "url": "https://gateway.pipeworx.io/mcp"    }  }}

Both URLs reach the same gateway and the same 1679+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

bash
curl -X POST https://gateway.pipeworx.io/v1/tools/giantbomb_search \  -H 'Content-Type: application/json' \  -d '{"query":"The Legend of Zelda"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/giantbomb_search. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

json
{  "mcpServers": {    "giantbomb": {      "command": "npx",      "args": ["-y", "@pipeworx/mcp-giantbomb"]    }  }}

Or run it directly to confirm it starts:

bash
npx -y @pipeworx/mcp-giantbomb

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Giantbomb data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Source: README.md at commit ecc5987

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v0.1.1LatestSep 25, 2026
  2. v0.1.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts