Grimoire

What the Grimoire MCP server does

The Grimoire MCP server gives an AI client direct access to structured campaign data for D&D and other tabletop RPGs. Campaign records can include NPCs, locations, factions, quests, items, player characters, creatures, vehicles, lore, world rules, planar forces, session recaps, session preparations, and custom mechanics.

The data model also includes typed relationships, open plot threads, world foundations, campaign metadata, session observations, and a collaborative wiki. This lets an assistant answer questions using current records and update those records after a conversation. For example, it can retrieve recent sessions and unresolved threads, identify entities connected to a location, or record a new recap in the campaign database.

How it works

The hosted endpoint is https://api.ttrpg.bot/mcp and uses Streamable HTTP with the MCP specification dated 2025-06-18. Authentication uses OAuth 2.1 with PKCE. During the first connection, the client opens a browser sign-in and consent flow. The user then selects a campaign, and access is restricted to that campaign on the server.

The Grimoire MCP server exposes 52 tools: 21 for reading and 31 for writing. Read operations return typed campaign state rather than requiring the model to search a folder of prose. Write operations update entities, wiki blocks, thread progressions, observations, relationships, and other supported records.

Visibility is applied server-side. The material describes common-knowledge, player-knowledge, and GM-secret tiers, plus a system tier for wiki content. Wiki inheritance can resolve through linked blocks and parent pages. Player connections receive filtered views, and inaccessible pages are not available to that connection.

Setup and configuration

No local installation is required. Add the endpoint as a custom connector in a compatible MCP client, sign in through the consent screen, choose a campaign, and approve access. A free account at https://www.ttrpg.bot provides the campaign used by the connection.

Clients configured with a JSON file can use:

{
  "mcpServers": {
    "grimoire": {
      "type": "streamable-http",
      "url": "https://api.ttrpg.bot/mcp"
    }
  }
}

The README specifically documents adding the connector in Claude.ai or ChatGPT, and also states that clients supporting custom connectors can use the endpoint. OAuth handles authentication; no token value or environment variable is listed for configuration.

Tools and capabilities

The tool groups cover:

• Entity search, retrieval, listing, schema inspection, creation, updates, deletion, and batch creation across 14 entity types.
• Typed relationships between campaign entities.
• Political, timeline, and geographic knowledge-graph queries with visibility filtering.
• World-foundation nodes and edges, including structured magic-system, divine-hierarchy, and fundamental-law data.
• Open-thread creation, resolution, updates, and session-by-session progressions.
• Wiki tree navigation, full-text search, page and block editing, reordering, batch operations, tables, and links to entities or pages.
• Campaign context, narrative state, campaign bible access, and updates.
• GM-only session observations that appear through narrative-state and timeline graph results.

A campaign://wiki MCP resource lists wiki pages and their hierarchy. The project also supplies a Claude Skill, usable as plain instructions, for session-start context gathering, typed writes, recap filing, and preparation workflows.

Limitations and notes

The service is hosted rather than self-hosted according to the supplied setup material. It requires a Grimoire account and an MCP client that can connect to the Streamable HTTP endpoint and complete OAuth 2.1 with PKCE. The provided material does not specify a local server package, environment variables, or an explicit software license.

The server is intended for campaign management, not general-purpose document storage. Entity searches cover campaign records, while wiki search covers page titles and block prose. Access to secrets depends on the connected role and visibility rules, so clients should not assume every campaign record is available to every user.