Email IMAP/SMTP MCP server: iCloud, Gmail, Yahoo, Outlook, and custom IMAP providers
Email (IMAP/SMTP) is an MCP integration. Email IMAP/SMTP MCP server: iCloud, Gmail, Yahoo, Outlook, and custom IMAP providers.
The published npm package is @mindstone/mcp-server-email-imap, version 0.3.2. Its declared MCP transport is stdio.
The package declares EMAIL_IMAP_EMAIL (required): Email address; EMAIL_IMAP_PASSWORD (required): App-specific password; 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..
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 0.3.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related communication MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| EMAIL_IMAP_EMAIL | Email address | Yes |
| EMAIL_IMAP_PASSWORD | App-specific password | Yes |
| EMAIL_IMAP_PROVIDER | Provider — icloud, gmail, yahoo, outlook, or custom (auto-detected from email domain if unset) | Optional |
| EMAIL_IMAP_IMAP_HOST | Custom IMAP host (for provider=custom) | Optional |
| EMAIL_IMAP_SMTP_HOST | Custom SMTP host (for provider=custom) | Optional |
| EMAIL_IMAP_IMAP_PORT | Custom IMAP port | Optional |
| EMAIL_IMAP_SMTP_PORT | Custom SMTP port | Optional |
| 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. | Optional |
| 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. | Optional |
| EMAIL_IMAP_RATE_LIMIT_WINDOW_MS | Sliding-window length for the rate limit (ms) | Optional |
| MCP_WORKSPACE_PATH | Workspace directory that email_get_attachment downloads into (fresh email-imap-attachment- staging directories). Defaults to the system temp directory. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.