JotDown

Jotdown is an MCP server that enables large language models to work with Notion pages and to generate mdbooks. It exposes two main tools: a Notion Page Tool for creating or updating Notion pages with LLM-generated content, and an mdbook Tool for producing structured markdown books, including chapters and navigation files like SUMMARY.md. This setup allows LLMs to manage content in Notion alongside publishing and organizing markdown books for documentation or knowledge bases. You can invoke the Notion tool to create or modify pages directly in your Notion workspace, and you can use the mdbook tool to assemble a complete book from generated content, complete with chapter organization and navigational structure.

Prerequisites:\n- Rust toolchain installed (Rust and Cargo). Install from https://www.rust-lang.org/.\n- Notion API token (internal integration secret) with access to your Notion workspace.\n- Claude Desktop or any MCP client configured with a Notion integration token.\n\nSteps to install:\n1. Clone the repository and build the binary:\nbash\ngit clone https://github.com/Harry-027/JotDown\ncd jotdown\ncargo build --release\n\n2. Install mdbook (required for mdbook generation):\nbash\ncargo install mdbook\n\n3. Notion setup:\n- Create and share an internal Notion integration with your workspace. Copy the internal integration secret (NOTION_TOKEN).\n- Create a page in Notion (e.g., titled Jot It Down) and ensure the integration has access.\n4. Configure the MCP client (Claude Desktop or other) to point to the built binary and provide environment variables:\njson\n"mcpServers": {\n "Jotdown": {\n "command": "/path_to_repo/Jotdown/target/release/Jotdown",\n "args": [],\n "env": {\n "NOTION_TOKEN": "your_notion_integration_token"\n }\n }\n}\n\n5. Restart your MCP client and run Jotdown via the configured server entrypoint.

Tips and common issues:\n- Ensure the NOTION_TOKEN has access to the required Notion workspace and pages.\n- The mdbook generation relies on cargo installing mdbook; if you encounter path or permission errors, confirm cargo bin directory is in your PATH.\n- If the Notion integration fails, verify the integration is shared with the specific page or workspace and that the Notion API token is current.\n- When upgrading Rust or dependencies, re-build with cargo build --release to produce an updated binary.\n- For debugging, run the binary directly and inspect console logs for Notion API errors or mdbook generation messages.