Email MCP Server
Enables email management for a single mailbox via IMAP and SMTP protocols. Supports reading, searching, and sending emails with threading support through stdio or HTTP transports.
README
email-mcp
Small personal MCP server for a single mailbox over IMAP + SMTP.
It is aimed at a private setup first:
- one mailbox
- credentials supplied through environment variables
- read mail over IMAP
- send mail over SMTP
- works well with Yandex Mail defaults, but can be pointed at any IMAP/SMTP provider
What I changed
This repo originally worked only in stdio mode. That is fine for local MCP clients, but ChatGPT web integration needs an HTTP MCP endpoint. The server now supports:
stdiofor local/dev usestreamable-httpfor ChatGPT web app usessefor compatibility
I also fixed a mail-threading issue:
- the old
reply_toparameter only set theReply-Toheader - real replies should usually use
In-Reply-ToandReferences read_emailnow returns those headers so they can be passed back intosend_email
And I improved read_email output by returning:
- decoded headers
- attachment metadata
- message threading headers
Attachment support
This version supports both reading and sending attachments.
Download an attachment from a received email
- Call
read_email(uid=..., folder="INBOX") - Inspect the
attachmentslist - Use
attachment_indexwithget_attachment(...)
get_attachment(...) returns:
filenamecontent_typesize_bytescontent_base64
Send attachments in outgoing email
send_email(...) accepts an attachments list.
Each item can be one of:
{"path": "/path/to/file.pdf"}
{"filename": "note.txt", "content_text": "hello from MCP"}
{"filename": "report.pdf", "content_base64": "JVBERi0x...", "content_type": "application/pdf"}
Sent folder behavior
After SMTP send succeeds, the same MIME message is appended to your IMAP sent folder.
By default that folder name is:
Sent
You can override it if your mailbox uses a different IMAP folder name:
export SENT_FOLDER="Sent"
# or
export MAILBOX_SENT_FOLDER="Sent"
If sent mail does not show up, first run list_folders() and use the exact folder name returned by your mailbox.
Files
server.py— MCP tool definitions and transport startupmail_ops.py— IMAP/SMTP implementationrequirements.txt— Python dependencies
Environment
Required:
export MAILBOX_EMAIL="you@example.com"
export MAILBOX_PASSWORD="your-app-password"
Optional provider settings:
export IMAP_HOST="imap.yandex.com"
export IMAP_PORT="993"
export SMTP_HOST="smtp.yandex.com"
export SMTP_PORT="465"
Optional sent-folder setting:
export SENT_FOLDER="Sent"
Optional MCP server settings:
export MCP_TRANSPORT="stdio"
export MCP_HOST="0.0.0.0"
export MCP_PORT="8000"
Aliases also supported for convenience:
export YANDEX_EMAIL="you@yandex.ru"
export YANDEX_APP_PASSWORD="..."
Install
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
Run locally with stdio
python server.py
This is the right mode for local MCP clients that spawn the process directly.
Run for ChatGPT web app
ChatGPT web needs a public HTTPS MCP endpoint. Start the server in HTTP mode:
python server.py --transport streamable-http --host 0.0.0.0 --port 8000
Then expose that port through a public HTTPS tunnel or reverse proxy, and register the resulting MCP URL in ChatGPT.
Tools exposed
list_folders()
Lists available IMAP folders.
search_emails(folder="INBOX", text=None, unseen_only=False, since_date=None, limit=30)
Searches messages by IMAP criteria.
Returns items like:
uidsubjectfromtodateflagssize_bytes
read_email(uid, folder="INBOX")
Fetches a full message without marking it read.
Returns:
- decoded headers
message_idin_reply_toreferencesattachmentsbody_plainbody_html
get_attachment(uid, folder="INBOX", attachment_index=None, filename=None)
Fetches a single attachment and returns it as base64.
send_email(...)
Sends a message through SMTP.
Important parameters:
reply_to_header— sets the Reply-To headerin_reply_to— threading headerreferences— threading headerattachments— optional list of attachment specs
For a real reply, use in_reply_to and usually also references.
Yandex notes
Typical Yandex defaults are:
- IMAP:
imap.yandex.com:993over SSL/TLS - SMTP:
smtp.yandex.com:465over SSL/TLS
Use an app password, not your main account password.
Next sensible upgrades
- inline/embedded image attachments
- attachment size limits and streaming
- move/archive/delete tools with confirmation
- OAuth instead of env-based credentials
- tests with mocked IMAP/SMTP backends
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。