by yunfeizhu
Securely access and manage your emails domains with IMAP Apple and SMTP. Enjoy reliable email delivery with IMAP/SMTP su
Connects your AI assistant to email accounts via IMAP/SMTP to read, search, and send emails directly from chat.
Email (IMAP/SMTP) is a community-built MCP server published by yunfeizhu that provides AI assistants with tools and capabilities via the Model Context Protocol. Securely access and manage your emails domains with IMAP Apple and SMTP. Enjoy reliable email delivery with IMAP/SMTP su It is categorized under productivity, communication.
You can install Email (IMAP/SMTP) in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Email (IMAP/SMTP) is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Email (IMAP/SMTP) reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
According to our notes, Email (IMAP/SMTP) benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Email (IMAP/SMTP) has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Email (IMAP/SMTP) is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Email (IMAP/SMTP) is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Useful MCP listing: Email (IMAP/SMTP) is the kind of server we cite when onboarding engineers to host + tool permissions.
We wired Email (IMAP/SMTP) into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Email (IMAP/SMTP) reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We evaluated Email (IMAP/SMTP) against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: Email (IMAP/SMTP) is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 69
Language: English | 中文
A Model Context Protocol server for IMAP/SMTP email operations with Claude, Cursor, and other AI assistants.
npm install -g mcp-mail-serverAdd to your claude_desktop_config.json:
{
"mcpServers": {
"mcp-mail-server": {
"command": "npx",
"args": ["-y", "mcp-mail-server"],
"env": {
"IMAP_HOST": "your-imap-server.com",
"IMAP_PORT": "993",
"IMAP_SECURE": "true",
"SMTP_HOST": "your-smtp-server.com",
"SMTP_PORT": "465",
"SMTP_SECURE": "true",
"EMAIL_USER": "[email protected]",
"EMAIL_PASS": "your-password"
}
}
}
}
Add to your Cursor MCP settings:
{
"mcpServers": {
"mcp-mail-server": {
"command": "npx",
"args": ["-y", "mcp-mail-server"],
"env": {
"IMAP_HOST": "your-imap-server.com",
"IMAP_PORT": "993",
"IMAP_SECURE": "true",
"SMTP_HOST": "your-smtp-server.com",
"SMTP_PORT": "465",
"SMTP_SECURE": "true",
"EMAIL_USER": "[email protected]",
"EMAIL_PASS": "your-password"
}
}
}
}
Add using the claude mcp add command:
claude mcp add mcp-mail-server \
-e IMAP_HOST=your-imap-server.com \
-e IMAP_PORT=993 \
-e IMAP_SECURE=true \
-e SMTP_HOST=your-smtp-server.com \
-e SMTP_PORT=465 \
-e SMTP_SECURE=true \
-e [email protected] \
-e EMAIL_PASS=your-password \
-- npx -y mcp-mail-server
Or manually add to .claude/settings.json:
{
"mcpServers": {
"mcp-mail-server": {
"command": "npx",
"args": ["-y", "mcp-mail-server"],
"env": {
"IMAP_HOST": "your-imap-server.com",
"IMAP_PORT": "993",
"IMAP_SECURE": "true",
"SMTP_HOST": "your-smtp-server.com",
"SMTP_PORT": "465",
"SMTP_SECURE": "true",
"EMAIL_USER": "[email protected]",
"EMAIL_PASS": "your-password"
}
}
}
}
Add to codex.json in your project root:
{
"mcpServers": {
"mcp-mail-server": {
"command": "npx",
"args": ["-y", "mcp-mail-server"],
"env": {
"IMAP_HOST": "your-imap-server.com",
"IMAP_PORT": "993",
"IMAP_SECURE": "true",
"SMTP_HOST": "your-smtp-server.com",
"SMTP_PORT": "465",
"SMTP_SECURE": "true",
"EMAIL_USER": "[email protected]",
"EMAIL_PASS": "your-password"
}
}
}
}
Other MCP clients can be configured similarly. The core configuration is:
{
"mcpServers": {
"mcp-mail-server": {
"command": "npx",
"args": ["-y", "mcp-mail-server"],
"env": {
"IMAP_HOST": "your-imap-server.com",
"IMAP_PORT": "993",
"IMAP_SECURE": "true",
"SMTP_HOST": "your-smtp-server.com",
"SMTP_PORT": "465",
"SMTP_SECURE": "true",
"EMAIL_USER": "[email protected]",
"EMAIL_PASS": "your-password"
}
}
}
}
Refer to your specific client's documentation for the appropriate configuration file location.
</details>| Tool | Description |
|---|---|
connect_all | Connect to both IMAP and SMTP servers |
get_connection_status | Check connection status and server info |
disconnect_all | Disconnect from all servers |
open_mailbox | Open specific mailbox/folder |
list_mailboxes | List available mail folders |
get_message_count | Get total message count in current mailbox |
get_unseen_messages | Get all unread emails |
get_recent_messages | Get recent emails |
search_by_sender | Find emails from specific sender |
search_by_subject | Search by subject keywords |
search_by_recipient | Find emails sent to specific recipient |
search_by_body | Search message body content |
search_since_date | Find emails since date |
search_unread_from_sender | Find unread emails from specific sender |
search_unreplied_from_sender | Find unreplied emails from specific sender |
search_with_keyword | Search emails by keyword/flag |
search_all_messages | Search all messages with optional date range and limit |
get_message | Retrieve email by UID |
get_messages | Retrieve multiple emails |
delete_message | Delete email by UID |
send_email | Send email via SMTP (with optional attachments) |
reply_to_email | Reply to specific email |
get_attachments | Get attachment metadata for an email |
save_attachment | Download and save attachments to local files |
mailboxName (string, default: "INBOX"), readOnly (boolean)sender (string, email address), startDate (string, optional), endDate (string, optional)subject (string, keywords), startDate (string, optional), endDate (string, optional)recipient (string, email address), startDate (string, optional), endDate (string, optional)text (string, search text), startDate (string, optional), endDate (string, optional)date (string, date format)sender (string, email address), startDate (string, optional), endDate (string, optional)sender (string, email address), startDate (string, optional), endDate (string, optional), limit (number, optional)keyword (string, keyword), startDate (string, optional), endDate (string, optional)startDate (string, optional), endDate (string, optional), limit (number, optional, default: 50)uid (number), markSeen (boolean, optional)uids (array), markSeen (boolean, optional)uid (number)to (string), subject (string), text (string, optional), html (string, optional), cc (string, optional), bcc (string, optional), attachments (string[], optional, absolute file paths)originalUid (number), text (string), html (string, optional), replyToAll (boolean, optional), includeOriginal (boolean, optional)uid (number) — Returns metadata: filename, contentType, size, indexuid (number), savePath (string, absolute path), attachmentIndex (number, optional, 0-based), returnBase64 (boolean, optional, default: false)Use natural language commands with your AI assistant:
⚠️ All variables are required
| Variable | Description | Example |
|---|---|---|
IMAP_HOST | IMAP server address | imap.gmail.com |
IMAP_PORT | IMAP port number | 993 |
IMAP_SECURE | Enable TLS | true |
SMTP_HOST | SMTP server address | smtp.gmail.com |
SMTP_PORT | SMTP port number | 465 |
SMTP_SECURE | Enable SSL | true |
EMAIL_USER | Email username | [email protected] |
EMAIL_PASS | Email password/app password | your-app-password |
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.