kindle-mcp
Provides tools for creating structured book summary pages in Notion from Kindle highlights, including personal thesis, core themes, key ideas, actionable takeaways, reflection questions, and memory capsules. Automatically manages a 'Kindle Book Summaries' database and supports first-run database initialization.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@kindle-mcp turn these Kindle highlights into a Notion summary"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
kindle-mcp
An MCP (Model Context Protocol) server that turns your Kindle highlights into structured personal book memory summaries saved directly to Notion.
Zero external AI API calls. All reasoning is performed by the host model (Claude Desktop) in its own context window. The server parses files, builds prompts, and writes to Notion — nothing else.
What it does
You share a Kindle highlight export file in Claude Desktop
Claude parses your highlights, generates a personal memory summary, and saves it to your Notion database
You get back a Notion page URL — nothing else shown in chat
All automatic. No copy-pasting. No manual steps.
Related MCP server: Medium MCP Server
Requirements
Notion account
Node.js 18+ installed
Notion MCP server running alongside this one (for first-run auto-setup)
Installation
1. Get a Notion API key
Click New integration → give it a name → click Submit
Copy the Internal Integration Secret (starts with
secret_...)
2. Add to Claude Desktop config
Open your Claude Desktop config file:
Mac:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add the following inside "mcpServers":
"kindle-mcp": {
"command": "npx",
"args": ["-y", "kindle-mcp"],
"env": {
"NOTION_API_KEY": "secret_..."
}
}3. Restart Claude Desktop
Fully quit (Cmd+Q on Mac) and reopen. You should see the tools available via the hammer icon in the chat input.
First-time use
On first run, the server needs a Notion page to create the Kindle Book Summaries database under. If you also have the Notion MCP running, this happens automatically — Claude will create the page and database without asking you anything.
If you don't have the Notion MCP, create any page in Notion and connect your integration to it first:
Open a Notion page → click
...top right → Connections → select your integration
After the first run, the database ID is saved locally at ~/.kindle-mcp/config.json and never needs to be set up again.
Usage
In Claude Desktop:
Attach your Kindle export file (
.htmlfrom the Kindle app, orMy Clippings.txtfrom a Kindle device)Say: "Use the process_kindle_export tool on this file"
Claude processes everything and returns your Notion page URL
Supported Kindle export formats
Format | How to get it |
HTML | Kindle app (iOS/Android/Mac) → open book → Notes → Export |
Plain text |
|
Both formats are auto-detected — no configuration needed.
Summary output structure
Each book gets a Notion page with:
Field | Description |
| One sentence capturing the core insight from your highlights |
| 3–5 recurring themes |
| 5–8 distinct ideas drawn from your highlights |
| 3–5 concrete actions implied by your highlights |
| 3–5 questions your highlights raise |
| A 3–4 sentence personal narrative distilling everything |
Summaries are generated only from your highlights — the model uses no external knowledge about the book.
Tools
Tool | Description |
| Primary tool. Parses a Kindle file and orchestrates the full flow |
| Creates the Notion database on first run (called automatically) |
| Pushes a generated summary to Notion as a structured page |
| Parses a Kindle file and returns raw highlights grouped by book |
| Builds a prompt package for the host model to generate a summary |
Notion database schema
The Kindle Book Summaries database is created automatically with:
Property | Type |
| Title |
| Rich Text |
| Rich Text |
All summary content (thesis, themes, ideas, etc.) is written as page body blocks.
License
MIT
Available Tools
5 toolsgenerate_personal_summaryA
Builds a prompt package for the host model to generate a personal book memory summary from highlights alone. Use this when processing a single book manually.
Inputs: title (required), author (required), highlights (required).
initialize_notion_databaseA
Creates the Kindle Book Summaries database in Notion under a given parent page. Call this automatically when process_kindle_export returns status='setup_required', using the page ID created by the Notion MCP tool.
Inputs: parentPageId (required).
parse_kindle_clippingsA
Parse a Kindle HTML export or My Clippings.txt and return highlights grouped by book. Use this when you only need the raw highlights without generating summaries.
Inputs: rawText (required).
process_kindle_exportA
PRIMARY TOOL. Given the raw content of a Kindle HTML export or My Clippings.txt file, parses all highlights and returns prompt packages plus explicit instructions. After calling this tool, you MUST follow the returned instructions exactly: generate each summary internally then immediately call push_to_notion for each book. Do not display summaries in chat — only report the Notion page URLs.
Inputs: rawText (required).
push_to_notionA
Push a generated book summary to a Notion database as a structured page. Call this once per book after generating each summary.
Inputs: notionDatabaseId (required), summary (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Tools have distinct purposes clearly marked in descriptions (e.g., 'PRIMARY TOOL', 'Use this when...'), though `parse_kindle_clippings` and `process_kindle_export` both parse exports, and `generate_personal_summary` overlaps with the internal generation step of the primary workflow.
Excellent consistency: all five tools use snake_case with imperative verb_noun structure (generate_, initialize_, parse_, process_, push_). The pattern is predictable and readable throughout.
Five tools is ideal for this focused scope: parsing (2 variants), summary generation, Notion database setup, and Notion publishing. Each tool earns its place without bloat.
Covers the full Kindle-to-Notion lifecycle including setup, parsing, generation, and publishing. Minor gap: no update or delete operations for existing Notion entries, requiring agents to only create new summaries.
Maintenance
Related MCP Connectors
YouTube transcripts (chunks, phrase search, most replayed moments), PDFs and web pages as Markdown.
Turn books in your private library into tables of contents, summaries and study docs.
Highlight anything you read. Then ask your AI about it: search, read and edit your highlights.
Long-term memory for Claude, ChatGPT, Cursor: search, save and organize notes, links, docs, videos.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAutomatically extracts and indexes knowledge from AI sessions and files using local LLMs, enabling semantic search and memory management.17 npmMIT
- FlicenseNot gradedqualityDmaintenanceTransforms a Medium article archive into an intelligent writing assistant for book writing, enabling content analysis, theme extraction, and chapter organization.1-
- AlicenseNot gradedqualityDmaintenanceEnables deep structural analysis of ebooks by extracting core conflicts, insights, mental models, and actionable items from PDF, Markdown, or text files.ISC
- AlicenseNot gradedqualityDmaintenanceConverts study materials like PDFs, slides, and DOCX into a searchable vector database with semantic search, summarization, and flashcard generation, integrated with Notion.5MIT