CommunitySlow· 2mo★ 4.3by kkjdaniel

BGG MCP

Queries the BoardGameGeek XML API 2 for games, collections, and statistics via Docker or Go binary.

View repo

Safety & Trust

Delv Safety Grade: C

Score 58/100 · assessed 2026-04-28

Maintainer45

Permissions85

Supply chain40

Transparency65

Incidents100

This MCP server wraps the BoardGameGeek XML API for querying board game data and user collections. The maintainer appears to be a solo developer (kkjdaniel) with limited visible track record. Distribution is via Docker Hub and Go binary, not standard package registries, which reduces supply chain verification. The server requires BGG_API_KEY and BGG_USERNAME environment variables, though BGG's API documentation suggests most endpoints work without authentication, raising questions about credential necessity. Permissions are appropriately scoped to read-only API queries with outbound network access only. The repository is open source with basic documentation, but lacks comprehensive security practices like dependency pinning or signed releases. No known security incidents exist. The narrow use case (board game lookups) limits blast radius, but the non-standard distribution and solo maintenance present moderate supply chain risks.

Lethal Trifecta (prompt-injection exposure)

TWO OF THREE

Private dataNo

Reads secrets, credentials, private files

Untrusted inputYes

Ingests web pages, PRs, issues, emails

External commsYes

Can send data outbound

Reviews and forum-style comments are user content.

Green flags

Read-only API queries with no write capabilities
Open source repository with visible code
Narrow scope limited to board game data lookups
No known security incidents or malicious activity
Docker containerisation provides some isolation

Red flags

Solo maintainer with limited public track record
Docker-only distribution bypasses standard package registry verification
Requires credentials (BGG_API_KEY) when BGG API may not need authentication
No dependency pinning or signed releases visible
Thin documentation on credential handling and security practices

Permissions requested

Outbound networkRead envAccess secrets

Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Install

docker run kdaniel/bgg-mcp

Env vars needed: BGG_API_KEYBGG_USERNAME

Review

BGG MCP wraps the BoardGameGeek XML API 2 so you can query game data, collections, and stats from Claude Desktop or Cursor. It's a Docker container or Go binary that speaks MCP, meaning you can ask Claude to look up a game's weight rating, check what's in your collection, or pull playtime logs without opening a browser tab. I'd reach for this when I'm researching games to buy or tracking what I own. Ask Claude to compare the complexity of three euros, and it fetches the actual BGG weight scores. Ask it to list unplayed games in your collection, and it pulls your username's data. The Docker route is clean: one command, no Go toolchain. The env vars (BGG_API_KEY and BGG_USERNAME) are straightforward, though BGG's API key process is a bit opaque if you've never touched it. The quirks are mostly BGG's fault. The XML API 2 is slow and occasionally flaky. Queries can take a few seconds, and rate limits exist but aren't well documented. The MCP server itself is thin, which is fine, it just passes requests through. If you're expecting rich filtering or local caching, you won't find it here. It's a direct pipe to BGG. Who shouldn't bother: anyone who doesn't already use BoardGameGeek. If your collection lives in Tabletop Simulator or a spreadsheet, this won't help. Also, if you're not comfortable with Docker or editing JSON configs, the setup friction might outweigh the convenience. But if you're a BGG regular who wants to query your collection or research games without context-switching, it's a tidy addition. I've used it to build shortlists of mid-weight games under 90 minutes, and it beats tabbing between Claude and BGG manually. Just don't expect instant responses, the API itself is leisurely.

Verdict

Install this if you're a BoardGameGeek user who wants to query games and collections from Claude without leaving your editor. Skip it if you don't track games on BGG or if you're allergic to Docker and manual config edits. It's a clean pipe to a slow API, useful but not magical.

Good at

Docker install is one command, no Go toolchain required.
Direct access to BGG's game database and your personal collection from Claude.
Useful for research workflows like comparing game weights or filtering unplayed titles.
Env var config is simple and the MCP interface is clean.

Watch out

BGG's XML API 2 is slow, expect multi-second waits per query.
No local caching, every request hits the remote API.
Rate limits exist but aren't clearly documented, easy to hit if you're not careful.
Requires a BGG account and API key, which adds setup friction if you're new to the platform.

Use cases

board game research
collection management
playtime tracking
recommendation lookups

Getting started

1. Run `docker run kdaniel/bgg-mcp` to pull the container, or build the Go binary from the repo if you prefer. 2. Add the server to your Claude Desktop or Cursor MCP config JSON, pointing to the Docker container or binary path, and set `BGG_API_KEY` and `BGG_USERNAME` in the env block. 3. Restart your host and ask Claude to fetch a game by name or list your BGG collection to verify the connection works. 4. Watch out for slow responses, BGG's API can take several seconds per query, and rate limits may kick in if you hammer it. 5. If queries fail, check that your BGG username is public and your API key is valid, BGG's key management UI is easy to miss.

Works with

Claude DesktopClaude CodeCursor