rpggeek-mcp
An MCP (Model Context Protocol) server for querying RPGGeek — the RPG section of the BoardGameGeek network. Connect it to Claude Desktop (or any MCP client) to let an AI assistant look up RPG products by name or ISBN and retrieve detailed product information.
Unofficial community project. Not affiliated with or endorsed by RPGGeek.
Tools
find_candidates
Searches RPGGeek for RPG products matching a name and/or ISBN. Returns up to 5 candidates.
Parameters (at least one required):
| Parameter | Type | Description |
|---|---|---|
name |
string |
Product name to search for |
isbn |
string |
ISBN (any format) |
Strategy: if an ISBN is provided it is tried first; the name is used as a fallback if the ISBN search returns no results.
Returns: a list of up to 5 candidates, each with:
rpggeek_id— RPGGeek's numeric item ID (shared with BoardGameGeek and VideoGameGeek)name— primary product nameyear_published— publication year, ornull
Results are scoped to RPG items only. An empty list means nothing was found. Pass rpggeek_id from a candidate to get_product_details to retrieve full data.
get_product_details
Returns full structured data for a known RPGGeek item.
Parameters:
| Parameter | Type | Description |
|---|---|---|
rpggeek_id |
integer |
RPGGeek's numeric item ID |
Returns:
| Field | Type | Description |
|---|---|---|
rpggeek_id |
integer |
|
name |
string |
Primary product name |
year_published |
integer | null |
|
description |
string | null |
Full product description |
systems |
string[] |
RPG systems (e.g. "Dungeons & Dragons 5E") |
categories |
string[] |
Product categories (e.g. "Core Rulebook", "Adventure/Scenario") |
designers |
string[] |
Designer names |
publishers |
string[] |
Publisher names |
thumbnail_url |
string | null |
Cover thumbnail URL |
rating |
number | null |
Average community rating |
Requirements
- uv must be installed. Python is managed automatically by uv.
- A bearer token for the RPGGeek XML API. Obtain one by logging in to your BGG/RPGGeek account and submitting an application at boardgamegeek.com/applications/create.
Installation
1. Create a .env file in the repo root (or any ancestor directory of where the server is installed):
cp .env.example .env
# then edit .env and set your bearer token
RPGGEEK_BEARER_TOKEN=your_bearer_token_here
2. Run the server — no cloning or venv management required with uvx:
uvx rpggeek-mcp serve
To install permanently as a tool:
uv tool install rpggeek-mcp
rpggeek-mcp serve
Connecting to Claude Desktop
Add the server to your Claude Desktop configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"rpggeek": {
"command": "uvx",
"args": ["rpggeek-mcp", "serve"],
"env": {
"RPGGEEK_BEARER_TOKEN": "your_bearer_token_here"
}
}
}
}
Restart Claude Desktop after saving. The RPGGeek tools will appear in the tool picker.
Usage example
Once connected, you can ask Claude things like:
"Find the RPGGeek entry for Dungeon Crawl Classics"
Claude will call find_candidates to get a list of matches, then get_product_details on the best one to pull full metadata.
Running the server manually
uv run rpggeek-mcp serve
The server speaks the MCP protocol over stdio and is designed to be launched by an MCP client rather than run interactively. Logs are written to logs/rpggeek_mcp.log.
Development
Run tests:
uv run pytest
Type-check:
uv run ty check
Lint and format:
uv run ruff check .
uv run ruff format .
Notes
- Uses the RPGGeek XML API 2. A bearer token is required; see Requirements above.
- Requests are rate-limited to 1 per second to respect the API's usage guidelines.
Metadata
Release files for rpggeek-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rpggeek_mcp-0.1.0.tar.gz | 13.2 kB | Without provenance | Details for rpggeek_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rpggeek_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for rpggeek_mcp-0.1.0-py3-none-any.whl |
Total release size: 35.3 kB
Release files / rpggeek_mcp-0.1.0.tar.gz
| Download URL | rpggeek_mcp-0.1.0.tar.gz |
|---|---|
| Size | 13.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4286c44448bfa4dccf5ab38f586b1c2ecadd96d67af913bd2fff7896ba8d1e39
|
|
BLAKE2b-256 checksum How to use checksums |
9e0c4f659da4495a4ddb48bffbe885fd4b58a29cdc426f71fc52e5ce30cbf9cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.23 {"installer":{"name":"uv","version":"0.11.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / rpggeek_mcp-0.1.0-py3-none-any.whl
| Download URL | rpggeek_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 22.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
194af698c2b87e353a1822e53346b73dcd615187f600b20580d4c75c196594d1
|
|
BLAKE2b-256 checksum How to use checksums |
b3a8994bcbc711e625510ad5f64d231dddbb6fa2c61c02cf9573d4874b60ebc1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.23 {"installer":{"name":"uv","version":"0.11.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for rpggeek-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.