Remote MCP server · was in the free directory

Continuity

io.github.LAHutchins91/continuity · 0.5.1

Private story bible for fiction writers, shared with AI assistants over MCP.

Now publishes source, not yet read

Its registry entry now declares a source repository: https://github.com/LAHutchins91/continuity-mcp, as the entry declares it. Nothing here has read it yet. It left the directory on 7 October 2026, when the nightly registry sweep recorded the change. The catalogue reads declared repositories in batches run by hand and lists a server only once it has read it; until then, this page is the record.

This page is the directory's record. Nobody here has read this server's code yet. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.

The tools it lists (11, as of 4 days ago)

The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.

list_story_projects

Find the user’s saved story projects before starting or resuming a story. Use the returned ID; do not guess projects. Page with offset.

create_story_project

Create a new private story project when the user asks. Does not save canon or scenes.

get_continuity_context

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.

search_story_canon

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.

upsert_canon_entry

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.

get_canon_history

Read previous and new content for a saved canon entry, newest first. No changes are made.

list_approved_scenes

Read approved scene summaries in story order. Page with offset to inspect older scenes or verify a scene number before saving.

record_approved_scene

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.

save_story_checkpoint

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.

list_story_checkpoints

Retrieve provisional story handoffs to recover progress across chats. These notes never override approved canon. Page with offset for older checkpoints.

continuity_audit

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.

Continuity

Where it answers

Connection test

The tools it lists (11, as of 4 days ago)