mcp-email-server
Full-featured, multi-account MCP email server for Windows, macOS, and Linux—read, search, organize, and send email via IMAP and SMTP.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Wh1isper/mcp-email-server with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Wh1isper/mcp-email-server'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/wh1isper--mcp-email-server)HTML
<a href="/listings/wh1isper--mcp-email-server"><img src="/api/listings/wh1isper--mcp-email-server/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
1. Configure an email account
From this source checkout, run the configuration UI with [`uv`](https://docs.astral.sh/uv/):
uv sync uv run mcp-email-server ui
For a published release whose notes state that it includes Local Email App V2, `uvx mcp-email-server@latest ui` is the equivalent temporary invocation.
Keep the foreground command running. On a truly empty installation, the authenticated browser session prepares private account storage at the safe local default; existing TOML or environment configuration instead offers an explicit import review while the previous settings keep running. The account-first UI has only **Email accounts** and **Settings & help** as primary destinations. Start with the email address and password; the UI fills common connection settings from the email domain and keeps them editable, while outgoing mail remains optional. A saved complete account is ready without a separate activation step. Use **Password & test** on the saved account if desired, then restart the MCP client to apply the selected settings.
2. Configure the MCP client
Use the same V2-capable distribution for stdio as for the UI. For a published V2 release, add the following server definition to the MCP client:
{
"mcpServers": {
"mcp-email-server": {
"command": "uvx",
"args": ["mcp-email-server@latest", "stdio"]
}
}
}Restart the MCP client after updating its configuration. When testing this source checkout before publication, invoke `uv run --directory /absolute/path/to/mcp-email-server mcp-email-server stdio` instead of pairing a managed catalog with PyPI `@latest`.
3. Verify the connection
Ask the client to list the configured email accounts or recent messages.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 25 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- {
- "$schema": "https://json.schemastore.org/claude-code-marketplace.json",
- "name": "mcp-email-server",
- "version": "0.0.1",
- "description": "Email MCP tools with safe, non-secret setup guidance.",
- "owner": {
- "name": "wh1isper"
- },
- "plugins": [
- {
- "name": "mcp-email-server",
- "source": "./plugins/mcp-email-server",
- "description": "Use email through MCP while handing secret entry to the user-operated CLI or local UI.",
- "version": "0.0.1",
- "author": {
- "name": "wh1isper"
- },
- "homepage": "https://mcp-email-server.wh1isper.top/",
- "repository": "https://github.com/Wh1isper/mcp-email-server",
- "license": "MIT",
- "keywords": ["email", "mcp", "security"],
- "category": "Productivity"
- }
- ]
- }
README.md · README · 120 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- # 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 **Import
- existing settings**. After a successful import, restart running MCP clients. See
- the detailed [upgrade guidance](docs/getting-started.md#upgrading-to-local-email-app-v2)
- and [import troubleshooting](docs/troubleshooting.md#legacy-import-reports-a-conflict-or-missing-credential).
- ## Quick start
- ### 1. Configure an email account
- From this source checkout, run the configuration UI with
- [`uv`](https://docs.astral.sh/uv/):
- ```bash
- uv sync
- uv run mcp-email-server ui
- ```
- For a published release whose notes state that it includes Local Email App V2,
- `uvx mcp-email-server@latest ui` is the equivalent temporary invocation.
- Keep the foreground command running. On a truly empty installation, the
- authenticated browser session prepares private account storage at the safe local
- default; existing TOML or environment configuration instead offers an explicit
- import review while the previous settings keep running. The account-first UI has
- only **Email accounts** and **Settings & help** as primary destinations. Start
- with the email address and password; the UI fills common connection settings from
- the email domain and keeps them editable, while outgoing mail remains optional.
- A saved complete account is ready without a separate activation step. Use
- **Password & test** on the saved account if desired, then restart the MCP client
- to apply the selected settings.
- ### 2. Configure the MCP client
- Use the same V2-capable distribution for stdio as for the UI. For a published
- V2 release, add the following server definition to the MCP client:
- ```json
- {
- "mcpServers": {
- "mcp-email-server": {
- "command": "uvx",
- "args": ["mcp-email-server@latest", "stdio"]
- }
- }
- }
- ```
- Restart the MCP client after updating its configuration. When testing this
- source checkout before publication, invoke `uv run --directory
- /absolute/path/to/mcp-email-server mcp-email-server stdio` instead of pairing a
- managed catalog with PyPI `@latest`.
- ### 3. Verify the connection
- Ask the client to list the configured email accounts or recent messages.
- ## Other configuration methods
- For the SQLite-backed managed CLI workflow, Windows and POSIX storage boundaries,
- headless environments, multiple accounts, custom TLS settings, and
- environment-variable configuration, see the
- [documentation](https://mcp-email-server.wh1isper.top/). Release 1.6.2 and later
- also publish Linux `amd64`/`arm64` images at
- `ghcr.io/wh1isper/mcp-email-server`; see the
- [container instructions](https://mcp-email-server.wh1isper.top/getting-started/#run-the-official-container-image).
- ## Documentation
- - [Getting Started](https://mcp-email-server.wh1isper.top/getting-started/)
- - [Configuration](https://mcp-email-server.wh1isper.top/configuration/)
- - [MCP Tools](https://mcp-email-server.wh1isper.top/tools/)
- - [Transports](https://mcp-email-server.wh1isper.top/transports/)
- - [Security](https://mcp-email-server.wh1isper.top/security/)
- - [Troubleshooting](https://mcp-email-server.wh1isper.top/troubleshooting/)
- ## Development
- See [CONTRIBUTING.md](https://github.com/Wh1isper/mcp-email-server/blob/main/CONTRIBUTING.md).
- ## License
- This project is licensed under the terms of the [LICENSE](https://github.com/Wh1isper/mcp-email-server/blob/main/LICENSE).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.