send-to-kindle-mcp
Allows sending document files to a Kindle device via Amazon's Send to Kindle email feature.
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., "@send-to-kindle-mcp send /home/user/book.epub to my Kindle"
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.
send-to-kindle-mcp
An MCP server that sends document files
(EPUB, PDF, TXT, …) to your Kindle using Amazon's Send to Kindle email
feature. The file is emailed as an attachment to your device's @kindle.com
address.
Tool
send_to_kindle
Argument | Type | Required | Description |
| string[] | yes | Absolute paths of the document files to send (1–25 files). |
| string | no | Target |
All files are sent as attachments in a single email. Amazon's limits: up to 25 attachments and 50 MB combined per email.
Supported formats: .epub, .pdf, .txt, .rtf, .htm, .html, .png,
.gif, .jpg, .jpeg, .bmp.
Related MCP server: AWS SES MCP Server
Prerequisites (do this once on Amazon's side)
Send to Kindle by email silently drops anything from an unapproved sender.
Find your Kindle address. Amazon → Manage Your Content and Devices → Devices → select your Kindle. It shows an address like
you_abc123@kindle.com.Approve your sending email. Same page → Preferences → Personal Document Settings → Approved Personal Document E-mail List → Add a new approved e-mail address. Add the address you'll send from (your
SMTP_FROM/SMTP_USER).
EPUB is supported natively (Amazon converts it to a Kindle format on receipt).
Install
No clone or build needed — the server runs via npx straight from npm:
npx @benbini/send-to-kindle-mcp(Your MCP client launches it for you using the config below; you don't normally run this by hand.)
Gmail note
Use an App Password, not your account password: Google Account → Security →
2-Step Verification → App passwords. Host smtp.gmail.com, port 587.
Register with an MCP client
Claude Code
claude mcp add send-to-kindle \
--env SMTP_HOST=smtp.gmail.com \
--env SMTP_PORT=587 \
--env SMTP_USER=you@gmail.com \
--env SMTP_PASS=your-app-password \
--env SMTP_FROM=you@gmail.com \
--env KINDLE_EMAIL=you_abc123@kindle.com \
-- npx -y @benbini/send-to-kindle-mcpGeneric mcpServers JSON (Claude Desktop, Cursor, etc.)
{
"mcpServers": {
"send-to-kindle": {
"command": "npx",
"args": ["-y", "@benbini/send-to-kindle-mcp"],
"env": {
"SMTP_HOST": "smtp.gmail.com",
"SMTP_PORT": "587",
"SMTP_USER": "you@gmail.com",
"SMTP_PASS": "your-app-password",
"SMTP_FROM": "you@gmail.com",
"KINDLE_EMAIL": "you_abc123@kindle.com"
}
}
}
}From source (development)
git clone https://github.com/BenjaminBini/send-to-kindle-mcp.git
cd send-to-kindle-mcp
npm install
npm run buildThen point your client's command/args at node /path/to/dist/index.js.
Environment variables
Variable | Required | Default | Notes |
| yes | — | SMTP server hostname. |
| no |
| SMTP port. |
| no |
| Force TLS-on-connect. |
| yes | — | SMTP username. |
| yes | — | SMTP password / app password. |
| no |
| From address; must be Amazon-approved. |
| no | — | Default target if the tool arg is omitted. |
Troubleshooting
Nothing arrives. Almost always the sender isn't on the approved list, or the Kindle address is wrong. Delivery can take a few minutes.
SMTP auth fails. For Gmail/Outlook you need an app password with 2FA on.
File rejected. Check every file is a supported format, that there are at most 25 of them, and that their combined size is under 50 MB.
Available Tools
1 toolsend_to_kindleA
Send a local document file (EPUB, PDF, DOCX, etc.) to a Kindle device via Amazon's Send-to-Kindle email feature. The file is emailed as an attachment to the Kindle address. NOTE: the sending email address must be on your Amazon 'Approved Personal Document E-mail List' or Amazon will silently drop the email.
Inputs: file_path (required), convert, kindle_email.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no risk of confusion between tools. The single tool's purpose is clearly distinct by default.
The single tool uses a clear, descriptive snake_case name (send_to_kindle), which is consistent with common MCP naming conventions.
A single tool is minimal but appropriate for a focused utility that performs one specific action (sending documents to Kindle). More tools could be added for auxiliary features, but the current count is reasonable.
The tool covers the core functionality of sending documents to Kindle. While it lacks additional features like managing approved senders or checking delivery status, these are not essential for the primary use case.
Related MCP Connectors
Send emails from natural language prompts. Hosted at https://cloudish.ai.
Send, track, and manage transactional and bulk email delivery
Send documents for e-signature, track signing status, and download signed PDFs. No API key required.
Send transactional email over a verified domain — templates, attachments, custom headers.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that allows Claude Desktop to send documents directly to your Kindle e-reader.2MIT
- AlicenseBqualityBmaintenanceSends emails using AWS Simple Email Service (SES) with support for HTML/plain text, CC, and BCC from any MCP client.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables sending Markdown or EPUB content to a Kindle device via MCP. Users can send documents to their Kindle directly from Claude or any MCP client.-
- FlicenseNot gradedqualityDmaintenanceConverts large comic archives (CBZ/CBR) into Kindle-optimized EPUB volumes with GPU acceleration, smart chunking under Amazon's 200MB limit, and device-specific profiles for manga/comics.-