Skip to main content
Glama

Related Servers

Alternatives to long-novel-agent-kit

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to maintain persistent project context locally, with source-backed memory and structured handoffs for seamless handover between interchangeable agents.
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI hosts to plan, draft, and check long-form novel chapters while honoring canon settings, character state, arcs, and check ordering, with approval-gated atomic commits. It keeps world, character, and chapter files as the human-editable source of truth, with snapshots and rollback for recovery.
      27
      148 npm
      Apache 2.0
    • 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.
      14
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI tools to collaboratively write novels by managing chapters, characters, and story state through commands like validate, context, draft, review, and approve.
      8
      MIT

    TDQS

    C2.9/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools have distinct purposes, but some overlap exists (e.g., build_agent_activity_report vs list_agent_activity, build_chapter_context vs build_chapter_context_brief). Descriptions help clarify, but agents may still confuse similar-sounding tools.

    Naming Consistency3/5

    Tools use a mix of verb prefixes (build_, check_, diff_, list_, get_, etc.) without a single consistent pattern. While each subgroup is internally consistent, the overall naming lacks predictability.

    Tool Count3/5

    31 tools is on the high side for a single server, but the domain (novel writing agent with chapter management, proposals, handoffs) is complex enough to justify the count. Some tools might be merged.

    Completeness4/5

    The tool set covers the core workflow: chapter readiness, proposal management, handoffs, diagnostics, and pre-write sessions. Minor gaps exist (e.g., no direct tool for writing content, but that is delegated to the agent via prompts).

    Maintenance

    ActivityInactive
    ResponsivenessNo issues