
Continuity by Ouroboros Apps
Story continuity, novel memory, and series bible for fiction writers, shared with AI assistants
What it can do
What data it sees
Do you need an account
No: the server works without sign-in
Story continuity, novel memory, and series bible for fiction writers, shared with AI assistants
How to connect
How to connect Continuity by Ouroboros Apps to Claude
The server address to paste into Claude settings:
https://continuitywriter.com/mcp
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect Continuity by Ouroboros Apps to ChatGPT
The server address to paste into ChatGPT settings:
https://continuitywriter.com/mcp
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect Continuity by Ouroboros Apps to Cursor
The server address to paste into Cursor settings:
https://continuitywriter.com/mcp
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (11)
Raw names from tools/list. Only developers need these.
| 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. |