Your story.
Your files.

Heinlein works with manuscripts stored as files you can open and understand. Here’s the shape of the work.

Start with Markdown

Your writing lives in ordinary Markdown files. You can work with a standalone draft or open a folder containing your project.

Organize a manuscript

For supported manuscript projects, a manifest describes the order and identity of scenes. Scenes remain editable source files; a chapter reading view can bring their text together in order.

PROJECT FOLDER
↳ Manuscript manifest: structure and order
↳ Scene files: your Markdown writing
↳ Assembled reading views and publishing output

Make editions

The publishing pipeline uses manuscript source and project configuration to build formats including PDF, EPUB, DOCX, HTML, and text. The outputs are publishing copies; the source remains your working material.

Your agents, in your draft, without mutation.

Connect an MCP-compatible agent to selected manuscript scenes. Heinlein’s local MCP connection can give it read-only access to your saved writing, so you can discuss the work with the context it needs.

With proposals enabled, an agent can offer a suggested change for your review in Studio. The MCP connection cannot save or apply that change to your manuscript. You decide whether to apply it.

The connection reads saved files, not unsaved editor text. Your chosen agent may have its own data and privacy policies, and other tools it can use have their own permissions.

Choose when to share

Editing and saving locally do not send your writing to an AI provider. Optional assistance and connected sharing involve separate actions you choose.