Story continuity, novel memory, and series bible for fiction writers, shared with AI assistants
Scored across 11 tools
Each tool has a fairly distinct resource+action target, and descriptions actively disambiguate overlapping retrieval tools (get_continuity_context vs search_story_canon vs get_canon_history). Minor risk of confusion remains between list_approved_scenes and get_continuity_context, which both surface scene content, but the stated selection-vs-verification split keeps them mostly separable.
Nearly all tools follow a verb_noun pattern (create_story_project, get_canon_history, list_approved_scenes, save_story_checkpoint, upsert_canon_entry) with consistent domain prefixes for story/canon/scene/checkpoint. continuity_audit breaks the pattern as noun_verb instead of audit_continuity, a minor deviation.
11 tools sit squarely in the well-scoped range and each maps to a distinct part of the continuity workflow (projects, canon, scenes, checkpoints, context, audit). No redundant or filler tools are apparent.
The surface covers the core lifecycle: create/list projects, upsert/search/history canon, record/list scenes, save/list checkpoints, and audit. Gaps are deletion/update of projects, scenes, and checkpoints, likely intentional for an append-only canon model, so agents can work around them.
Retrieve locked canon for the assistant to compare against a short proposed scene. This tool supplies evidence; the assistant must identify contradictions. Does not save or approve the scene.
Inputs: projectId (required), proposedText (required), offset. Returns: data
Create a new private story project when the user asks. Does not save canon or scenes.
Inputs: name (required), description. Returns: data
Read previous and new content for a saved canon entry, newest first. No changes are made.
Inputs: canonEntryId (required), offset. Returns: data
Retrieve relevant canon, recent approved scenes, and the latest provisional checkpoint before continuing a saved story or recovering it in a new chat. request is a brief scene/topic query, never a chat transcript. Results are a selection; use search_story_canon for specific missing facts.
Inputs: request (required), projectId (required), limit. Returns: data
Read approved scene summaries in story order. Page with offset to inspect older scenes or verify a scene number before saving.
Inputs: projectId (required), offset. Returns: data
Retrieve provisional story handoffs to recover progress across chats. These notes never override approved canon. Page with offset for older checkpoints.
Inputs: projectId (required), offset. Returns: data
Find the user’s saved story projects before starting or resuming a story. Use the returned ID; do not guess projects. Page with offset.
Inputs: offset. Returns: data
Store a concise summary of a scene the user has approved. Never record an unapproved draft. An occupied scene number is preserved unless replaceExisting is true and the user requested replacement. Identical retries return the saved scene.
Inputs: summary (required), projectId (required), sceneNumber (required), title, +2 more. Returns: data
Preserve a concise story-session handoff when the user asks to save progress or has authorized ongoing checkpoints for this story. Stores provisional notes, not canon or an approved scene. Separate established progress from unresolved ideas. Send only focused story state, never a full transcript, credentials, or unrelated personal details. Reuse checkpointId on retries.
Inputs: title (required), projectId (required), storyState (required), checkpointId (required), +2 more. Returns: data
Search saved canon by literal title/content text, or browse every entry with an empty query and offset. Use to verify details before revising an entry or when context retrieval omits something.
Inputs: projectId (required), query, offset. Returns: data
Save a fact or revise canon only after the user approves it. Preserve the existing title/kind. LOCKED requires approval as established fact; brainstorming is not approval. Existing entries require expectedRevision from retrieval; conflicting edits fail without overwriting. Identical retries leave revision history unchanged.
Inputs: kind (required), title (required), status (required), content (required), +6 more. Returns: data
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Write a novel in the Claude or ChatGPT you already pay for. Keeps your book, cast and timeline.
A structured story bible for long-form fiction: scenes, characters, world, plot and foreshadowing.
Personal wiki and memory layer for AI assistants. Persistent, structured memory across sessions.
D&D and TTRPG campaign manager for GMs: your AI reads and writes a live, typed campaign database.
Add one secure layer between your agents and this server.