dsh-novel-writer
Related Servers
Alternatives to dsh-novel-writer
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes 30+ novel-writing tools over stdio or HTTP so external agents such as Claude Code or WorkBuddy can use their own models and API keys to read chapters, write prose, manage characters, foreshadowing, story arcs and worldbuilding, run local semantic search, and launch review sub-agents. Supports one-click enabling with configurable port, token, and approval mode.AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables 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.14MIT
- AlicenseAqualityBmaintenanceEnables human-like non-fiction authoring by training custom voices, applying tone presets, auditing drafts for AI tells, and managing dictionaries, all locally.1969 npm8MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first markdown vault with a built-in MCP server (streamable HTTP). 16 tools and 2 resources for Claude Code / Desktop / Cursor: read/write/search plus context_for_query, find_orphans, weekly_digest, compare_notes, semantic_outline. Per-folder agent permissions, LanceDB vectors, local Xenova ONNX embedder swappable to Ollama. Single Bun binary. AGPL.33AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceA low-token human-AI co-reading MCP tool that imports local EPUB/TXT/Markdown books into chunks, enabling AI to read only relevant fragments and write co-reading results to long-term reading notes and progress files.73MIT
- 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
TDQS
Scored across 18 tools
The three analysis tools (novel_sentence_analysis, novel_style_check, novel_style_report) are explicitly disambiguated in their descriptions, but novel_settings, novel_outline, and novel_plot have fuzzy boundaries—both settings and outline manage character/world data, and outline's hook records overlap with plot's foreshadowing tracker. An agent could plausibly route the same request to two different tools.
All tools share a consistent novel_ prefix in snake_case, but the second part mixes conventions: bare verbs (novel_read, novel_import), bare nouns (novel_books, novel_plot), noun+verb compounds (novel_style_check, novel_continuity_check), and noun+noun compounds (novel_sentence_analysis, novel_style_report). The prefix keeps it readable, but the pattern is not predictable enough to guess tool names.
18 tools is at the heavy end, but the server's scope is genuinely broad: reading, writing, importing, editorial analysis, style checking, revision planning, plot tracking, settings, summaries, continuity auditing, and semantic search. Each tool has a distinct job, though the analysis triad plus fix_plan could arguably be consolidated without much loss.
Reading, creating, analysis, and management surfaces are well covered, but there are notable gaps: no way to update or delete a chapter after creation, no book-level delete/rename, and novel_fix_plan explicitly refrains from generating text, leaving no tool that actually applies revisions to the manuscript. Settings and summaries have full CRUD, but the core chapter lifecycle is incomplete.