Email Server▌

by ai-zerolab
Connect your free email services or Mailchimp for seamless automation. Manage emails efficiently with IMAP and SMTP supp
Integrates with email providers to enable sending and receiving emails, automating workflows and managing communications via IMAP and SMTP functionality.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Automating email workflows and responses
- / Building email management applications
- / CI/CD pipeline email notifications
- / Customer support automation
capabilities
- / Send emails with reply threading
- / List email metadata and retrieve full content
- / Delete emails by ID
- / Download email attachments
- / Manage multiple email accounts
- / Configure accounts via UI or environment variables
what it does
Connects to email accounts via IMAP and SMTP to send, receive, list, and manage emails programmatically. Supports multiple email providers and attachment downloads.
about
Email Server is a community-built MCP server published by ai-zerolab that provides AI assistants with tools and capabilities via the Model Context Protocol. Connect your free email services or Mailchimp for seamless automation. Manage emails efficiently with IMAP and SMTP supp It is categorized under communication. This server exposes 7 tools that AI clients can invoke during conversations and coding sessions.
how to install
You can install Email Server 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.
license
BSD-3-Clause
Email Server is released under the BSD-3-Clause license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
mcp-email-server
IMAP and SMTP via MCP Server
- Github repository: https://github.com/ai-zerolab/mcp-email-server/
- Documentation https://ai-zerolab.github.io/mcp-email-server/
Installation
Manual Installation
We recommend using uv to manage your environment.
Try uvx mcp-email-server@latest ui to config, and use following configuration for mcp client:
{
"mcpServers": {
"zerolib-email": {
"command": "uvx",
"args": ["mcp-email-server@latest", "stdio"]
}
}
}
This package is available on PyPI, so you can install it using pip install mcp-email-server
After that, configure your email server using the ui: mcp-email-server ui
Environment Variable Configuration
You can also configure the email server using environment variables, which is particularly useful for CI/CD environments like Jenkins. zerolib-email supports both UI configuration (via TOML file) and environment variables, with environment variables taking precedence.
{
"mcpServers": {
"zerolib-email": {
"command": "uvx",
"args": ["mcp-email-server@latest", "stdio"],
"env": {
"MCP_EMAIL_SERVER_ACCOUNT_NAME": "work",
"MCP_EMAIL_SERVER_FULL_NAME": "John Doe",
"MCP_EMAIL_SERVER_EMAIL_ADDRESS": "john@example.com",
"MCP_EMAIL_SERVER_USER_NAME": "john@example.com",
"MCP_EMAIL_SERVER_PASSWORD": "your_password",
"MCP_EMAIL_SERVER_IMAP_HOST": "imap.gmail.com",
"MCP_EMAIL_SERVER_IMAP_PORT": "993",
"MCP_EMAIL_SERVER_SMTP_HOST": "smtp.gmail.com",
"MCP_EMAIL_SERVER_SMTP_PORT": "465"
}
}
}
}
Available Environment Variables
| Variable | Description | Default | Required |
|---|---|---|---|
MCP_EMAIL_SERVER_ACCOUNT_NAME | Account identifier | "default" | No |
MCP_EMAIL_SERVER_FULL_NAME | Display name | Email prefix | No |
MCP_EMAIL_SERVER_EMAIL_ADDRESS | Email address | - | Yes |
MCP_EMAIL_SERVER_USER_NAME | Login username | Same as email | No |
MCP_EMAIL_SERVER_PASSWORD | Email password | - | Yes |
MCP_EMAIL_SERVER_IMAP_HOST | IMAP server host | - | Yes |
MCP_EMAIL_SERVER_IMAP_PORT | IMAP server port | 993 | No |
MCP_EMAIL_SERVER_IMAP_SSL | Enable IMAP SSL | true | No |
MCP_EMAIL_SERVER_IMAP_VERIFY_SSL | Verify IMAP SSL certificates (disable for self-signed) | true | No |
MCP_EMAIL_SERVER_SMTP_HOST | SMTP server host | - | Yes |
MCP_EMAIL_SERVER_SMTP_PORT | SMTP server port | 465 | No |
MCP_EMAIL_SERVER_SMTP_SSL | Enable SMTP SSL | true | No |
MCP_EMAIL_SERVER_SMTP_START_SSL | Enable STARTTLS | false | No |
MCP_EMAIL_SERVER_SMTP_VERIFY_SSL | Verify SSL certificates (disable for self-signed) | true | No |
MCP_EMAIL_SERVER_ENABLE_ATTACHMENT_DOWNLOAD | Enable attachment download | false | No |
MCP_EMAIL_SERVER_SAVE_TO_SENT | Save sent emails to IMAP Sent folder | true | No |
MCP_EMAIL_SERVER_SENT_FOLDER_NAME | Custom Sent folder name (auto-detect if not set) | - | No |
Enabling Attachment Downloads
By default, downloading email attachments is disabled for security reasons. To enable this feature, you can either:
Option 1: Environment Variable
{
"mcpServers": {
"zerolib-email": {
"command": "uvx",
"args": ["mcp-email-server@latest", "stdio"],
"env": {
"MCP_EMAIL_SERVER_ENABLE_ATTACHMENT_DOWNLOAD": "true"
}
}
}
}
Option 2: TOML Configuration
Add enable_attachment_download = true to your TOML configuration file (~/.config/zerolib/mcp_email_server/config.toml):
enable_attachment_download = true
[[emails]]
# ... your email configuration
Once enabled, you can use the download_attachment tool to save email attachments to a specified path.
Saving Sent Emails to IMAP Sent Folder
By default, sent emails are automatically saved to your IMAP Sent folder. This ensures that emails sent via the MCP server appear in your email client (Thunderbird, webmail, etc.).
The server auto-detects common Sent folder names: Sent, INBOX.Sent, Sent Items, Sent Mail, [Gmail]/Sent Mail.
To specify a custom Sent folder name (useful for providers with non-standard folder names):
Option 1: Environment Variable
{
"mcpServers": {
"zerolib-email": {
"command": "uvx",
"args": ["mcp-email-server@latest", "stdio"],
"env": {
"MCP_EMAIL_SERVER_SENT_FOLDER_NAME": "INBOX.Sent"
}
}
}
}
Option 2: TOML Configuration
[[emails]]
account_name = "work"
save_to_sent = true
sent_folder_name = "INBOX.Sent"
# ... rest of your email configuration
To disable saving to Sent folder, set MCP_EMAIL_SERVER_SAVE_TO_SENT=false or save_to_sent = false in your TOML config.
Self-Signed Certificates (e.g., ProtonMail Bridge)
If you're using a local mail server with self-signed certificates (like ProtonMail Bridge), you'll need to disable SSL certificate verification:
{
"mcpServers": {
"zerolib-email": {
"command": "uvx",
"args": ["mcp-email-server@latest", "stdio"],
"env": {
"MCP_EMAIL_SERVER_IMAP_VERIFY_SSL": "false",
"MCP_EMAIL_SERVER_SMTP_VERIFY_SSL": "false"
}
}
}
}
Or in TOML configuration:
[[emails]]
account_name = "protonmail"
# ... other settings ...
[emails.incoming]
verify_ssl = false
[emails.outgoing]
verify_ssl = false
For separate IMAP/SMTP credentials, you can also use:
MCP_EMAIL_SERVER_IMAP_USER_NAME/MCP_EMAIL_SERVER_IMAP_PASSWORDMCP_EMAIL_SERVER_SMTP_USER_NAME/MCP_EMAIL_SERVER_SMTP_PASSWORD
Then you can try it in Claude Desktop. If you want to intergrate it with other mcp client, run $which mcp-email-server for the path and configure it in your client like:
{
"mcpServers": {
"zerolib-email": {
"command": "{{ ENTRYPOINT }}",
"args": ["stdio"]
}
}
}
If docker is avaliable, you can try use docker image, but you may need to config it in your client using tools via MCP. The default config path is ~/.config/zerolib/mcp_email_server/config.toml
{
"mcpServers": {
"zerolib-email": {
"command": "docker",
"args": ["run", "-it", "ghcr.io/ai-zerolab/mcp-email-server:latest"]
}
}
}
Installing via Smithery
To install Email Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @ai-zerolab/mcp-email-server --client claude
Usage
Replying to Emails
To reply to an email with proper threading (so it appears in the same conversation in email clients):
- First, fetch the original email to get its
message_id:
emails = await get_emails_content(account_name="work", email_ids=["123"])
original = emails.emails[0]
- Send your reply using
in_reply_toandreferences:
await send_email(
account_name="work",
recipients=[original.sender],
subject=f"Re: {original.subject}",
body="Thank you for your email...",
in_reply_to=original.message_id,
references=original.message_id,
)
The in_reply_to parameter sets the In-Reply-To header, and references sets the References header. Both are used by email clients to thread conversations properly.
Development
This project is managed using uv.
Try make install to install the virtual environment and install the pre-commit hooks.
Use uv run mcp-email-server for local development.
Releasing a new version
- Create an API Token on PyPI.
- Add the API Token to your projects secrets with the name
PYPI_TOKENby visitin
FAQ
- What is the Email Server MCP server?
- Email Server is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Email Server?
- This profile displays 66 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.6 out of 5—verify behavior in your own environment before production use.
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★66 reviews- ★★★★★Alexander Johnson· Dec 28, 2024
I recommend Email Server for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Arjun Abbas· Dec 20, 2024
We evaluated Email Server against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★James Gill· Dec 20, 2024
Strong directory entry: Email Server surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★James Patel· Dec 20, 2024
According to our notes, Email Server benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Arjun Nasser· Dec 16, 2024
Email Server is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Emma Nasser· Dec 16, 2024
Email Server reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Neel Choi· Dec 4, 2024
Useful MCP listing: Email Server is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Aarav Liu· Nov 23, 2024
According to our notes, Email Server benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Sakshi Patil· Nov 19, 2024
Email Server reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Anaya Mensah· Nov 11, 2024
Email Server has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 66