Continuity by Ouroboros Apps
Related Servers
Alternatives to Continuity by Ouroboros Apps
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables writers and AI agents to preserve continuity in long-form fiction by maintaining a narrative knowledge graph and exposing MCP tools for querying outlines, entities, references, and consistency diagnostics.14MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI-driven long-form novel creation and management, including chapter generation, character and timeline tracking, semantic memory retrieval, version savepoints, and deep consistency checking across multiple projects through MCP tools, with support for local LM Studio or any OpenAI-compatible API.16MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to search canon works, lock timeline-scoped rules and character seals, audit plots for out-of-character or canon-breaking content before writing, and generate divergent worldbuilding hooks.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for managing a writer's bible, a structured and searchable knowledge base of a narrative universe with tools for characters, places, events, and semantic search.-
- AlicenseNot gradedqualityBmaintenanceEnables any MCP-capable AI app to share one private, user-owned memory, so a fact told to ChatGPT on a phone can be recalled by Claude, Gemini, Cursor, Codex or another client later. It stores, searches, reads and updates short fact pages, keeps old values in history instead of deleting them, and refuses to save passwords or keys.370 npmMIT
- AlicenseAqualityCmaintenanceProvides a persistent, branching store for fictional scenes — stories, character assignments, turns and editable summaries — exposed as ten validated, revision-checked MCP tools. Supports optimistic concurrency, idempotent turn appends, canon rules and story export over a bearer-token-authorized HTTP boundary that fails closed.10MIT
TDQS
Scored across 11 tools
Most tools map cleanly to a resource+action (scenes, projects, checkpoints, canon writes), so selection is straightforward. The one soft cluster is the three read paths over canon — get_continuity_context, search_story_canon, and continuity_audit — which all return canon-ish content, though the descriptions draw usable lines (bundle vs. literal lookup vs. locked-canon evidence for contradiction checks).
Ten of eleven tools follow a clear verb_noun pattern (get_, search_, upsert_, list_, record_, create_, save_). The lone outlier is continuity_audit, a bare noun_verb with no leading action verb, and the domain prefix drifts between story_ and canon_ across otherwise parallel tools.
Eleven tools is well within the sweet spot and each one covers a distinct surface: context recovery, canon read/write/history, scenes, projects, and checkpoints. No tool looks redundant or filler.
Core lifecycle is covered: canon has upsert plus literal search and revision history, scenes have list and record (with replaceExisting), checkpoints have save and list, projects have list and create. The notable gap is that nothing is ever deletable — no canon removal, no project rename/delete, no checkpoint pruning — which is plausibly intentional for an append-only continuity log but leaves dead ends for cleanup.