Connect Grimoire to Claude
Give Claude access to your campaign with a single click.
Grimoire is an MCP server, which means you can plug it into Claude (the chat product at claude.ai or the Claude Desktop app) and ask Claude questions about your campaign in plain English. Claude will fetch NPCs, locations, factions, wiki pages, open story threads, and anything else it needs directly from your Grimoire campaign.
No installation. No copy-pasting tokens. No JSON config files. You add Grimoire to Claude once, sign in with your existing Grimoire account, choose a campaign, and you're connected.
What Claude can do once connected
- Read everything about a single campaign you've picked: NPCs, locations, factions, items, lore, quests, sessions, relationships, the campaign bible, the wiki, and open story threads.
- Create and update entities on your behalf if you're the Game Master ("Create an NPC named Thrain, a dwarven weaponsmith based in Millbrook").
- Respect visibility rules. DM-only content stays DM-only. Player tokens can't read DM secrets or modify anything.
- Stay within one campaign. A connection is bound to the campaign you approved on the consent screen — Claude cannot see your other campaigns through the same connection.
How to connect (Claude.ai web)
Step 1: Open Claude's Connector settings
Sign in to claude.ai, open Settings (your profile icon → Settings), then choose Connectors in the sidebar.
Step 2: Add a custom connector
Scroll to the bottom and click "Add custom connector." A dialog will ask for a server URL. Paste:
https://api.ttrpg.bot/mcp
Click Add.
Step 3: Sign in to Grimoire
Claude will open a Grimoire login page in a new tab. Sign in with the same account you use for the Grimoire app (Google, Discord, GitHub, or your player account).
Step 4: Choose a campaign
After login, Grimoire shows a consent screen listing the campaigns you own. Pick the campaign you want Claude to access, review the permissions ("read campaign data," "modify campaign data"), and click Approve & connect. If you only own one campaign, it's selected for you automatically.
Step 5: Use it
You're back in Claude.ai. The Grimoire connector shows up under the paperclip menu and Claude will use it whenever a question requires campaign data. Try:
"What NPCs are in my campaign?"
"Who is the blacksmith in Millbrook, and what's their relationship to the Merchant's Guild?"
"Create an NPC named Thrain — a dwarven weaponsmith, blunt but fair, sells custom armor."
"Summarize what happened in our last session and what story threads are still open."
"Help me prep next week's session — what factions are scheming, and which NPCs are likely to show up?"
How to connect (Claude Desktop)
The flow is essentially the same. Open Claude Desktop, go to Settings → Connectors → Add custom connector, paste https://api.ttrpg.bot/mcp, sign in, pick a campaign, approve. Claude Desktop opens the consent flow in your default browser.
Switching campaigns
A connection is bound to a single campaign for security — Claude only sees what you explicitly granted. To grant access to a different campaign:
- Remove the existing connector from Claude.ai Settings → Connectors.
- Add it again with the same URL.
- Pick the new campaign on the consent screen.
(You can also keep two connections — for example, one named "Worldspire (Sunday game)" and one named "Sea of Stars (Tuesday game)" — by adding the URL twice and picking a different campaign each time.)
Revoking access
Three ways:
- From Claude: Remove the Grimoire connector from Settings → Connectors. Claude will discard its tokens.
- From Grimoire: In your Grimoire account settings, you can revoke any client's access. Within 15 minutes the AI's active token expires and it loses the ability to call our server.
- Account-wide: Email us at privacy@ttrpg.bot if you think a token has leaked and we'll revoke everything tied to your account.
What Claude actually sees
Worth being clear: when you grant access, Claude does *not* download a copy of your campaign. It calls Grimoire each time it needs something. The data lives on Grimoire's servers; Claude sees only the specific entity / page / search result it asked for in the moment.
Read more in our Privacy Policy section on AI integration.
Tool inventory
The MCP server exposes 33 tools across six domains:
Search & read (read-only): search_campaign · get_entity · list_entities · get_field_options · get_tag_options · get_entity_catalog · get_constitution · get_campaign_bible · get_wiki_page · get_wiki_tree · get_relationships · get_open_threads · get_thread_progressions · get_narrative_state · current_campaign
Create & modify (Game Master only): create_entity · update_entity · delete_entity · batch_create_entities · update_campaign_bible · create_wiki_page · create_wiki_block · update_wiki_block · move_wiki_block · delete_wiki_block · batch_create_wiki_blocks · batch_reorder_wiki_blocks · add_relationship · delete_relationship · create_open_thread · update_open_thread · resolve_open_thread · unresolve_open_thread · add_thread_progression
Claude decides which tool to call based on your question — you don't need to memorize this list.
Troubleshooting
"I don't see a 'Connect' button after adding the URL."
Make sure you pasted exactly https://api.ttrpg.bot/mcp with no trailing slash or query string. The connector should appear under Settings → Connectors with a "Sign in" button next to it.
"The consent screen says I don't have any campaigns."
You're logged in to a Grimoire account that doesn't own any campaigns. Create or import one in Grimoire first, then retry the connector flow.
"Claude says it doesn't know about something I know is in my campaign."
Two common causes: (1) the connector's tools aren't enabled in Claude's tool permissions — open the connector settings and verify the relevant tools are toggled on; (2) the content is set to DM-only visibility and you connected with a Player token instead of a GM token.
"Connection expired" / Claude asks me to reconnect.
Tokens are short-lived for security and refreshed automatically. If automatic refresh ever fails, just click reconnect — Claude will reopen the consent flow.