dtrpg-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DTRPG_API_KEY | Yes | Your DriveThruRPG Application Key, used to authenticate against the API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Search DriveThruRPG for products matching a title query. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.