Storywright MCP
A multi-agent book-writing MCP server that manages a guarded chapter pipeline (writer → editor → third-pass agents → approve) with project planning, continuity tracking, and export/diff helpers.
README
Storywright MCP
Multi-agent book-writing MCP server for Cursor, Claude Desktop, OpenCode, or any host that speaks MCP over stdio. It combines a guarded chapter pipeline (writer → editor → configurable third passes → approve), JSON/Markdown projects on disk, book-bible planning, continuity tracking, manuscript search, marker scans, prior-chapter context budgeting, and export/diff helpers.
Golden path (first hour)
-
Install (from this repo):
cd C:\Apps\claude_plugins\storywright-mcp uv sync --extra dev -
Set API key (User env or MCP
envblock):ANTHROPIC_API_KEYand/orANTHROPIC_AUTH_TOKEN— required for writer/editor/third-pass (MiniMax usually uses Bearer +ANTHROPIC_BASE_URL).
-
Register MCP in Cursor — create or edit
mcp.json:Scope Path (Windows) User (all workspaces) %USERPROFILE%\.cursor\mcp.jsonThis repo only <repo>\.cursor\mcp.jsonMerge
storywrightinto the existing"mcpServers"object if the file already has other servers.Anthropic API key (secrets via Windows env — set User env vars, then reference them):
{ "mcpServers": { "storywright": { "command": "uv", "args": ["run", "--directory", "C:/Apps/claude_plugins/storywright-mcp", "storywright-mcp"], "env": { "ANTHROPIC_API_KEY": "${env:ANTHROPIC_API_KEY}", "STORYWRIGHT_PROJECTS_ROOT": "C:/Users/you/Documents/writing", "STORYWRIGHT_ANTHROPIC_MODEL": "claude-sonnet-4-20250514" } } } }MiniMax (same as your working shell — Bearer + base URL + model):
{ "mcpServers": { "storywright": { "command": "uv", "args": ["run", "--directory", "C:/Apps/claude_plugins/storywright-mcp", "storywright-mcp"], "env": { "ANTHROPIC_BASE_URL": "https://api.minimax.io/anthropic", "ANTHROPIC_AUTH_TOKEN": "${env:ANTHROPIC_AUTH_TOKEN}", "STORYWRIGHT_ANTHROPIC_MODEL": "MiniMax-M2.7", "STORYWRIGHT_PROJECTS_ROOT": "C:/Users/you/Documents/writing" } } } }Set
ANTHROPIC_AUTH_TOKENin Windows Environment Variables (User), or temporarily embed the value only if you accept the risk of it sitting on disk. EditSTORYWRIGHT_PROJECTS_ROOTto wherever you wantbook_projects/to live.Reload MCP: Command Palette → “Cursor: Reload MCP Servers” (or restart Cursor).
uvmust be onPATHfor the terminal where Cursor spawns servers. -
In chat, run tools in order:
check_environment— confirms key + model + version.create_book_project(project_name="my-novel", book_title="My Novel", third_agents=["comedy","pacing"])plan_book()… through phases (optional), or skip to chapters.add_chapter/add_characteras needed.get_pipeline_status— shows exact next tool per chapter.- Per chapter:
start_chapter→run_writer_agent→run_editor_review→ eachrun_third_agent→approve_chapter.
-
Artifacts to know:
briefs/revision_queue.json— notes fromrequest_revision(writer prompt reads these).reports/chapter-NN-editor-meta.json— parsed verdict + meta block from editor.manuscript/chapter-NN-draft.prev.md— backup before each writer overwrite; usediff_chapter.EXPORT-manuscript.md— optional output fromexport_manuscript.
Features
- Strict workflow: Third-pass only after editor; approve requires all configured third-pass agents unless
force=true. - Pipeline hints:
get_pipeline_statuslists the next tool call per chapter. - API readiness:
check_environmentvalidates Anthropic credentials (ANTHROPIC_API_KEYand/orANTHROPIC_AUTH_TOKEN) before you burn a session. - Prior prose budget: Writer includes recent approved chapter text up to configurable word/chapter limits (saves context vs dumping the whole book).
- Retries: Transient Anthropic errors (429/5xx, timeouts) retry with backoff (
STORYWRIGHT_ANTHROPIC_MAX_RETRIES). - Structured editor meta: Editor reports should end with
---STORYWRIGHT_META_START---…END---; parsed JSON beside the markdown report. - Export / diff:
export_manuscript,diff_chapter(draft vs.prev.md). - Resources:
storywright://project/*,storywright://meta/version.
Install
cd storywright-mcp
uv sync --extra dev
Environment
| Variable | Purpose |
|---|---|
ANTHROPIC_API_KEY |
Optional if using Bearer below — writer/editor/third-pass calls |
ANTHROPIC_AUTH_TOKEN |
Optional — Bearer token (same pattern as Claude Code; MiniMax often uses this instead of API_KEY) |
ANTHROPIC_BASE_URL |
Optional — e.g. https://api.minimax.io/anthropic for MiniMax’s Anthropic-compatible API |
STORYWRIGHT_ANTHROPIC_MODEL |
Model id (e.g. MiniMax-M2.7 when using MiniMax) |
STORYWRIGHT_PROJECTS_ROOT |
Parent directory; projects go to {root}/book_projects/<slug>/ |
STORYWRIGHT_STATE_DIR |
last_project.json for load_last_book_project (default ~/.storywright) |
STORYWRIGHT_PRIOR_CHAPTERS_MAX_WORDS |
Max words of prior approved prose injected into writer (~default 12000) |
STORYWRIGHT_PRIOR_CHAPTERS_MAX_COUNT |
Max number of prior chapters considered (~default 8) |
STORYWRIGHT_ANTHROPIC_MAX_RETRIES |
Retries for transient API failures (~default 2) |
STORYWRIGHT_ANTHROPIC_RETRY_DELAY_SECONDS |
Base delay between retries (~default 2.0) |
MiniMax (Anthropic-compatible gateway)
Storywright uses the official anthropic Python SDK, which reads ANTHROPIC_BASE_URL and ANTHROPIC_AUTH_TOKEN the same way as Claude Code. Mirror your ~/.claude/settings.json env into the Storywright MCP env block in Cursor (or shell), for example:
ANTHROPIC_BASE_URL=https://api.minimax.io/anthropicANTHROPIC_AUTH_TOKEN= your MiniMax token (Bearer)STORYWRIGHT_ANTHROPIC_MODEL=MiniMax-M2.7(or whatever model id your provider expects)
Do not commit API keys; prefer OS env or Cursor secrets.
Run (stdio)
uv run storywright-mcp
uv run python -m storywright_mcp
Claude Desktop / OpenCode
Use the same command / args as Cursor if your app supports MCP stdio servers.
Typical workflow
create_book_project(..., third_agents=[...])orload_book_project("C:/absolute/.../book_projects/my-book")plan_book()… (optional)start_chapter(1)→run_writer_agent(1)→run_editor_review(1)→run_third_agent(1, …)→approve_chapter(1)
Use get_pipeline_status whenever you lose track.
CLI
uv run storywright-mcp agents # list third-pass agents
uv run storywright-mcp smoke # ping Anthropic/MiniMax (tiny token use)
uv run storywright-mcp smoke --with-book # temp folder + new project + chapter 1 writer (full pipeline chunk)
Names like run_editor_review(1) are MCP tools (used from Cursor/chat), not shell commands. From PowerShell you can call the same logic after load_book_project:
uv run python -c "from storywright_mcp import workflow; workflow.load_book_project(r'C:/path/to/book_projects/your-book'); print(workflow.run_editor_review(1))"
Test MiniMax (or any Anthropic-compatible proxy)
From PowerShell, set the same variables as in ~/.claude/settings.json, then run smoke from the repo (credentials stay in your shell only):
$env:ANTHROPIC_BASE_URL = "https://api.minimax.io/anthropic"
$env:ANTHROPIC_AUTH_TOKEN = "<your-token>"
$env:STORYWRIGHT_ANTHROPIC_MODEL = "MiniMax-M2.7"
cd C:\Apps\claude_plugins\storywright-mcp
uv run storywright-mcp smoke
If you see STORYWRIGHT_SMOKE_OK in the output, routing and auth work. Use smoke --with-book to confirm create_book_project → run_writer_agent against live inference (costs more tokens; files land under a temp storywright-smoke-* directory).
CI
GitHub Actions runs ruff + pytest on push/PR (.github/workflows/ci.yml).
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。