mcp-email-server
An MCP server for reading, searching, organizing, and sending email through IMAP and SMTP.
mcp-email-server supports Windows, macOS, and Linux. See
Security 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:
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
and import troubleshooting.
Quick start
1. Configure an email account
From this source checkout, run the configuration UI with
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.
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. Release 1.6.2 and later
also publish Linux amd64/arm64 images at
ghcr.io/wh1isper/mcp-email-server; see the
container instructions.
Documentation
Development
See CONTRIBUTING.md.
License
This project is licensed under the terms of the LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for mcp-email-server 1.13.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mcp_email_server-1.13.2.tar.gz | 886.7 kB | Without provenance | Details for mcp_email_server-1.13.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_email_server-1.13.2-py3-none-any.whl | Python 3 | none | any | Details for mcp_email_server-1.13.2-py3-none-any.whl |
Total release size: 1.2 MB
Release files / mcp_email_server-1.13.2.tar.gz
| Download URL | mcp_email_server-1.13.2.tar.gz |
|---|---|
| Size | 886.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e9f6a31f51478e79bf849a9be60d4988773f084075fd38503500eb836fe02b0
|
|
BLAKE2b-256 checksum How to use checksums |
b0bc19b4a01a0bdc6ed13209cf1e1ec40af04bdff5181b01ffd7c7738152c4ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / mcp_email_server-1.13.2-py3-none-any.whl
| Download URL | mcp_email_server-1.13.2-py3-none-any.whl |
|---|---|
| Size | 309.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a47d54239c94a972d82431f4cda4fae66ffb704e9287b7551acf5a3fec8ff362
|
|
BLAKE2b-256 checksum How to use checksums |
c51f5fcad0844250020cbaf91de249c84e96f465ae908522ea08c83884a98b68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for mcp-email-server 1.13.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
