I
igorolv/mail-mcp-server
Give your AI agent your whole mailbox, including on-premises Exchange, with no way to change it.
updated 2026-11-14
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · igorolv/mail-mcp-server · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
igorolv/mail-mcp-server;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# Mail MCP Server
Excerpted from the repository README (abridged)
Give your AI agent your whole mailbox, including on-premises Exchange, with no way to change it.
MCP server (stdio) for on-premises Microsoft Exchange over EWS and any IMAP mailbox with password
sign-in, tested on Mail.ru and Gmail. It downloads every message once, converts bodies and
attachments to Markdown on your machine, builds a Lucene search index, and answers the agent from
that copy, so text inside PDF, Office and ZIP attachments is searchable in Russian and English.
Status: version 0.1.1 is published. Checked end to end on Exchange 2013 (about 8
thousand messages), Mail.ru (about 34 thousand) and Gmail with an app password. Developed and
tested on Windows.
Contents: Features ·
How it works ·
Typical Scenarios ·
Quickstart ·
MCP Tools ·
Commands ·
Build ·
Stack ·
Documentation ·
License
## Features
Works with on-premises Exchange. EWS with NTLM and your normal domain password, tested on
Exchange 2013. No Microsoft Graph needed. Other mailboxes work over IMAP, tested on Mail.ru and Gmail.
Attachments are searchable too. Text from PDF, Word, Excel, PowerPoint, ZIP archives,
attached emails, Outlook .msg and winmail.dat is extracted and indexed, so the agent can
find the contract inside the attachment, not just the message that carried it.
Search that understands word forms. Russian and English, across subject, body, addresses
and attachments. Copies of one message appear once, and conversations are followed across
folders (search).
Cannot change your mailbox. Read-only is enforced at the protocol level: write commands are
rejected before they are sent, and downloading a message does not mark it as read
(security).
Careful with your account. One sign-in per sync and no retries. After a rejected password,
it stops trying until you fix it, which reduces the risk of a domain lockout.
Fast, and works offline. The agent reads a local copy, so answers don't depend on the mail
server. Sync runs only when you ask for it.
Your mail stays on your machine. No cloud service of its own: conversion and indexing are
local, and the local copy is unfiltered. Your AI client still sees what the tools return, and an
optional secret filter masks passwords and codes in responses.
Several mailboxes, one server. Passwords can stay out of the config, in Windows Credential
Manager, a password manager or an environment variable (connections).
## How it works
1. Download all mail. The sync tool copies the included folders of each mailbox as original .eml files, then only changes on later runs.
2. Convert it locally to Markdown. Bodies and attachments — PDF, Office documents, archives,
attached messages — are converted with pandoc (required), PDFBox and Apache POI.
3. Index it. A Lucene index per mailbox with Russian and English word forms.
4. Use it from MCP. Tools search and read the local copy only; they never contact a mail
server.
text
MCP client (Claude Code, Codex, OpenCode, VS Code, ...)
| JSON-RPC over stdin / stdout
mail-mcp-server --- search, read ---> Lucene index + / /messages/
+--- sync (on request) --- EWS / IMAP --+--> .eml -> Markdown -> index
## Typical Scenarios
The agent picks the tools itself; these are the chains it usually follows.
MCP server (stdio) for on-premises Microsoft Exchange over EWS and any IMAP mailbox with password
sign-in, tested on Mail.ru and Gmail. It downloads every message once, converts bodies and
attachments to Markdown on your machine, builds a Lucene search index, and answers the agent from
that copy, so text inside PDF, Office and ZIP attachments is searchable in Russian and English.
Status: version 0.1.1 is published. Checked end to end on Exchange 2013 (about 8
thousand messages), Mail.ru (about 34 thousand) and Gmail with an app password. Developed and
tested on Windows.
Contents: Features ·
How it works ·
Typical Scenarios ·
Quickstart ·
MCP Tools ·
Commands ·
Build ·
Stack ·
Documentation ·
License
## Features
Works with on-premises Exchange. EWS with NTLM and your normal domain password, tested on
Exchange 2013. No Microsoft Graph needed. Other mailboxes work over IMAP, tested on Mail.ru and Gmail.
Attachments are searchable too. Text from PDF, Word, Excel, PowerPoint, ZIP archives,
attached emails, Outlook .msg and winmail.dat is extracted and indexed, so the agent can
find the contract inside the attachment, not just the message that carried it.
Search that understands word forms. Russian and English, across subject, body, addresses
and attachments. Copies of one message appear once, and conversations are followed across
folders (search).
Cannot change your mailbox. Read-only is enforced at the protocol level: write commands are
rejected before they are sent, and downloading a message does not mark it as read
(security).
Careful with your account. One sign-in per sync and no retries. After a rejected password,
it stops trying until you fix it, which reduces the risk of a domain lockout.
Fast, and works offline. The agent reads a local copy, so answers don't depend on the mail
server. Sync runs only when you ask for it.
Your mail stays on your machine. No cloud service of its own: conversion and indexing are
local, and the local copy is unfiltered. Your AI client still sees what the tools return, and an
optional secret filter masks passwords and codes in responses.
Several mailboxes, one server. Passwords can stay out of the config, in Windows Credential
Manager, a password manager or an environment variable (connections).
## How it works
1. Download all mail. The sync tool copies the included folders of each mailbox as original .eml files, then only changes on later runs.
2. Convert it locally to Markdown. Bodies and attachments — PDF, Office documents, archives,
attached messages — are converted with pandoc (required), PDFBox and Apache POI.
3. Index it. A Lucene index per mailbox with Russian and English word forms.
4. Use it from MCP. Tools search and read the local copy only; they never contact a mail
server.
text
MCP client (Claude Code, Codex, OpenCode, VS Code, ...)
| JSON-RPC over stdin / stdout
mail-mcp-server --- search, read ---> Lucene index + / /messages/
+--- sync (on request) --- EWS / IMAP --+--> .eml -> Markdown -> index
## Typical Scenarios
The agent picks the tools itself; these are the chains it usually follows.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/igorolv-mail-mcp-server/)
- Source
- awesome · https://github.com/igorolv/mail-mcp-server
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.