
Wraps the free D&D 5th Edition API so Claude can look up spells, monsters, and game rules without authentication. Part of the Pipeworx gateway that bundles 250+ data sources behind a single MCP endpoint. Right now it exposes list_spells for searching by name or level, plus get_spell for full details. You can call tools directly or use ask_pipeworx to handle queries in plain English and let the gateway route them. Useful if you're building D&D character sheets, campaign tools, or just need quick spell lookups during a session. No API keys, no rate limits mentioned, just point your MCP client at the gateway URL.
D&D 5e MCP — wraps the D&D 5th Edition API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_spell | Get spell details including damage, range, duration, components, and effects. Provide spell index (e.g., "fireball", "magic-missile", "cure-wounds"). Returns damage dice, range, casting time, and effect descriptions. |
get_monster | Get monster stats including AC, HP, abilities, skills, senses, and actions. Provide monster index (e.g., "aboleth", "dragon-red-adult", "goblin"). Returns ability scores, skill bonuses, and attack/action details. |
get_class | Get class features, hit dice, proficiencies, and advancement tables. Provide class index (e.g., "barbarian", "wizard", "rogue"). Returns feature progression, proficiency gains, and subclass options. |
list_spells | Search D&D 5e spells by name or level. Returns spell indices, names, and levels for use with get_spell to fetch full details. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"dnd5e": {
"url": "https://gateway.pipeworx.io/dnd5e/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/dnd5e/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Dnd5e data" })
The gateway picks the right tool and fills the arguments automatically.
MIT