dtrpg-mcp
This server lets you search DriveThruRPG (a tabletop RPG digital marketplace) for products — either from your personal purchased library or the full public catalog. It requires a DTRPG_API_KEY for authentication.
Search capabilities:
Search your purchased library (
in_library: true, the default): Find products you've already bought, matching a text query against product titles (case-insensitive substring match).Search the public catalog (
in_library: false): Find any product available on DriveThruRPG, including items you don't own, using a keyword match against product titles.Control result count: Limit results via
max_values(default is 10).
Each result includes:
product_id— DriveThruRPG product identifierorder_product_id— your specific purchased order ID (null for catalog searches)title— product titledescription— short blurb about the productpublisher— publisher nameauthors— list of authors (populated for catalog searches only)game_system— game system tag (when available)
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@dtrpg-mcpsearch my library for 'Traveller' supplements"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
dtrpg-mcp
An MCP server that lets an LLM search your DriveThruRPG library and the public DriveThruRPG catalog for tabletop RPG products, returning structured details (title, description, publisher, authors, game system, and DriveThruRPG product id) for each match.
It speaks MCP over stdio and exposes two tools: search_library (your
purchased products) and search_products (the general public catalog).
Requirements
Python >= 3.12
A DriveThruRPG Application Key (see Getting an API key below)
Related MCP server: Azgaarnoth MCP Server
Installation
pip install dtrpg-mcpor, to run it without installing anything permanently:
uvx dtrpg-mcpConfiguration
The server needs one environment variable:
Variable | Required | Description |
| Yes | Your DriveThruRPG Application Key, used to authenticate against the API. |
You can set it directly in your shell/MCP client config, or drop a .env
file next to your project (the server walks up from its own install
location looking for .env, so a .env in your working directory or a
parent of it will be picked up automatically via python-dotenv).
Getting a DriveThruRPG API key
Log in to drivethrurpg.com.
Go to My Account -> Application Keys (or open
https://www.drivethrurpg.com/en/account/application-keysdirectly).Click Generate New Key, give it a name (e.g. "dtrpg-mcp"), and create it.
Copy the generated key — this is your
DTRPG_API_KEY.
The key only grants access to your library and to the public product catalog search; it does not expose your payment details or let anything make purchases on your behalf.
Using it with an MCP client
Add it to your client's MCP server config. For example, in Claude Desktop's
claude_desktop_config.json:
{
"mcpServers": {
"dtrpg": {
"command": "uvx",
"args": ["dtrpg-mcp"],
"env": {
"DTRPG_API_KEY": "your-application-key-here"
}
}
}
}If installed via pip instead of uvx, use "command": "dtrpg-mcp" with
no args.
Tools
Both tools return a list of product detail objects with the same shape:
Field | Description |
| The DriveThruRPG product id. |
| The id of your specific purchased order/product; |
| Product title. |
| A short description/blurb of the product. |
| Publisher name. |
| List of author names (only populated by |
| Game system tag, when DriveThruRPG's API surfaces one for the product; otherwise |
search_library
Search products you've already purchased in your DriveThruRPG library.
Parameters
Name | Type | Default | Description |
| string | — | Text to match against product titles (case-insensitive substring match). |
| integer |
| Maximum number of results to return. |
Example call — anything in your library with "dungeon" in the title:
{"query": "dungeon"}Performance note: DriveThruRPG's library endpoint has no server-side title filter and is capped at 50 items per page, with each page taking several seconds to return. A query that matches nothing (or matches only late in a large library) can take tens of seconds to resolve, since pages are fetched in concurrent batches rather than one huge request. This is a limitation of the underlying API, not something a client-side change can fully eliminate.
search_products
Search the general public DriveThruRPG catalog for products — not limited to your library, so this also finds things you don't own.
Parameters
Name | Type | Default | Description |
| string | — | Text to match against product titles (keyword match). |
| integer |
| Maximum number of results to return. |
Example call — search the catalog for "bardo", capped to 5 results:
{"query": "bardo", "max_values": 5}Notes on the DriveThruRPG API
DriveThruRPG does not publish official API documentation. This client's
endpoint usage was reverse-engineered from the community projects
glujan/drpg and
quickwick/drivethrurpg-calibre-plugin,
and verified empirically against the live API. Notably, the per-product
detail endpoint (GET products/{id}) returns 403 for Application Keys
like the one this tool uses (it appears to require a different auth scope),
so search_library and search_products build product details from the
library (order_products) and catalog search (products) list endpoints
instead, both of which work with a standard Application Key.
Development
uv sync
uv run pytestRun the server directly for manual/stdio testing:
uv run dtrpg-mcpAvailable Tools
1 toolsearchB
Search DriveThruRPG for products matching a title query.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Text to match against product titles (case-insensitive substring match for library search; keyword match for catalog search). | |
| in_library | No | If true (default), search only the products already purchased in the caller's DriveThruRPG library. If false, search the full public DriveThruRPG catalog instead. | |
| max_values | No | Maximum number of results to return (default 10). |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It only says 'search', which implies a read operation, but does not state idempotency, safety, or side effects. Important context like the library/catalog behavior is missing from the description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that conveys the core purpose efficiently. No extraneous words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 3 parameters and no annotations, the description is too sparse. It omits key context such as the library vs catalog distinction, result limits, and what the output contains. The output schema covers return format but the description should at least indicate results are products.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description adds minimal semantic value beyond the schema—just 'title query' which is already detailed in the schema fields.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches DriveThruRPG for products matching a title query. It is specific and unambiguous, but lacks mention of the library vs catalog context which is a key differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implicitly conveys usage: when you need to search products by title. However, it provides no explicit guidance on when to choose this tool over alternatives, nor does it mention that the library/catalog distinction exists.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v0.1.0- First observed
search
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools, so disambiguation is perfect.
The single tool name 'search' is clear and consistent with itself; no pattern inconsistency exists.
A single search tool is far too few for a server intended to interact with a product database like DriveThruRPG, which typically requires multiple operations (e.g., retrieve details, filter, browse).
The server only provides search functionality, lacking essential operations like getting product details, browsing categories, or managing purchases, making it severely incomplete for its domain.
Maintenance
Related MCP Connectors
Agentic search over your Dewey document collections from any MCP-compatible client.
Federated search of books and papers, BibTeX/RIS citations, open-access retrieval and reading.
Academic literature search, retrieval, and private library management on top of OpenAlex.
- acopioOAuthdev.acopio
Search and get recommendations from your own saved catalog of developer tools and services.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables product search and retrieval from e-commerce APIs, returning markdown-formatted product listings with clickable links and prices for easy shopping assistance.5 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides AI assistants with tools to query and explore the Azgaarnoth D\&D world repository, including searching content, retrieving stat blocks, spells, and browsing categories like races, classes, nations, and creatures across ~4,200 markdown files.-
- AlicenseNot gradedqualityDmaintenanceProvides access to the DigiKey Product Search API v4, allowing users to search for electronic components and retrieve detailed product specifications. It supports keyword searches, pricing inquiries, manufacturer lookups, and access to technical datasheets.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables users to search and retrieve board game data via the Board Game Atlas API, including game details, ratings, and availability.8 npmMIT