Yad
An MCP server and OpenClaw plugin for Yandex Mail, Calendar, Disk and Contacts using app passwords
Install
{
"mcpServers": {
"yandex": {
"command": "npx",
"args": ["tsx", "/path/to/yad/mcp-server.ts"],
"env": {
"YANDEX_LOGIN": "user@yandex.ru",
"YANDEX_DISK_APP_PASSWORD": "xxxx-xxxx-xxxx-xxxx",
"YANDEX_MAIL_APP_PASSWORD": "xxxx-xxxx-xxxx-xxxx",
"YANDEX_CALENDAR_APP_PASSWORD": "xxxx-xxxx-xxxx-xxxx",
"YANDEX_CONTACTS_APP_PASSWORD": "xxxx-xxxx-xxxx-xxxx"
}
}
}
}Clone the repository first. Keep passwords only for the services you need.
This is third-party code. Review the repository files before installing.
What it does
The server connects the agent to four Yandex services over open protocols: IMAP and SMTP for mail, CalDAV for calendar, CardDAV for contacts, WebDAV and REST API for Disk. The agent reads, searches, sends and deletes mail, downloads attachments, creates and edits events and contacts, and uploads, moves and publishes files. Files over 10 MB go through the Disk REST API, which needs an OAuth token. IMAP IDLE reports new mail in real time, and in OpenClaw it hands each message to a separate agent. For locked-down networks it supports HTTP or SOCKS proxies and ships a diagnostic tool.
Who it is for. For people who work in Yandex 360 and want an agent to handle their mail, calendar and files.
Good fit when
- You need to find mail by sender and subject and summarize it
- You need to create a Yandex Calendar event or update a contact
- You need to upload a report to Yandex Disk and get a public link
Not a fit when
- You need organization-wide OAuth access rather than app passwords
- The agent must not send or delete mail on your behalf
Example request
Find emails from accounting this week and move our meeting to Friday at 15:00Limitations
Each service needs its own Yandex app password, and large Disk files also need an OAuth token. There is no ready npx package: the server runs via tsx from a cloned repository. Yandex WebDAV is unreliable above 10 MB. A proxy with hostname-based rules may block IMAP, as the README explains.
How to disable. Remove the yandex block from the MCP client config or the yad plugin from OpenClaw and revoke the app passwords at id.yandex.ru.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| YANDEX_LOGIN required | Yandex login or full email |
| YANDEX_MAIL_APP_PASSWORD secret | App password of type Mail |
| YANDEX_CALENDAR_APP_PASSWORD secret | App password of type Calendars |
| YANDEX_DISK_APP_PASSWORD secret | App password of type Files |
| YANDEX_CONTACTS_APP_PASSWORD secret | App password of type Contacts |
| YANDEX_DISK_OAUTH_TOKEN secret | OAuth token for Disk files over 10 MB |
Security check
- Sends and deletes email on the mailbox owner's behalf
- Deletes Disk files and publishes them via public links
- Stores app passwords for a personal Yandex account
README in short
The README describes a server for Yandex Mail, Calendar, Disk and Contacts available as MCP and as an OpenClaw plugin. It covers MCP config, environment variables, plugin install and IMAP IDLE. A large section explains proxy use with a port table and checks via yad_diagnose. Tool tables, app password setup, getting a Disk OAuth token and development commands follow. MIT license.
FAQ
Do I need to register an OAuth app?
Not for mail, calendar, contacts or files up to 10 MB; app passwords are enough. OAuth is only needed for large Disk files.
Can I enable only Disk?
Yes. Only YANDEX_LOGIN is required; services without an app password stay off.
Related
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
Anthropic's official plugins for knowledge work roles: sales, support, product, marketing, legal, finance, data and enterprise search