story-architect-mcp
Related Servers
Alternatives to story-architect-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA MCP server that acts as a structural secretary for novel writing, enabling project management, scene checklists, foreshadowing tracking, draw.io import, progress suggestions, and Task Master PRD export.21MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server providing 67 tools for AI-assisted storywriting, world-building, character development, screenplay generation in industry formats (Fountain, FDX, PDF), storyboards, and production analytics.-
- 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.15MIT
- 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 gradedqualityFmaintenanceA Model Context Protocol server that manages character knowledge and relationships for creative writing projects, offering semantic search and AI-powered analysis.4MIT
- AlicenseAqualityBmaintenanceMCP server that analyzes your writing style to generate personal voice rules, scores drafts for AI slop, and verifies authorship, enabling LLMs to write in your specific voice.7MIT
TDQS
Scored across 32 tools
Most tools have distinct purposes, but several analysis tools overlap heavily: story_analyze_voice, story_analyze_sentiment, and story_track_emotion all deal with tone/emotion, while story_scan_messy_project, story_auto_refactor_structure, and the layout brief/verdict pair require careful reading to choose correctly. The descriptions help, but an agent can still misselect among these clusters.
Nearly all tools use the story_ prefix with snake_case and a verb_noun pattern (e.g., story_write_chapter, story_log_plot_hole, story_analyze_pacing). Minor deviations like story_init, story_export, story_stats, and story_snapshot are still readable and do not break the convention.
With 32 tools, the surface is heavy for a single MCP server and exceeds the typical well-scoped range of roughly 3-15 tools. Several specialized analysis and layout tools could likely be consolidated without losing core capability.
The server covers project setup, chapter writing/reading, continuity tracking, analysis, export, and snapshot rollback, which is a broad lifecycle for novel architecture. There are minor gaps such as no explicit outline/bible CRUD tools and no dedicated list-open-plot-holes operation, but agents can work around most of these via existing tools.