D&D Beyond MCP Server
Related Servers
Alternatives to D&D Beyond MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceAn MCP server that provides Claude direct access to D\&D Beyond accounts to manage characters, campaigns, and sourcebook content. It enables users to search for spells and monsters, retrieve character data, and read owned digital books through an authenticated session.6-
- AlicenseBqualityDmaintenanceA comprehensive Model Context Protocol server for managing Dungeons & Dragons campaigns with tools for characters, NPCs, locations, quests, combat encounters, and session tracking.3014MIT
- FlicenseNot gradedqualityCmaintenanceA local MCP server that provides access to D&D Beyond character sheets, SRD content (spells, monsters, items), a dice roller, and optional campaign tools via undocumented endpoints.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to read D&D Beyond characters, campaigns, and game reference data, with optional opt-in tools for session tracking and character building.MIT
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to Dungeons & Dragons 5e game information via the Model Context Protocol, enabling queries for spells, monsters, equipment, and more.48MIT
- FlicenseNot gradedqualityBmaintenanceA D&D 5e digital toolset with an MCP server enabling Claude to manage characters, search the SRD, roll dice, and interact with campaigns and encounters. It syncs data with the web app for real-time collaboration.-
TDQS
Scored across 35 tools
Most tools have clearly distinct purposes: search_* vs get_* vs list_*, plus unique tools like ddb_login and ddb_rate_encounter. Minor overlap exists between ddb_search_site and the specific compendium searches, and between ddb_get_rules and ddb_get_condition, but descriptions help clarify.
The ddb_ prefix and common verbs (search_*, get_*, list_*) create a predictable pattern. Deviations like ddb_character_lookup (instead of ddb_lookup_character) and single-word verbs (ddb_login, ddb_navigate, ddb_interact) break the convention slightly, but the overall scheme remains readable.
With 35 tools, this is well beyond the 25+ threshold and feels heavy for an agent to navigate. While the domain is broad, many tools could be consolidated (e.g., a single compendium search with type filters) or the server could be split into focused servers.
The tool surface is extensive, covering characters, campaigns, compendium searches, rules, books, browser automation, and encounter tools. However, there are notable gaps: you can search for feats, races, classes, backgrounds, and class features, but there are no corresponding ddb_get_* tools for these categories (only ddb_character_lookup which requires a character). This makes it impossible to directly retrieve full details for those compendium items.