Mail.ru MCP server and Telegram notifier
Mail Agent
An MCP server for Mail.ru email in Claude.ai, plus a separate Telegram bot that checks the inbox every 15 minutes and alerts on important messages
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
- The send_reply tool sends emails via SMTP on behalf of the mailbox owner
- The Mail.ru app password sits in Railway environment variables in plain text with no secrets manager
Install
Manual install
Deploy mcp-server as a Railway service with Root Directory mcp-server and the MAIL_IMAP_HOST, MAIL_SMTP_HOST, MAIL_USERNAME and MAIL_PASSWORD (a Mail.ru app password) variables, generate a domain, then in Claude.ai go to Settings, MCP Servers and add https://<domain>.up.railway.app/mcp.
This is third-party code. Review the repository files before installing.
What it does
The repository provides two independent services. An MCP server on FastMCP and Streamable HTTP exposes 7 tools for Mail.ru email over IMAP and SMTP: new emails in the last N hours, emails flagged Important, search by text, sender and date, full message content, structured data for analysis, replying to an email via SMTP, and listing mailbox folders. A Telegram notifier runs as a background worker, checking mail via IMAP every 15 minutes, classifying messages into categories (urgent: government bodies like Rosreestr and the tax service; important: finance and contracts; lead: commercial proposals and tenders), running them through Claude for analysis, and sending a Telegram alert, deduplicating already-sent messages via SQLite. Both services are meant to be deployed on Railway as separate services.
Who it is for. For Mail.ru email owners who want access to their inbox from Claude.ai and instant Telegram alerts on important messages.
Good fit when
- You want to read, search and reply to Mail.ru email right from the Claude.ai chat
- You want Telegram alerts on emails from government bodies, finance or new leads without constantly checking mail
- You are ready to deploy two services on Railway and store a Mail.ru app password in environment variables
Not a fit when
- You don't want to store an email app password in cloud-hosting environment variables: the services read it plainly from ENV
- You need email other than Mail.ru: the IMAP and SMTP addresses are hardcoded to imap.mail.ru and smtp.mail.ru
- You don't want an always-on background process: telegram-notifier is built to run continuously on a check interval
Example request
Show new emails from the last 6 hours and reply to the accounting email confirming the invoice was paidLimitations
The repository has no license. The Mail.ru email password (an app password) is stored in Railway environment variables in plain text, with no secrets manager. The repo includes a folder of ready commercial proposal templates and real company logos (Gazprom, Magnit, Rostelecom and others) for its proposal-generation tool, worth noting before forking for your own use.
How to disable. Delete or stop both services in Railway, revoke the Mail.ru app password, and remove the MCP server from Claude.ai's settings.
MCP
- Transport
- http
- Authentication
- not required
| Environment variables | |
|---|---|
| MAIL_USERNAME required | Mail.ru mailbox address |
| MAIL_PASSWORD required, secret | Mail.ru app password for IMAP and SMTP |
Security check
- The send_reply tool sends emails via SMTP on behalf of the mailbox owner
- The Mail.ru app password sits in Railway environment variables in plain text with no secrets manager
README in short
The Russian README describes the structure of the two services, a step-by-step Railway deployment including creating a GitHub repo, environment variables for each service, connecting the MCP to Claude.ai via a URL, a table of the 7 MCP tools, and a table of the Telegram notifier's email classification categories by urgency.
FAQ
Do I need my regular mail password or an app password?
The README specifies a Mail.ru app password, which has to be created separately in the account's security settings, not the main account password.
Are both services required?
No, the MCP server and the Telegram notifier are independent, and you can deploy just one of them.
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