IMAP Mail MCP
Enables LLM clients to read and search email via IMAP with tools for listing folders, searching messages, and fetching message content. It supports pagination, snippets, and thread context, and is designed for local AI workflows.
README
IMAP Mail MCP
IMAP Mail MCP is an MCP (Model Context Protocol) server that lets LLM clients read email through IMAP tools.
It is designed for:
- local AI workflows (Cursor, ollmcp, other MCP hosts)
- mailbox exploration/search/summarization
- extension by developers who want to add mail tools
Current implementation is read-only (list/search/fetch/status/thread context/attachment metadata).
What You Get
- 10 MCP tools for common mail workflows
- consistent sorting and cursor pagination support
- guardrails for result size and snippet size
- deterministic tests plus CI
- TypeScript codebase that is easy to extend
Quick Start
1. Install
git clone https://github.com/FaisalFehad/imap-mail-mcp.git
cd imap-mail-mcp
cp .env.example .env
npm install
npm run build
2. Configure .env
Set IMAP credentials in .env:
| Variable | Required | Description | Typical Example |
|---|---|---|---|
IMAP_HOST |
yes | IMAP host | 127.0.0.1 |
IMAP_PORT |
yes | IMAP port | 1143 |
IMAP_SECURE |
yes | true for TLS, false for plain |
false |
IMAP_USER |
yes | IMAP username | you@proton.me |
IMAP_PASS |
yes | IMAP password | ... |
IMAP_TLS_REJECT_UNAUTHORIZED |
no | validate TLS cert chain | false for local self-signed |
MAIL_MAX_BODY_LENGTH |
no | max body chars in mail_get_message |
50000 |
MAIL_MAX_RESULTS |
no | global cap for list/search limits | 200 |
MAIL_SNIPPET_LENGTH |
no | max snippet chars when enabled | 400 |
Proton Bridge users usually run with IMAP_HOST=127.0.0.1, IMAP_PORT=1143, IMAP_SECURE=false.
3. Run
node dist/index.js
Or via package bin:
npx imap-mail-mcp
Compatibility alias still works:
npx proton-bridge-mcp
MCP Client Setup
Cursor
Add server config (Settings -> MCP):
{
"mcpServers": {
"imap-mail": {
"command": "node",
"args": ["/absolute/path/to/imap-mail-mcp/dist/index.js"],
"env": {
"IMAP_HOST": "127.0.0.1",
"IMAP_PORT": "1143",
"IMAP_SECURE": "false",
"IMAP_USER": "your@proton.me",
"IMAP_PASS": "your-bridge-password"
}
}
}
}
ollmcp
- Create
~/.config/ollmcp/mcp-servers/servers.json:
{
"mcpServers": {
"imap-mail": {
"command": "node",
"args": ["/absolute/path/to/imap-mail-mcp/dist/index.js"],
"env": {
"IMAP_HOST": "127.0.0.1",
"IMAP_PORT": "1143",
"IMAP_SECURE": "false",
"IMAP_USER": "your@proton.me",
"IMAP_PASS": "your-bridge-password"
},
"disabled": false
}
}
}
- Run:
ollmcp -j ~/.config/ollmcp/mcp-servers/servers.json
If ollmcp is not in PATH, use ~/.local/bin/ollmcp.
Tool Reference
Use mail_search_advanced as the default search entry point.
| Tool | Use For | Notes |
|---|---|---|
mail_list_folders |
list mailboxes/folders | start here |
mail_list_messages |
list messages in one mailbox | supports limit, sort, cursor, includeSnippet, returnPage |
mail_get_message |
full message body by UID | returns envelope + body text |
mail_search |
basic filter search | convenience wrapper |
mail_search_advanced |
keyword/sender/receiver/subject/body/date/sent-date/read-state/message-id | primary search tool |
mail_get_mailbox_status |
counters for one mailbox | messages, unseen, recent, UID metadata |
mail_list_unread |
unread messages in a mailbox | same pagination/sort options as list/search |
mail_list_attachments |
attachment metadata by UID | no binary download |
mail_query_by_folder |
free text query by selected fields | convenience wrapper |
mail_get_thread_context |
related messages around a UID | thread continuity for summarization/reply |
Common List/Search Options
Supported by list/search tools:
limit: requested size (clamped byMAIL_MAX_RESULTS)sort:ascordesc(defaultdesc)cursor: opaque cursor for next pageincludeSnippet: include snippet text in envelope resultsreturnPage: return{ items, nextCursor }instead of only array
Envelope result fields are stable:
{
"uid": 123,
"subject": "string",
"from": "comma-separated addresses",
"to": "comma-separated addresses",
"date": "ISO-8601 string",
"messageId": "optional string",
"snippet": "optional string"
}
Example Workflows
Find unread billing mail in INBOX
mail_search_advancedwithmailbox=INBOX,keyword=bill,unseen=true,limit=20mail_get_messageon the most relevant UID
Summarize a conversation before drafting a reply
mail_get_thread_contextwith target UID andlimit- fetch one or two full messages with
mail_get_message - summarize using context
Scan a large folder in pages
mail_list_messageswithreturnPage=true- pass returned
nextCursorto next call until absent
Developer Guide (Use This Codebase)
Project Layout
src/index.ts MCP server, tool schemas, handlers
src/imap.ts IMAP operations and query behavior
src/query.ts sorting/pagination/cursor/snippet helpers
src/config.ts environment parsing and defaults
tests/*.test.mjs deterministic tests
Add a New Tool
- Add schema in
src/index.tstool list. - Add handler branch in
src/index.tscall handler. - Implement IMAP logic in
src/imap.ts. - Add deterministic tests in
tests/. - Update this README tool table.
Keep LLM Behavior Predictable
- keep envelope field names stable
- prefer additive changes (avoid breaking existing tool args)
- keep default ordering deterministic
- keep limits clamped
- avoid expensive full-mailbox scans where possible
Testing
Run deterministic tests (no live mailbox required):
npm test
Run live smoke test (requires real IMAP credentials):
node scripts/test-mcp.mjs
CI runs:
npm cinpx tsc --noEmitnpm test
Troubleshooting
Error: Command failed no such user (NO)
Usually bad IMAP_USER/IMAP_PASS or temporary server lockout after failed attempts.
Check:
IMAP_USERis your IMAP login identity, not host/IPIMAP_PASSis correct for that IMAP account- for Proton Bridge, use the Bridge-generated password
- wait a few minutes after repeated failed login attempts
TLS errors (wrong version number, ssl3_get_record)
You are likely using TLS against a plain IMAP port.
Fix:
- set
IMAP_SECURE=falsefor local plain IMAP endpoints (common with Bridge) - verify port matches secure/non-secure mode
Self-signed cert errors
If your IMAP endpoint uses self-signed certs:
- set
IMAP_TLS_REJECT_UNAUTHORIZED=false
ollmcp: command not found
Install via pip/pipx/uvx, or run with full path:
~/.local/bin/ollmcp -j ~/.config/ollmcp/mcp-servers/servers.json
Security
- never commit
.envor credential files - keep IMAP credentials in MCP client env or local
.env - this implementation does not send or modify mail
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。
mcp-server-qdrant
这个仓库展示了如何为向量搜索引擎 Qdrant 创建一个 MCP (Managed Control Plane) 服务器的示例。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。