Archivist AI

Archivist AI MCP Server

The official Model Context Protocol (MCP) server for Archivist AI -- a TTRPG campaign memory platform for game masters and players.

Registry metadata lives in server.json. Publishing to the official MCP Registry is automated on version tags via .github/workflows/publish-mcp.yml (git tag v3.0.1 && git push origin v3.0.1).

Connect AI assistants like Claude, ChatGPT, Cursor, Notion, and Windsurf directly to your campaign data: characters, sessions, locations, factions, items, quests, journals, key moments, hero awards, quotes, spotlights, and more.

Quick Start

MCP Server URL: https://mcp.myarchivist.ai/mcp

Discord tools live on a sibling host: https://discord.myarchivist.ai/mcp. That is a separate MCP resource (OAuth + your recording bot) and does not replace campaign tools here.

Claude Desktop

Claude Desktop requires the mcp-remote proxy (Node.js must be installed).

Add to your claude_desktop_config.json (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):

{

"mcpServers": { "archivist-ai": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.myarchivist.ai/mcp", "--header", "X-API-Key:${ARCHIVIST_API_KEY}" ], "env": { "ARCHIVIST_API_KEY": "YOUR_API_KEY" } } } }

Replace YOUR_API_KEY with your Archivist AI API key from app.myarchivist.ai. Restart Claude Desktop after saving.

API keys must be sent in the X-API-Key header. Do not put an API key in an Authorization: Bearer header; Bearer credentials are reserved for OAuth access tokens.

OpenCode

OAuth (recommended):

{

"$schema": "https://opencode.ai/config.json", "mcp": { "archivist-ai": { "type": "remote", "url": "https://mcp.myarchivist.ai/mcp" } } }

To use an API key instead, disable OAuth auto-detection and send the key in X-API-Key:

{

"$schema": "https://opencode.ai/config.json", "mcp": { "archivist-ai": { "type": "remote", "url": "https://mcp.myarchivist.ai/mcp", "oauth": false, "headers": { "X-API-Key": "{env:ARCHIVIST_API_KEY}" } } } }

</details>

Cursor

Add to .cursor/mcp.json in your project:

{

"mcpServers": { "archivist-ai": { "url": "https://mcp.myarchivist.ai/mcp" } } }

</details>

Windsurf

Add to your MCP configuration:

{

"mcpServers": { "archivist-ai": { "serverUrl": "https://mcp.myarchivist.ai/mcp" } } }

</details>

ChatGPT

Archivist AI is available as a ChatGPT plugin. Search for "Archivist AI" in the ChatGPT plugin store.

Example Prompts

• "List my campaigns, then summarize the most recent session of my Curse of Strahd campaign."
• "Create a new NPC named Captain Mirelle Voss, a smuggler who works for the Silver Hand faction, and link her to the Port of Dusk location."
• "Add a quest called 'Recover the Moonstone' to my campaign, then list all open quests and the characters involved."

Available Tools

Read tools are non-destructive and idempotent. Write tools follow standard REST semantics — deletes are destructive and idempotent; PATCH is non-idempotent; PUT is idempotent. Every read tool that returns text-carrying descriptions (Character, Faction, Location, Item, Moment, Beat, Session, Journal) accepts an optional with_links parameter — see Wikilinks below for why you almost always want to pass with_links: true before editing.

Campaign delete, session delete, product-view-only endpoints (beat reorder/batch-edit, campaign settings, cast/member management), multipart recording uploads, and AI image generation are intentionally not exposed.

OAuth scopes and write access

OAuth clients that connect via https://app.myarchivist.ai request scopes at authorization time. Every write tool (create/update/delete + image upload) additionally requires the agent_write scope on the caller's token.

The MCP mirrors the API's enforcement in tools/list: agent clients without agent_write see only the read tools, and receive a "tool not found" JSON-RPC error if they attempt to call a write tool anyway. API-key credentials and non-agent OAuth clients bypass this filter — the API is the authoritative gate for them and all tools remain visible.

Existing OAuth clients that connected before agent_write was advertised need to re-authorize to receive a token with the new scope.

Campaigns

Sessions

Story Structure

Highlights

World Building

Quests

| Tool | Descript