技能潮 SkillTide 提交收录
官方说明7 个来源MCP 服务8 天前
BigCactusLabs/dead-letter

BigCactusLabs/dead-letter

Convert .eml exports to
在 GitHub 查看 ↗直链 · 无中转页
配置模板(请按你的客户端调整)
claude mcp add dead-letter -- npx -y dead-letter
这是根据仓库名生成的可粘贴骨架,命令行参数与包名请以该项目 README 为准。
★ 数取值
8 ★ · BigCactusLabs/dead-letter · 取自 GitHub 搜索 API · (2026-10-16 20:00:20 核对)
来源明细
收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
收录与活跃
收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 7 个来源列出
评分构成
综合分 703 · 8 ★ · 7 个来源 · mcp
常见问题(答案都来自我们的记录)
怎么安装?
我们【没有】从该仓库取到安装命令(我们的 install 覆盖率只有约 4%)。请看它的 README 或 releases 页。
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库 BigCactusLabs/dead-letter;我们收录于 2026-10-09;最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
第三方质量标记

dead-letter

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

**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:
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 .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 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 .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.
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.
来源
awesome · https://github.com/BigCactusLabs/dead-letter
按领域浏览
MCP 服务
Traction
8 ★
收录于
昨天

更多MCP 服务

查看MCP 服务全部 5,525 条 →

所属领域与标签

每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。

浏览全部领域 →

← 返回索引