mbox-mcp is by arose26 — not by us.
We indexed this project so people can find it. We are not selling it, we host no copy of the code, and we are not affiliated with or endorsed by its authors — get it from them.
Indexed Sep 28, 2026 · 0 stars at index time. Maintainers: claiming verifies your identity and unlocks a higher assurance tier. Removal requests are honored.
MCP server · for humans & their agents
mbox-mcp
unclaimed listingactively maintainedFreeMIT
mbox-mcp, an open-source project.
by Open Source Community · New publisher
mbox-mcp, an open-source project.
arose26/mbox-mcp is an open-source project by arose26. Indexed here so it can be found — not resold.
It is free. Get it from the upstream repository: https://github.com/arose26/mbox-mcp
From the project's own README (excerpt, reproduced for discovery under its MIT license):
mbox-mcp
An MCP server for local email archives. Point it at a Google Takeout .mbox export or a folder of .eml files and ask Claude things like: • "Who did I email most in this archive?" • "Find the message where the landlord mentioned the lease renewal." • "Summarize my correspondence with bob@example.com from early 2026."
Everything stays on your machine. No OAuth, no app passwords, no IMAP connection, no cloud. Every other email MCP server connects to a live account — this one reads the archive files you already have, which is exactly what you want for the 15 years of Gmail sitting in a Takeout export.
Quick start
Claude Code
Claude Desktop — add to claudedesktopconfig.json:
Then: "Open C:\\Takeout\\Mail\\All mail Including Spam and Trash.mbox and tell me about it."
Tools
Tool What it does ------ -------------- openarchive Index an .mbox file or .eml directory: message count, date range, top senders searchmessages Search by keyword, sender, subject, date range — plus bounded body-text search getmessage Fully parse one message: decoded body, headers, attachment names/sizes
Built for large archives
A Takeout mbox is often multiple gigabytes with 100k+ messages. The design reads the minimum, lazily: • Streaming index — one pass in 8 MiB chunks, recording byte offsets; only the current message's first 16 KiB is ever held for envelope parsing (sender, subject, date, RFC 2047 decoding). • Full MIME on demand — reading a message parses just that message (postal-mime: nested multipart, charsets, quoted-printable/base64). Attachments are listed with names and sizes, never dumped into context. • Honest body search — bodyquery only full-parses messages that already match your envelope filters, stops at a scan cap, and reports how many it scanned, so…
01Capabilities
Does
- No capabilities recorded
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 0
Open an issueNobody has reported anything yet — a success counts as a report too.
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
This listing is unclaimed, so publisher identity cannot be verified and it stays below the “verified” tier by design — that is a statement about the listing, not about the project’s quality. Our automated scans still ran; a maintainer who claims it unlocks identity verification.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 0.0.0 | stable | Sep 28, 2026 | Indexed listing — see the upstream repository for real release history. |