Write your engineering book in your IDE.
Built&Written is an MCP server for writers — connect it to Cursor, Cline or Continue.dev and ask your IDE to outline, draft, revise and export your technical book or handbook.
Same MCP endpoint everywhere — no IDE-specific config.
Replacing 4 subchapters with a more concrete revision. Running in background.
- Claude.ai
- Claude Desktop
- Cursor
- Cline
- Continue.dev
- ChatGPT (OpenAI Apps)soon
Standard MCP server — connect Built&Written to any MCP-compatible AI client.
Can I write a book inside Cursor?
If you write code for a living, you probably already write longer drafts faster in Cursor than in any web app. Built&Written's MCP server lets you keep that flow — and ship to KDP at the end.
IDE-grade editing
Diff view, multi-buffer review, keybindings you already know — applied to chapter content, not source files.
Code stays in your workspace
Built&Written only sees book content. Your repos, dotfiles and snippets are never read.
Same endpoint, every client
One Streamable HTTP MCP URL works in Cursor, Cline, Continue.dev — and Claude on the side.
Two-minute setup for Cursor, Cline or Continue.dev.
Same Streamable HTTP MCP endpoint, same bearer token. Switch clients freely — the book project stays put.
Install mcp-remote (one time)
Open your terminal and run:
npm install -g mcp-remote
Requires Node.js 18+. Run node --version to check.
Create an API key
Add to claude_desktop_config.json
Open ~/AppData/Roaming/Claude/claude_desktop_config.json (Windows) or ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) and paste:
claude_desktop_config.json
{
"mcpServers": {
"builtwritten": {
"command": "mcp-remote",
"args": [
"https://mcp.builtwritten.com/mcp",
"--header",
"Authorization:Bearer bw_live_YOUR_TOKEN"
]
}
}
}Replace bw_live_YOUR_TOKEN with your actual key. Note: Authorization:Bearer has no space after the colon — this is required by mcp-remote.
Restart Claude Desktop
Windows path issue?
If Claude Desktop shows "Server disconnected" on Windows, make sure mcp-remote is installed globally ( npm install -g mcp-remote) and use "command": "mcp-remote" not "command": "npx". The npx approach fails because Node.js is installed in a path with spaces.
What the IDE can actually do.
A subset of the 30+ MCP tools — the ones Cursor users reach for first. Full list lives in /docs/mcp.
get_contentRead text for one chapter at a time.patch_subchapter_contentReplace one subchapter's text in place.start_ai_rewriteRewrite a subchapter with an action: shorten, expand, simplify, revoice.start_export_pdfGenerate a print-ready KDP-formatted PDF and return a signed URL.
We’re not for every book.
Pure fiction with heavy structure
We optimize for non-fiction, technical and business books. Multi-POV novels need a different tool.
Reference books with live code
Built&Written stores prose. If your book is 80% executable notebooks, use a Quarto / Jupyter pipeline.
Internal docs that must live in the repo
If your book is part of your codebase (Docusaurus, MDX in repo), keep it there. Use us when you want PDF / KDP / EPUB output.
Strict house style with bespoke tooling
If you already have an O'Reilly / Manning workflow, our exports aren't a drop-in. Use us pre-acquisition.
Writing a book in Cursor — answered.
Yes — Built&Written is an MCP server that Cursor can connect to. Ask Cursor in chat to read, draft or revise chapters. The book lives in your Built&Written project, not in editor buffers.
Cursor gives you IDE-grade tooling — file-level edits, multi-buffer review, diff view. Claude.ai is faster for plain-English direction. Both share the same Built&Written project.
Connect Built&Written to Cursor (or Cline / Continue.dev) as an MCP server. Outline chapters in chat, generate drafts in the background, then review and edit each subchapter directly in the IDE before exporting to KDP-ready PDF or EPUB.
Yes — Built&Written is an MCP server for writing books that works in Cursor, Cline, Continue.dev and Claude. Same endpoint, same tool surface.
No. Your code stays in your IDE workspace. Built&Written only reads and writes book content — chapters, subchapters and metadata in your account.
Currently PDF, EPUB and DOCX. DocBook export is on the roadmap. KDP-compliant trim sizes are built in.
Yes — same Streamable HTTP MCP endpoint and the same tool surface. Setup is in our docs at /docs/mcp.
Not a dedicated one. Any MCP-compatible CLI client connects to the same endpoint.
Ship your engineering book.
Free to start. Two-minute MCP setup for Cursor, Cline or Continue.dev.