Manage TTRPG campaigns: NPCs, locations, factions, quests, sessions, lore, and knowledge graphs.
If you already use Grimoire, the grimoire mcp server is the piece that lets your assistant work with it directly. Manage TTRPG campaigns: NPCs, locations, factions, quests, sessions, lore, and knowledge graphs.
Grimoire is a campaign manager for D&D and tabletop RPG gamemasters with a hosted MCP server built in. A campaign in Grimoire is structured data, not pages: typed NPCs, factions, locations, quests, items, sessions, and lore, connected by relationships and knowledge graphs. This MCP gives any AI client you connect a live, structured view of that database and your current situation in-game, so the AI answers from your actual canon instead of guessing. Upload and parse notes into structured database entities, query your world by relationship, drive prep and recaps from the conversation you're already having.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Product — https://www.ttrpg.botChangelog — https://www.ttrpg.bot/changelogSupport — zmanlevelup@gmail.comEndpoint — https://api.ttrpg.bot/mcpTransport — Streamable HTTP (MCP spec 2025-06-18)Auth — OAuth 2.1, one-click consent flowTools — 48 across 7 groups (20 read, 28 write)This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Grimoire's toolset — Product, Changelog, Support and 4 more — is a fair guide to whether it matches your workflow. It is maintained by bot.ttrpg; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Grimoire's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Product | https://www.ttrpg.bot |
| Changelog | https://www.ttrpg.bot/changelog |
| Support | zmanlevelup@gmail.com |
| Endpoint | https://api.ttrpg.bot/mcp |
| Transport | Streamable HTTP (MCP spec 2025-06-18) |
| Auth | OAuth 2.1, one-click consent flow |
| Tools | 48 across 7 groups (20 read, 28 write) |
{
"mcpServers": {
"grimoire": {
"type": "streamable-http",
"url": "https://api.ttrpg.bot/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.