Yandex Mail MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host for the HTTP MCP endpoint (for example 127.0.0.1). | |
| MCP_PORT | No | Port for the HTTP MCP endpoint (for example 8000). | |
| YANDEX_EMAIL | Yes | Your Yandex email address. | |
| MCP_TRANSPORT | No | MCP transport to use; default is stdio. Set to streamable-http for a local HTTP MCP endpoint. | stdio |
| MCP_AUTH_TOKEN | No | Bearer token for HTTP transport authentication; required for non-loopback binds unless MCP_ALLOW_UNAUTHENTICATED_REMOTE=true. | |
| MCP_ALLOWED_HOSTS | No | Allowed hostnames or IP addresses and ports for DNS rebinding protection, e.g. 127.0.0.1:*,192.168.1.5:*. | |
| YANDEX_ALLOW_WRITE | No | Enable write operations such as move_to_promotions; default is false (read-only). | false |
| MCP_ALLOWED_ORIGINS | No | Allowed browser origins for HTTP transport when needed. | |
| YANDEX_APP_PASSWORD | Yes | Dedicated Yandex Mail app password; do not use your primary account password. | |
| MCP_ALLOW_UNAUTHENTICATED_REMOTE | No | Set to true to explicitly allow unauthenticated remote HTTP access on non-loopback binds. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_foldersA | List IMAP folder names in the connected Yandex mailbox. |
| list_recent_emailsA | Read most recent messages, without marking them read. Maximum 100. |
| search_emailsC | Find sender, subject or content matches in a folder. |
| get_emailA | Read a message by IMAP UID, without marking it as read. |
| move_to_promotionsA | Move a message from Inbox to a dedicated promotions folder. Disabled by default; requires server opt-in, confirm=true and client elicitation. Never permanently deletes mail. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct primary action: listing folders, listing recent mail, searching, fetching by UID, and moving to promotions. The only mild overlap is between list_recent_emails and search_emails, but their descriptions make the intended use cases distinguishable.
All tool names follow a consistent snake_case verb_noun pattern: list_folders, list_recent_emails, search_emails, get_email, move_to_promotions. There are no mixed conventions or vague verbs.
Five tools is a well-scoped set for a focused mail-reading server, and each tool corresponds to a meaningful operation. The count is neither bloated nor trivially thin.
The surface covers reading, searching, and one specialized move operation, but it lacks core email lifecycle operations such as sending, replying, general moving/archiving, deleting, and marking read/unread. An agent tasked with normal mailbox management would hit significant dead ends.