dnd-beyond-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ddb_loginA | Open a browser and log into D&D Beyond via Wizards ID. Run once — the session is saved to disk and reused automatically on all future calls. |
| ddb_statusA | Check whether the D&D Beyond session is active. Run ddb_login first if this reports not logged in. |
| ddb_list_charactersA | List all characters in your D&D Beyond account (name, ID, level, race, class). |
| ddb_get_characterB | Get the full character sheet for a D&D Beyond character by ID or name. |
| ddb_get_campaignA | Get campaign details and member roster for a D&D Beyond campaign. |
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 5 tools
Each tool has a clear, distinct purpose: login, status check, list characters, get character details, and get campaign details. There is no overlap or ambiguity between them.
All tools follow the consistent prefix 'ddb_' and verb_noun pattern (e.g., ddb_get_campaign, ddb_list_characters). Even login and status fit the pattern without underscore, maintaining uniformity.
With 5 tools covering authentication, status, listing, and detailed retrieval, the count is well-scoped for a focused D&D Beyond integration. It is neither too sparse nor overwhelming.
The tool set provides a solid read-only surface: login, session check, character listing, character details, and campaign details. Missing write operations (e.g., create/update character) but covers the core retrieval needs for the domain.