Generating chapter text is the easy part; wiring SUMMARY.md so the chapters actually appear in the book is the part people abandon, and it is automated here. On the Notion side, the setup step to note is the page named `Jot It Down` — the integration needs it to exist and to be shared before anything writes.
A Rust MCP server with two publishing targets. One writes pages into Notion through your integration; the other assembles structured content into an mdBook, handling the files that make the book navigable.
- A Notion tool that creates a new page or updates an existing one with generated content
- An mdbook tool that generates a book from content — creating chapter markdown files, README.md and the SUMMARY.md that links them
- Chapters are linked in SUMMARY.md automatically, so the book's navigation is not left as manual work
- Both targets take content produced in the conversation rather than requiring an intermediate file
Rust, with the server built by `cargo build --release` and the client pointed at the resulting binary. Book generation additionally needs the mdbook CLI, installed with `cargo install mdbook`. For Notion you need an internal integration secret in NOTION_TOKEN, and a page titled `Jot It Down` shared with that integration — the integration will not work without it.