MCP Integrations

Connect Your AI Assistant to Your Campaigns

Bardkeeper speaks the Model Context Protocol. Let Claude, ChatGPT, or Gemini search your sessions and answer questions about your world — without leaving the conversation.

What you can do

The Model Context Protocol is an open standard that lets AI assistants securely read from external data sources. Once connected, your assistant can ask Bardkeeper about your campaigns and use the answers in its replies.

  • Ask questions about your campaign lore and get answers grounded in your actual session transcripts and notes.
  • Search across every session for specific dialogue, NPC names, items, or quotes.
  • Pull up session summaries, character rosters, and the NPCs, locations, and factions you've catalogued.
  • Explore how entities connect across sessions — useful for prep and recaps.

Getting started

Prerequisites

  • A Bardkeeper account (sign in with Discord).
  • An AI assistant that supports the Model Context Protocol (Claude, ChatGPT, Gemini, and others).
1

Claude Desktop

Fastest path. Click below and Claude Desktop opens with the Bardkeeper server pre-configured — just approve in the browser.

Connect Claude Desktop
2

ChatGPT, Gemini & other MCP clients

Point your client at the Bardkeeper MCP URL. On first use you'll sign in with Discord and approve access — no tokens to copy and paste.

Your client discovers the OAuth endpoints automatically from this URL.

3

OpenClaw

OpenClaw's MCP client registry supports OAuth for streamable HTTP servers. Save the Bardkeeper server definition, then run the login flow from the CLI.

openclaw mcp set bardkeeper '{"url":"https://bardkeeper.com/mcp","transport":"streamable-http","auth":"oauth","oauth":{"scope":"mcp:read"}}'
openclaw mcp login bardkeeper
openclaw mcp login bardkeeper --code <code-from-browser>
openclaw mcp doctor bardkeeper --probe

Logout clears stored credentials without removing the server definition: openclaw mcp logout bardkeeper

4

Scripts & API clients

For automation or clients without OAuth, generate a Personal Access Token from your account page and send it as a Bearer token.

Generate a token from your account page:

Manage MCP Tokens

Send the token as Authorization: Bearer <token>.

Access & permissions

Bardkeeper MCP reuses your Discord login. Your assistant only sees the campaigns you own or have been granted access to — same permission model as the web dashboard.

  • Sign in with Discord — OAuth 2.1 with PKCE is the primary flow — no shared API keys to leak.
  • Read-only by default — Connected assistants can search and read your campaign data. Write tools are gated behind a separate scope and a server-side flag.
  • Revocable tokens — Personal Access Tokens for scripts are scoped, labelable, and can be revoked anytime.