Scrivener MCP写作管理服务器

Scrivener MCP

MCP server for Scrivener: connect your novels, screenplays, and manuscripts to Claude, ChatGPT, and any AI assistant, with document management, writing analysis, content enhancement, offline semantic search, and character/plot tracking.

Start with the safe first session, then use editorial review and workflows, export presets, or the Windows guide. Compatibility evidence records actual coverage and limits.

Install · Mac App · What You Can Do · All Tools · Guides · Contributing

Scrivener MCP lets your AI assistant open, read, edit, analyze, and search your Scrivener projects directly. No exporting, no copy-pasting text back and forth. Tell it which project to open and start working.

You: Open my novel and analyze the pacing in Chapter 12.

Claude: Opens the .scriv project, reads Chapter 12, runs pacing analysis. The first half moves well, but the middle stalls — a three-page internal monologue starting at paragraph 14 kills the momentum you built in the confrontation scene. Consider cutting it to a paragraph and moving the backstory to Chapter 8.

Works with Claude Desktop, Claude Code, VS Code (Copilot/Continue), Cursor, and any MCP-compatible client. Scrivener 3 on macOS, Windows, and Linux. Listed on the official MCP Registry as io.github.writerslogic/scrivener-mcp.

Install

Mac app: Draftbridge for Scrivener, $4.99

Not a terminal person? Draftbridge for Scrivener is the ready-made Mac app. It finds your AI apps — Claude Desktop, BoltAI, Cursor, VS Code, LM Studio, Raycast, Claude Code — connects Scrivener MCP to each with one click, shows your projects, and repairs the connection after an app update. No Terminal, no Node.js, no settings files. One-time $4.99, up to 3 Macs, signed and notarized by Apple.

The server, setup tool, and Claude Desktop extension here stay free and open source. The app is closed source; the fee buys the notarized build and supports development. See the Mac install guide and FAQ. Report app problems with the mac-app label.

Free: Claude Desktop extension or command line

Prefer to do it yourself? The .mcpb extension (Claude Desktop only) and the terminal setup below do the same job for free.

From a terminal:

Otherwise, from a terminal:

npm install -g scrivener-mcp

Restart Claude Desktop and it's ready. Other clients need one more step:

npx scrivener-setup

This finds Claude Desktop, Claude Code, Cursor, VS Code, LM Studio, BoltAI, and Raycast and configures them for you, then confirms the server starts. No Node.js on your Mac? See the Mac install guide. To set up Claude Code by hand instead: claude mcp add -s user scrivener -- npx scrivener-mcp, then restart it (or run /mcp).

npx -y @smithery/cli install scrivener-mcp --client claude

npx scrivener-mcp

{
	"mcpServers": {
		"scrivener": { "command": "npx", "args": ["scrivener-mcp"] }
	}
}

npm install -g writerslogic/scrivener-mcp              # latest main
npm install -g writerslogic/scrivener-mcp#v0.12.0       # a specific release

brew install writerslogic/tap/scrivener-mcp

docker build -t scrivener-mcp https://github.com/writerslogic/scrivener-mcp.git
docker run -i --rm -v /path/to/your/projects:/projects scrivener-mcp

security add-generic-password -s anthropic-api-key -a anthropic -w sk-ant-your-key-here   # Keychain
export ANTHROPIC_API_KEY="sk-ant-..."                                                      # or export it directly

What You Can Do

Open a project first. The server has no link to the Scrivener app itself and can't see what's open there — say "Open my Scrivener project at ~/Documents/My Novel.scriv", or "Discover my Scrivener projects" if you don't know the path. On macOS, "Use the project I have open in Scrivener" works too (the first time, macOS will ask permission to control Scrivener). Do this once per conversation. If the project is also open and unsaved in Scrivener itself, save or close it there first, or the two can write over each other.

Manage your manuscript. Read chapters, create scenes, reorganize the binder, update synopses — all through conversation. "Create a new scene called 'The Reveal' after Chapter 5, and move the old epilogue to the trash."

Analyze your writing. Readability, pacing, style, dialogue quality, emotional arc — grounded in your actual prose, not generic advice. Ask whether a chapter's pacing is off and get specifics: which paragraphs stall, how the scene compares to your other chapters, filter-word density against your own average.

Enhance your prose. Targeted edits: cut filter words, strengthen verbs, vary sentence structure, add sensory detail, turn telling into showing, tighten dialogue, fix pacing.

Track characters and plot. Character profiles, plot threads, and style guides persist with the project across sessions. Save a profile for a character once; a consistency check months later catches contradictions — dialogue that doesn't sound like them, a limp that disappears for a chapter.

Search by meaning. "Find scenes where the protagonist feels isolated" works even if that word never appears, within the disclosed English story-concept vocabulary. The installed Holographic Memory System combines native BM25 with supplied local concept vectors. Results include exact passages, locations and saved revisions; changed passages are replaced incrementally. Provider interpretation and explanations are optional.

Track relationships. Query how characters, locations, themes, and plot threads connect. No Neo4j required — relationships live in the semantic memory engine and persist with the project; Neo4j adds deeper graph analysis if you have it.

Compile and export. Assemble chapters into one manuscript with your own formatting and structure preserved. Export inline as Markdown, HTML, or JSON, or write a DOCX, EPUB, or PDF to disk.

All Tools

75 tools organized by workflow. To keep token usage low, tools load progressively — project tools at startup, document and search tools once a project is open, the rest on demand. Set SCRIVENER_MCP_EAGER_TOOLS=1 to load everything up front.

Guides

• Getting Started -- Installation, configuration, your first session
• MCP Client Setup -- Copy-paste config for Claude Desktop, Claude Code, Cursor, and VS Code
• Writing with AI -- Analysis workflows, enhancement strategies, memory management
• Troubleshooting -- Common issues and fixes
• Token Optimization -- How the server minimizes context window usage
• Architecture -- How the server works, module structure, data flow
• Scrivener Compatibility -- Supported Scrivener versions, platforms, and format coverage
• Scrivener File Format -- The reverse-engineered .scriv format, what we read vs. infer, and safe-modification guidance
• Fuzzing -- Jazzer.js target and OSS-Fuzz integration details
• Contributing -- Development setup, code conventions, adding new tools

Requirements

• Node.js 22.14+ on the 22 release line, or 23.6+ (Node 24 recommended)
• Scrivener 3 project files (.scriv)
• macOS, Windows, or Linux
• Optional: Anthropic, OpenAI, or OpenRouter API key for provider-backed AI features
• Optional: Neo4j for persistence and advanced graph queries; core relationship tools work without it

Development

See the compatibility and upgrade policy for runtime checks, protocol contracts, dependency upgrades and the stable release gate.

git clone https://github.com/writerslogic/scrivener-mcp.git
cd scrivener-mcp
npm install
npm run dev          # Development mode with hot reload
npm run build        # Compile TypeScript
npm test             # Run tests
npm run typecheck    # Type checking only

Why This One?

A few Scrivener MCP servers exist. Our column describes the current server; other feature claims come from each project's own docs, published package, and advertised tools, last re-read on 2026-10-22; stars, forks, activity, and published version were refreshed

necessarily impossible through the connected AI client.

Counts and feature claims can change. Follow the linked projects for their own latest documentation. The table is generated from docs/comparison.yml — edit claims there, not here.

The alternative that isn't an MCP server

Scrivener can also Sync to External Folder, writing each document out as RTF or plain text, which any generic file-access MCP server (like @modelcontextprotocol/server-filesystem) can then read and write.

It's free and works today. What you lose is everything tied to the actual project — binder hierarchy, metadata, labels and status, snapshots, compile settings, RTF formatting — and edits land in the sync folder rather than the project itself, so a bad edit gets reconciled by Scrivener on the next sync instead of caught before it happens. Fine for occasional read-only help with prose; not if you want the structure to survive the round trip.

Contributing

We welcome contributions of all sizes. Check the issue tracker for good first issue labels, or see the contributing guide for development setup.

Areas where help is especially welcome:

• Test coverage (#18)
• Windows testing and path handling
• Scrivener 2 compatibility testing
• Documentation improvements (#25)

Security

Found a vulnerability? Please report it privately — see SECURITY.md.

License

AGPL-3.0 © WritersLogic, Inc.

Scrivener is a trademark of Literature & Latte Ltd. This project is independent and is not affiliated with, endorsed by, or sponsored by Literature & Latte.

Free for personal use and open-source projects. Commercial license available for proprietary integration. See COMMERCIAL_LICENSE.md for details.

Also from WritersLogic: WritersProof witnesses your keystrokes, pauses, and revisions as you write, then seals that process into tamper-evident, independently verifiable proof you wrote it yourself — AI accusations, settled with evidence instead of your word.

GitHub · npm · Issues · Changelog