Email MCP: Yandex, Mail.ru and other providers
Email MCP Server
An HTTP/SSE wrapper around an IMAP MCP server for remote mailbox access from Claude Web: read, search, send, across 15 providers
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- It can send, forward and delete email on the user's behalf
- Mail credentials are stored in a Docker volume; server access equals mailbox access
Install
Manual install
git clone https://github.com/nikolausm/imap-mcp-server.git && cd imap-mcp-server && npm install && npm run build && npm run setupThe base server this repository wraps.
This is third-party code. Review the repository files before installing.
What it does
The server wraps the third-party STDIO MCP server nikolausm/imap-mcp-server in an HTTP/SSE transport so a mailbox can be reached remotely, for example from Claude Web through a custom connector. It supports several mail accounts at once, encrypts credentials with AES-256, and provides tools for reading, searching, sending, replying to and forwarding email, plus folder management. The README gives specific setup steps for Gmail, Outlook, Yahoo and the Russian mail services Yandex and Mail.ru, with concrete IMAP/SMTP addresses.
Who it is for. For people who want to give an agent access to a personal or work mailbox on Yandex, Mail.ru or another provider from Claude Web.
Good fit when
- You need remote mailbox access through Claude Web, not just a desktop client
- You have several mail accounts, including Yandex or Mail.ru, and want to manage them from one place
- You need to send and forward mail, not just read it
Not a fit when
- You only need local access to one account: it is simpler to run the base imap-mcp-server without the wrapper
- You have no server to deploy the wrapper on: the repository assumes self-hosting, there is no ready cloud instance
Example request
Find unread emails from accounting in my Yandex mailbox from the last weekLimitations
This is a wrapper around a separate project, nikolausm/imap-mcp-server, and the core mail logic lives there, not in this repository. The README references the author's own production server (217.199.253.8, mcp.svsfinpro.ru) as a deployment example; for your own use you need your own server. It requires an app password from the mail provider, a regular account password will not work.
How to disable. Stop the container (docker-compose down) or remove the connector from Claude Web settings, then revoke the app password at the mail provider.
MCP
- Transport
- http
- Authentication
- API key
| Environment variables | |
|---|---|
| HOST | Address the server listens on, defaults to 0.0.0.0 |
| PORT | Server port, defaults to 8080 |
| IMAP_SERVER_PATH | Path to the built imap-mcp-server |
Security check
- It can send, forward and delete email on the user's behalf
- Mail credentials are stored in a Docker volume; server access equals mailbox access
README in short
The README describes the wrapper architecture over imap-mcp-server, local and Docker startup, health and sse endpoints, the full IMAP tool list (accounts, mail, folders), app-password instructions for Gmail, Yandex and Mail.ru, and security and deployment notes for the author's own production server.
FAQ
Does it work with Yandex and Mail.ru?
Yes, the README gives ready IMAP/SMTP addresses for both: imap.yandex.ru and imap.mail.ru.
Do I need my own server?
Yes, remote HTTP/SSE access requires your own hosting; the project does not provide a ready cloud instance.
Related
A self-hosted knowledge base with block-level references and a built-in MCP server for connecting AI agents to your notes
A CLI for every Google Workspace API with JSON output and agent skills: Drive, Gmail, Calendar, Sheets and more
Local search over Markdown notes, docs and meeting transcripts: keywords, semantic search and reranking, with an MCP server
A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI