Yandex Mail MCP server
ymail-mcp
Yandex work mail in Claude Code over IMAP: reading, searching threads and drafting replies without sending
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Only reads mail and creates drafts; sending is not implemented
- The app password is stored locally with a file-permission check
Install
Manual install
claude mcp add ymail -- /path/to/uv run --directory ~/projects/ymail-mcp ymail-mcpRun git clone and uv sync first; the path to uv must be absolute.
This is third-party code. Review the repository files before installing.
What it does
The server connects a Yandex mailbox over IMAP and gives the agent read tools: folder list, unread messages, search by sender, subject, text and dates, reading a whole message and the thread around it. Separately it can create a draft, including a reply, and move a message to trash. It cannot send mail: a deliberate choice by the author, so a person always reviews and sends the draft. Reading uses IMAP BODY.PEEK, so messages are not marked read. There is a CLI for checking the setup without a model, and a companion calendar tool called ycal.
Who it is for. For people who run work correspondence in Yandex Mail and want an agent to search messages, read threads and draft replies.
Good fit when
- You need to find a message by subject or sender and read the whole thread around it
- You need a draft reply that you will send yourself
- You want to go through unread mail together with an agent
Not a fit when
- You need the agent to send mail itself: the server refuses to on principle
- Your mail is not on Yandex, or your organization's security policy forbids app passwords
Example request
Find the latest accounting email about the invoice and draft a reply confirming paymentLimitations
Requires a Yandex ID app password (a regular account password will not work), created under Security. The server refuses to start if the credentials file is readable by anyone but the owner. Needs uv to install. There is no send capability by design. Tested only against Yandex; the code is not built for other IMAP providers.
How to disable. Run claude mcp remove ymail in Claude Code and revoke the app password in Yandex ID if needed.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| YMAIL_USER required | Yandex mail address |
| YMAIL_PASSWORD required, secret | App password created in Yandex ID |
Security check
- Only reads mail and creates drafts; sending is not implemented
- The app password is stored locally with a file-permission check
README in short
The README lists seven tools in a table marked read or write, explains getting the app password and storing it in a protected file or env vars. It separately covers gotchas: IMAP folder name encoding, the need to check sent mail too, and Cyrillic search queries. It ends with the companion ycal calendar project and a joint mail-and-calendar workflow.
FAQ
Why can't the server send mail?
A deliberate choice by the author: a message sent by mistake cannot be recalled, while a draft a person reviews and sends carries zero of that risk.
Will my regular Yandex ID password work?
No, you need a separate app password for IMAP mail access; the regular account password is rejected.
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