Jotdown - MCP Server for Notion Page Creation and mdBook Generation

Created By
Harry-027a year ago
An MCP Server in Rust for creating Notion pages & mdBooks with LLMs 🦀
Overview

what is Jotdown?

Jotdown is a Model Context Protocol (MCP) server that allows large language models (LLMs) to interact with Notion and generate Markdown Books (mdbooks). It facilitates content management and publishing workflows by integrating with these systems.

how to use Jotdown?

To use Jotdown, install the necessary dependencies, set up your Notion API token, and configure your MCP client. You can then create or update Notion pages and generate mdbooks using LLMs.

key features of Jotdown?

  • Notion Integration: Automatically create or update Notion pages with LLM-generated content.
  • Mdbook Generation: Create and manage mdbooks directly from content, including generating necessary markdown files.
  • MCP Support: Maintains context over interactions for intelligent content creation.

use cases of Jotdown?

  1. Creating structured articles or documents in Notion.
  2. Generating comprehensive markdown books from LLM-generated content.
  3. Managing content updates in Notion seamlessly.

FAQ from Jotdown?

  • Can Jotdown integrate with any LLM?

Yes! Jotdown is designed to work with any LLM that supports MCP.

  • Is Jotdown free to use?

Yes! Jotdown is open-source and free to use.

  • What are the prerequisites for using Jotdown?

You need Rust installed, a Notion API token, and an MCP client like Claude.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Harry-027
Star
11
Language
Rust
License
MIT license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago