Email (IMAP/SMTP) runs on your own machine — the client starts it, so there is no endpoint to ping. 156 installs a week from npm. Last commit 2 Nov 2026.
Email IMAP/SMTP MCP server: iCloud, Gmail, Yahoo, Outlook, and custom IMAP providers
We read the source, 22 h ago · rules 995398eba69f
A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.
fs.writeFileSync(outFd, pdfBuffer);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-server-email-imap -e 'EMAIL_IMAP_EMAIL=<EMAIL_IMAP_EMAIL>' -e 'EMAIL_IMAP_PASSWORD=<EMAIL_IMAP_PASSWORD>' -- npx -y @mindstone/mcp-server-email-imap
{
"mcpServers": {
"mcp-server-email-imap": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-email-imap"
],
"env": {
"EMAIL_IMAP_EMAIL": "<EMAIL_IMAP_EMAIL>",
"EMAIL_IMAP_PASSWORD": "<EMAIL_IMAP_PASSWORD>"
}
}
}
}
[mcp_servers.mcp-server-email-imap]
command = "npx"
args = ["-y", "@mindstone/mcp-server-email-imap"]
env = { EMAIL_IMAP_EMAIL = "<EMAIL_IMAP_EMAIL>", EMAIL_IMAP_PASSWORD = "<EMAIL_IMAP_PASSWORD>" }
{
"mcpServers": {
"mcp-server-email-imap": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-email-imap"
],
"env": {
"EMAIL_IMAP_EMAIL": "<EMAIL_IMAP_EMAIL>",
"EMAIL_IMAP_PASSWORD": "<EMAIL_IMAP_PASSWORD>"
}
}
}
}
{
"servers": {
"mcp-server-email-imap": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-email-imap"
],
"env": {
"EMAIL_IMAP_EMAIL": "<EMAIL_IMAP_EMAIL>",
"EMAIL_IMAP_PASSWORD": "<EMAIL_IMAP_PASSWORD>"
}
}
}
}
Put your own values in place of
<EMAIL_IMAP_EMAIL> (Email address), <EMAIL_IMAP_PASSWORD> (App-specific password).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
EMAIL_IMAP_PROVIDER (Provider — icloud, gmail, yahoo, outlook, or custom (auto-detected from email domain if unset)), EMAIL_IMAP_IMAP_HOST (Custom IMAP host (for provider=custom)), EMAIL_IMAP_SMTP_HOST (Custom SMTP host (for provider=custom)), EMAIL_IMAP_IMAP_PORT (Custom IMAP port), EMAIL_IMAP_SMTP_PORT (Custom SMTP port), EMAIL_IMAP_MAX_RECIPIENTS (Safety cap: maximum combined To+CC+BCC recipients per email_send call. Defaults to 25; raising bypasses spam-prevention guardrails against prompt-injection-driven mass sends), EMAIL_IMAP_RATE_LIMIT_PER_HOUR (Safety cap: maximum email_send calls per rolling window. Defaults to 50; protects against runaway sends when injection content escapes the LLM's intent), EMAIL_IMAP_RATE_LIMIT_WINDOW_MS (Sliding-window length for the rate limit (ms)), MCP_WORKSPACE_PATH (Workspace directory that email_get_attachment downloads into (fresh email-imap-attachment-* staging directories). Defaults to the system temp directory).
Unified email MCP server for Gmail, Outlook, iCloud, and IMAP with batch operations
Connect Gmail, Outlook, iCloud, Yahoo and IMAP to AI apps in one MCP connection.
Email for AI agents: read, search and send from your Gmail, Outlook, Yahoo, iCloud or IMAP inbox.
Email MCP server for AI agents: IMAP/SMTP, Gmail, Outlook, calendar, ManageSieve, AI triage, OAuth2.
Hosted MCP server for your Gmail, Outlook and IMAP mail, with mailboxes and scopes set per agent.
Email MCP server for Gmail, Outlook and any IMAP mailbox, hardened against prompt injection
MCP server for Aruba email and calendar via IMAP/SMTP/CalDAV
Inbox placement tests across Gmail, Outlook, Yahoo and 30+ providers.
Answers built from our own checks of this server.