大禹
Related Servers
Alternatives to 大禹
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 gradedqualityCmaintenanceEnables MCP clients to create and manage long-form story projects with isolated databases, persistent drafts, canonical continuity checks, controlled updates, and local semantic retrieval through MCP tools, resources, and prompts.MIT
- AlicenseNot gradedqualityBmaintenanceEnables long-form web novel writing workflows by ingesting chapters into a state database, running deterministic consistency checks, querying entity histories, replaying extraction results, and retrieving conflict reports via MCP tools.MIT
- AlicenseAqualityBmaintenanceContinuity by Ouroboros Apps (https://ouroborosapps.com). Story continuity for fiction writers: a series bible and novel memory that keeps characters, places, timelines, and plot facts consistent across chats. Connect by pasting https://continuitywriter.com/mcp into Claude, Cursor, Grok, or ChatGPT (OAuth). Docs: https://ouroborosapps.com/docs/continuity11MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to draft long-form web novels with persistent, disk-backed memory, assembling a pre-writing task brief from structured settings, outlines, foreshadowing ledgers, and timelines, then committing post-chapter fact increments. It also audits pacing, checks per-chapter six-dimension consistency, gates commits on unresolved review findings, and can replay the commit chain to rebuild state when records and manuscripts disagree.1MIT
TDQS
Scored across 27 tools
The foreshadow family (list/health/overdue/extract/add/resolve/touch) is mostly separable, but foreshadow_health and foreshadow_overdue clearly overlap, as do extract_facts and extract_foreshadow. More seriously, check_redline, check_ai_flavor, check_format, check_self_consistency, and check_pacing are all described as sub-components that review_chapter already runs internally, so an agent cannot easily tell when to call the standalone check versus the aggregate review. The four bare-name tools (character/goldfinger/tone/harddata) read like variants of save_card rather than distinct operations.
Most tools use verb_noun snake_case (save_outline, check_title, add_foreshadow, resolve_foreshadow), which is readable and predictable. However, several use noun_verb ordering (foreshadow_list, foreshadow_health, foreshadow_overdue), one is noun_verb reversed (release_gate), and four are bare nouns (character, goldfinger, tone, harddata) with no verb at all. The mix of prefix-style and suffix-style grouping makes scanning the tool list harder than it needs to be.
At 27 tools this exceeds the comfortable range, and the inflation is partly artificial: character/goldfinger/tone/harddata appear to be one save_card call differentiated by a type parameter, and five check_* tools duplicate work already bundled into review_chapter. A pipeline this complex justifies many tools, but several do not earn a separate entry.
The surface covers the full lifecycle well: project init, 7-step SOP tracking, chapter planning, outline persistence, multi-layer review, release gating, drift callback, methodology lookup, and a complete foreshadow add/resolve/touch/list/health/overdue loop. Gaps remain around chapter manuscript handling (outlines can be saved but there is no save_chapter/get_chapter or chapter listing) and there is no update/delete path for foreshadow or cards, so mistakes must be worked around rather than corrected.