dead-letter MCP server
io.github.BigCactusLabs/dead-letter·v0.4.10·8 starsConvert .eml and .mbox email to clean Markdown for RAG, LLM pipelines, and local knowledge bases
not scanned yet
8 stars
Reviews
Write oneNobody has reviewed dead-letter yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
dead-letter tools
No tool declarations could be read from the package source. They show once the server is installed.
How dead-letter compares
Against every graded Email MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 90% of 916 Email servers
- GitHub stars
- 8
- more than 86% of 493 Email servers
Release history: 7 versions in the registry since 2026-08-21, latest 2026-10-29, typically one every 10 days.
Install dead-letter in Claude Code, Cursor or VS Code
claude mcp add dead-letter -- uvx dead-letter
What the publisher says
From the dead-letter repository's README, as published. We do not edit it. Read it on GitHub
<!-- mcp-name: io.github.BigCactusLabs/dead-letter -->
dead-letter
Turn .eml email exports into clean, local, LLM-ready Markdown.
dead-letter converts .eml email exports into clean Markdown with YAML front matter — threads split, signatures stripped, attachments extracted, calendars parsed. One file or ten thousand.
Use it to build a readable email archive, move messages into Markdown-based knowledge systems, or prepare email for RAG and LLM pipelines without feeding raw MIME and base64 into your context window. No account, upload, or API key required.
⚡ Try it
If you already have uv, run dead-letter without installing it globally:
uvx --python 3.12 dead-letter convert message.emlOr install with Homebrew or pip below. Agents and MCP clients can use the client-specific setup in llms-install.md.
🎯 Common use cases
- Email → Markdown archives — turn exported .eml collections into readable, portable Markdown with structured metadata
- RAG and LLM ingestion — normalize message text, thread structure, links, and attachment metadata before chunking or indexing
- Agent workflows — expose conversion and diagnostics directly to Claude, Codex, and other MCP clients
- Knowledge bases — move email into Markdown-first systems such as Obsidian, static archives, or local search pipelines
- Digital preservation — retain human-readable content and useful message structure without depending on one mail client
✨ Features
- Full-fidelity conversion — HTML sanitization, Gmail/Outlook thread segmentation, inline image handling, and calendar event summaries
- CLI — point it at a file or a directory and go
- Local web UI — dark command-center interface with drag-and-drop import, watch mode, conversion grade badges, processing history, and per-job diagnostics
- Inbox/Cabinet workflow — drop .eml files into an Inbox, let dead-letter organize the Markdown bundles into a Cabinet
- Install validation — dead-letter doctor checks your runtime environment
- Conversion report — opt-in JSON report with per-file diagnostics, including attachment referenced/retained counts for automation and audit
- MCP server — integrate with Claude Desktop, Claude Code, Codex, and other MCP clients
- Claude plugin — marketplace install in Claude Code or Cowork with four slash commands (/dead-letter:convert, /dead-letter:summarize, /dead-letter:triage, /dead-letter:cabinet)
- Portable Agent Skill — teaches skill-aware agents when and how to convert .eml files
- Python API — from dead_letter import convert and you're off
🧠 Built for LLM Pipelines
Raw .eml files are noisy input for downstream LLM and retrieval pipelines — MIME headers, multipart boundaries, duplicated HTML/plain bodies, and encoded attachments all get mixed into the text path.
dead-letter normalizes that into Markdown with YAML front matter, so message text and metadata are ready for chunking or indexing without MIME parsing or base64 cleanup. Default convert() and convert_dir() runs write a single .md per message and keep attachment names in front matter.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
dead-letter: common questions
- Is dead-letter MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the dead-letter safety report
- How do I install dead-letter?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does dead-letter need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is dead-letter maintained?
- The last commit was 32 days ago (2026-10-02). The latest release is v0.4.10.
- What can I use instead of dead-letter?
- Servers from other publishers that do the same job: Sendsoon MCP server, emailmd MCP server and Mailoo - Email MCP Server.
- How does dead-letter compare with other Email MCP servers?
- safety score 92/100 (higher than 90% of 916 Email servers); github stars 8 (more than 86% of 493 Email servers). Full comparison.
Alternatives to dead-letter
Same job from other publishers: the closest match first, then the best rated.
- SendsoonSend email, look up public IP information, and convert files to Markdown through SendSoon.not reviewedGrowingB
- emailmdRender markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.not reviewedEstablishedA
- Mailoo - Email MCP ServerEmail MCP server for AI agents: IMAP/SMTP, Gmail, Outlook, calendar, ManageSieve, AI triage, OAuth2.5.0(1)GrowingA
- OpenOSINTAI-powered OSINT agent & MCP server. 21 tools: email, breach, IP, WHOIS, DNS, Shodan, GitHub & more.not reviewedEstablishedC
Inbox ZeroSearch Gmail and Outlook, save drafts, manage email rules, and view email stats.not reviewedEstablishedA