MCP SERVERRead, search, send and reply to email over IMAP and SMTP, across several accounts and any provider.
LABSCO SUMMARY
Collapsing fifteen actions behind one tool with lazy parameter discovery is the interesting choice here: the client sees one entry, and the schema for an action only arrives when it is needed. Passwords sit in a plaintext config file, so keep it out of version control and treat the send code as a workflow checkpoint rather than a security boundary.
A provider-agnostic email MCP server. It talks plain IMAP and SMTP, so it works against Gmail, Outlook, Purelymail, DomainFactory or any standard mail host, and it can hold several accounts at once. Everything is exposed through a single email tool with an action argument, which keeps the client's tool list to one entry.
An accounts.json listing each mailbox with its address and password (app passwords for Gmail and Outlook), pointed at by ACCOUNTS_FILE — or a single account through EMAIL_ADDRESS, EMAIL_PASSWORD, IMAP_HOST and SMTP_HOST. Install with pip install simple-email-mcp and the client runs simple-email-mcp over stdio. The config is re-read on every call, so rotating a value takes effect without a restart. Setting send_code makes the assistant ask you for that code before any send.
One command plus credentials — pip install simple-email-mcp, then supply credentials
USE CASES
List recent messages in a folder, then read the ones that matter in full.
Read the message, then reply-all with threading, quoting and recipients set for you.
Check the attachment paths, sizes and MIME types first, then send.
Search by IMAP criteria, move what belongs elsewhere, and mark the rest read.
Validate the configuration without logging in, then confirm the account list looks right.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
emailEmail client (IMAP/SMTP). Call with just action to discover its parameters. Actions: validate_config, list_accounts, list_folders, list_emails, search, read, send, reply, reply_all, forward, move, mark, save_attachment, get_attachment, prepare_attachments.
BEFORE YOU INSTALL
1 tool when we connected. The single email tool takes actions such as send, reply, search and read. The v1 tools, including email_send_email and email_read_email, no longer exist.
An accounts.json (ACCOUNTS_FILE points at it), or EMAIL_ADDRESS, EMAIL_PASSWORD, IMAP_HOST and SMTP_HOST in your environment
All 3 documented setups run the server on your machine.
CONTEXT COST
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
pip install simple-email-mcpclaude mcp add email -s user -e ACCOUNTS_FILE=<YOUR_ACCOUNTS_FILE> -- simple-email-mcpEMAIL_PASSWORD only applies to the single-account setup without accounts.json: set EMAIL_ADDRESS, EMAIL_PASSWORD, IMAP_HOST and SMTP_HOST as environment variables for the server (with -e in claude mcp add, or an env block). With accounts.json, each account's password goes in its password field, and ACCOUNTS_FILE points the server at the file.
{
"mcpServers": {
"email": {
"command": "simple-email-mcp"
}
}
}EMAIL_PASSWORD only applies to the single-account setup without accounts.json: set EMAIL_ADDRESS, EMAIL_PASSWORD, IMAP_HOST and SMTP_HOST as environment variables for the server (with -e in claude mcp add, or an env block). With accounts.json, each account's password goes in its password field, and ACCOUNTS_FILE points the server at the file.
{
"mcpServers": {
"email": {
"command": "python",
"args": [
"<YOUR_PATH_TO_SIMPLE_EMAIL_MCP>"
]
}
}
}EMAIL_PASSWORD only applies to the single-account setup without accounts.json: set EMAIL_ADDRESS, EMAIL_PASSWORD, IMAP_HOST and SMTP_HOST as environment variables for the server (with -e in claude mcp add, or an env block). With accounts.json, each account's password goes in its password field, and ACCOUNTS_FILE points the server at the file.
MCP servers
tecnologicachile
emailens
Wh1isper
Shy2593666979