Full-featured, multi-account MCP email server for Windows, macOS, and Linux—read, search, organize, and send email via IMAP and SMTP.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-email-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mcp-email-server [](https://github.com/Wh1isper/mcp-email-server/releases) [](https://github.com/Wh1isper/mcp-email-server/actions/workflows/main.yml?query=branch%3Amain) [](https://codecov.io/gh/Wh1isper/mcp-email-server) [](https://github.com/Wh1isper/mcp-email-server/blob/main/LICENSE) An MCP server for reading, searching, organizing, and sending email through IMAP and SMTP. > [!NOTE] > Version 1.0.0 introduces Local Email App V2. Updating the package does not > automatically import existing settings created with PyPI 0.16.0 and earlier: > they remain active in backward-compatible `legacy` mode, so there is no required > migration. If you > would like to use the new managed storage, you can review and import those > settings whenever it is convenient. `mcp-email-server` supports Windows, macOS, and Linux. See [Security](docs/security.md) for platform-specific filesystem and credential storage details. ## Optional migration for existing installations An `@latest` release that includes Local Email App V2 offers a preview-first CLI migration: ```bash uvx mcp-email-server@latest config init \ --database ~/.config/mcp-email-server/managed.sqlite3 uvx mcp-email-server@latest config import-legacy uvx mcp-email-server@latest config import-legacy --apply uvx mcp-email-server@latest config doctor ``` The apply step displays the plan again and asks for `IMPORT` confirmation. A complete import selects managed mode; otherwise the existing legacy settings remain selected. The source TOML file and its legacy keyring entries are left untouched. You can also run `uvx mcp-email-server@latest ui` and choose **Impor…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.