Skip to main content
Glama
jedikim

storyai

by jedikim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to storyai

No user-submitted related servers found.

    Related Servers

    • Novel Workspace MCP

      LiZh132707
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      15
      MIT

    • canonkeeper-mcp

      zhangzhend0ng
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    • Continuity by Ouroboros Apps

      LAHutchins91
      A
      license
      Not graded
      quality
      B
      maintenance
      Continuity 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/continuity
      9 npm
      MIT

    • story-agent

      Mufalp
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    • ledger-mcp

      kbkb628
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables a scriptwriting agent to build and query a persistent, per-project ledger of story propositions and each character's knowledge state, so every proposed line of dialogue is checked before it is written and blocked when it uses information that character cannot yet know. Also supports full-script leak audits, incremental scene ingestion, wiki-style ledger lookups, and waiving false positives with an auditable decision trail.
      19 npm
      MIT

    • Alethea World History Engine

      Watashicuvu
      A
      license
      Not graded
      quality
      D
      maintenance
      A narrative graph engine that enables LLMs to generate, track, and mutate complex fictional worlds while maintaining consistency between factions, characters, and locations. It acts as a specialized RAG framework for storytelling, allowing models to manage thousands of entities without exceeding context limits.
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 14 tools

    Disambiguation4/5

    Each tool targets a clearly distinct operation: search (find), read (get, outline), graph navigation (refs, trace, neighborhood), diagnostics (check, impact), and staged writes (ingest, propose, commit). Minor overlap exists between ingest/propose (both create proposals) and check/impact (both diagnostic), but the descriptions draw clear boundaries.

    Naming Consistency3/5

    Naming is mixed: most tools use imperative verbs (get, find, check, commit, propose, ingest, trace, query), but several are nouns or abbreviations (outline, promises, refs, neighborhood, graph_schema). The pattern is readable but inconsistent across verb and noun conventions.

    Tool Count4/5

    14 tools is on the higher end but reasonable given the rich domain of narrative graph management, continuity diagnostics, foreshadowing, and staged write workflows. Each tool appears to earn its place, though the count leans toward the heavy side of the ideal range.

    Completeness4/5

    The surface covers the full lifecycle well: reading (get, outline), search (find, query), graph navigation (refs, trace, neighborhood), schema introspection (graph_schema), diagnostics (check, impact), and staged writes (ingest, propose, commit). Minor gaps exist (no explicit delete/rollback tool, no direct promise mutation), but the workflow demonstrates no dead ends.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources