Why Cursor, of all things
The tool built to hold a whole codebase can hold a whole book
Cursor was designed to keep large projects in context. A novel is just another big project.
Cursor is an AI code editor — and that’s exactly why it’s a surprisingly great place to write a book. It was built to reason over large, structured projects and to call external tools through MCP. Swap “codebase” for “manuscript” and the same strengths apply: structure, context, and tool use.
On its own, though, Cursor still leans on the model’s memory, and a long book will drift the same way it does anywhere else. The fix is the same: give it real project state.
Add BookWriter’s MCP server and Cursor gets a server-side book bible and a chapter-by-chapter writing loop. You write in a clean editor with your files beside you, and the book actually finishes.