dead-letter
概览
作者提供的说明(英文原文)
Convert .eml and .mbox email to clean Markdown for RAG, LLM pipelines, and local knowledge bases
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查;尚未扫描代码
- 使用情况i非常新↓ 326/周 · ★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在你的电脑上运行
- 传输方式: stdio
- 分类: 搜索与 AI 记忆
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 1 项
- 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
- 注册中心没有列出需要填写的密钥。
你需要
- PyPI已安装 Python 的 uv(用于 uvx 命令)
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
链接指向作者自己的文件;我们不托管也不重新打包它。打开文件后,Claude Desktop 会进行安装。
在终端中运行这条命令
claude mcp add dead-letter -- uvx dead-letter dead-letter-mcp或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"dead-letter": {
"command": "uvx",
"args": [
"dead-letter",
"dead-letter-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"dead-letter": {
"type": "stdio",
"command": "uvx",
"args": [
"dead-letter",
"dead-letter-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 BigCactusLabs 验证,该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与“搜索与 AI 记忆”中的其他服务器比较i
- 星标数多于此分类中其他 5688 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5688 个服务器的 81% 更新
- 基础检查结果等于或优于此分类中其他 5688 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
dead-letter 安全吗?
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(0.4.10)于9天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv), MCPB, Docker。
有什么可以替代它?
同一分类中有:Context7, Codebase Memory, Exa
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.eml
Or 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
.emlcollections 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
.emlfiles into an Inbox, let dead-letter organize the Markdown bundles into a Cabinet - Install validation —
dead-letter doctorchecks 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 five slash commands (
/dead-letter:convert,/dead-letter:summarize,/dead-letter:triage,/dead-letter:cabinet,/dead-letter:mbox) - Portable Agent Skill — teaches skill-aware agents when and how to convert
.emlfiles - Python API —
from dead_letter import convertand 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.
To separate the filesystem artifacts too, bundle and Cabinet workflows write message.md plus retained decoded files under attachments/. The Markdown is ready for text ingestion, while PDFs, spreadsheets, calendar files, and other retained binary attachments stay cleanly split out for whatever downstream parser you already use.
For direct LLM integration, the MCP server lets clients call dead-letter's conversion tools without shelling out. Conversion is local; your chosen MCP host may still send returned email text to a remote model.
📊 Token-cost benchmarks
dead-letter's value isn't fewer tokens than every alternative — it's fidelity per token: keeping useful email structure without carrying raw MIME into context. Measured across an 11-message synthetic corpus of HTML threads, attachments, and newsletters (tokenizer o200k_base, structured thread mode):
- ~88% fewer tokens than the raw `.eml` in the reported aggregate comparison — the attachment category's median is ~126k tokens raw vs ~180 converted.
- Structure survives — thread structure, per-message sender attribution, links, and attachment metadata remain readable. The tested naive baselines are often cheaper because they discard information (0/2 attachment names retained vs dead-letter's 2/2).
Those counts measure the Markdown representation, not the contents of retained binary attachments or downstream answer quality. The shipping default is latest-message mode; the benchmark uses structured mode for a same-thread comparison.
The benchmark is honest about where it loses: naive extraction is fewer tokens when you don't mind throwing away metadata, links, and thread structure. Full method, the complete table (including those rows), tokenizer disclosure, and a one-command reproduce are in benchmarks/.
📦 Install
Pick one route. The distribution map explains how the channels fit together; installing all of them is not necessary.
| You want | Start here |
|---|---|
| Core CLI or Python API | Homebrew / pip below, or the uvx quick try |
| Local web UI | dead-letter[ui] below |
| Claude Desktop extension or another MCP client | MCP Server |
| Claude Code / Cowork commands | Plugin |
| Container-isolated MCP | Containers |
| Portable agent instructions | Agent Skill |
With Homebrew on Apple silicon macOS:
brew tap BigCactusLabs/tap
brew install dead-letter
The Homebrew formula installs the CLI (dead-letter convert, dead-letter doctor). Formulas for 0.4.7 and later also install the dead-letter-mcp server; the optional web UI is not included.
With pip:
pip install dead-letter # core + CLI
pip install 'dead-letter[cli]' # + watchfiles (used by backend/UI watch mode) pip install 'dead-letter[ui]' # + web UI, API server, and watch mode pip install 'dead-letter[mcp]' # + MCP server
Use pipx for an isolated UI or MCP install:
pipx install 'dead-letter[ui]' # installs dead-letter and dead-letter-ui
Or, for MCP instead:
pipx install 'dead-letter[mcp]' # installs dead-letter and dead-letter-mcp
Or run individual entrypoints without a global package install using uvx:
uvx --python 3.12 dead-letter convert message.eml
uvx --python 3.12 --from 'dead-letter[mcp]' dead-letter-mcp
uv caches tools/dependencies and may download Python on first use. These unpinned trial commands do not promise a fresh latest version on every run; see version pinning for a reviewed deployment.
From source:
git clone https://github.com/BigCactusLabs/dead-letter.git
cd dead-letter uv sync --extra dev --locked # all extras
Or choose only the surface you're developing:
uv sync --extra ui --locked # UI only uv sync --extra mcp --locked # MCP only
Agent Skill (any host)
Install the portable Agent Skill into whichever agent you use:
gh skill install BigCactusLabs/dead-letter dead-letter --agent claude-code
gh skill install BigCactusLabs/dead-letter dead-letter --agent codex gh skill install BigCactusLabs/dead-letter dead-letter --agent github-copilot
Needs gh 2.90 or newer. The skill is independent of the Claude plugin. Pin a reviewed skill tag/commit for reproducibility; the default latest release can also be a plugin release. For exact pin syntax, other hosts, manual installation, and discovery metadata, see Agent Discovery.
🚀 Quick Start
CLI — convert a single file:
dead-letter convert message.eml
Convert a whole directory:
dead-letter convert inbox/ --output out/
Generate a JSON conversion report alongside the output:
dead-letter convert inbox/ --output out/ --report
With --output, the report is written to that output directory as .dead-letter-report.json. Without --output, file conversions write the report next to the source message and directory conversions write it to the input directory root.
Check your runtime environment:
dead-letter doctor
Directory conversion scans recursively for .eml files, matches the suffix case-insensitively, skips symlinked files whose resolved targets escape the requested input tree, and deduplicates in-tree symlink aliases that resolve to the same message file.
Web UI — start the local server:
dead-letter-ui --host 127.0.0.1 --port 8765
Open http://127.0.0.1:8765 — on first launch, a setup prompt suggests default Inbox and Cabinet folders. Configure those folders before importing or starting jobs. Skipping dismisses the prompt but leaves those actions gated until setup is completed. Import .eml files with drag and drop or the file picker. Single-file imports use file mode, while multi-file drops create one directory-mode batch job. Mixed drops ask for confirmation before skipping non-.eml files.
The backend enforces a 100 MB per-file import limit for both single and batch uploads; browser batches also have aggregate-size and file-count limits.
From a source checkout, prefix with uv run:
uv run dead-letter convert message.eml
uv run --extra ui dead-letter-ui --host 127.0.0.1 --port 8765
🐍 Python API
from dead_letter import convert
result = convert("message.eml") print(result.subject, result.sender) print(result.output) # path to the generated .md
With options:
from dead_letter import convert, ConvertOptions
result = convert("message.eml", options=ConvertOptions( strip_signatures=True, strip_quoted_headers=True, ))
Strip signature images (logos, social icons) and tracking pixels:
result = convert("message.eml", options=ConvertOptions(
strip_signature_images=True, strip_tracking_pixels=True, ))
When enabled, these filters remove matched images from rendered Markdown and omit stripped inline signature/tracking assets from bundle attachment output.
Bundle conversion (Markdown + attachments + source in one directory):
from dead_letter import convert_只显示了开头部分;其余内容请在仓库中阅读