OpenApps

Continuity by Ouroboros Apps MCP server — tools & history

Continuity by Ouroboros Apps MCP server: observed open status, tool schemas, linked apps and version history.

Continuity by Ouroboros Apps

Endpoint: https://continuitywriter.com/mcp

Observed status: open. Checked: 2026-10-12T05:10:24+00:00.

Linked apps

  • Continuity by Ouroboros Apps

    I built Continuity so Cursor and other MCP clients can keep my story bible straight: characters, places, timelines and plot facts stay consistent across ChatGPT, Claude, Grok and Cursor. MCP URL: https://continuitywriter.com/mcp. More plugins at https://ouroborosapps.com.

Observed tools

  • 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.
  • create_story_project — Create a new private story project when the user asks. Does not save canon or scenes.
  • get_canon_history — Read previous and new content for a saved canon entry, newest first. No changes are made.
  • 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.
  • list_approved_scenes — Read approved scene summaries in story order. Page with offset to inspect older scenes or verify a scene number before saving.
  • list_story_checkpoints — Retrieve provisional story handoffs to recover progress across chats. These notes never override approved canon. Page with offset for older checkpoints.
  • 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.
  • 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.
  • 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.

Data as of 2026-10-12T05:10:24+00:00.

OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.

REST API specification · Guide for AI clients · Manage API keys and MCP connections