Yahoo Mail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YAHOO_EMAIL | Yes | Your full Yahoo Mail address | |
| YAHOO_IMAP_HOST | No | IMAP host override | imap.mail.yahoo.com |
| YAHOO_IMAP_PORT | No | IMAP port override | 993 |
| YAHOO_SMTP_HOST | No | SMTP host override | smtp.mail.yahoo.com |
| YAHOO_SMTP_PORT | No | SMTP port override | 465 |
| YAHOO_APP_PASSWORD | Yes | App password generated in step 1 | |
| YAHOO_MCP_READ_ONLY | No | Set to true to disable create_folder, move_message, and send_email — only reading is possible. | 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_foldersA | List all folders/mailboxes in the Yahoo Mail account, including special-use folders like Inbox, Sent, Drafts, and Trash. |
| create_folderA | Create a new folder (mailbox) in Yahoo Mail. Use '/' to specify a nested folder path, e.g. 'Projects/Alpha'. |
| list_messagesA | List message summaries (subject, from, to, date, read status) in a given folder, optionally filtered by unread status, sender, subject text, or date. |
| get_messageA | Fetch the full content (text and HTML body) of a single message by folder and UID. |
| move_messageC | Move a single message from one folder to another by UID. |
| send_emailB | Compose and send a new email from the configured Yahoo Mail account. Provide plain text and/or HTML body. |
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 6 tools
Each tool targets a distinct action and resource: folders vs. messages vs. sending. list_messages and get_message are clearly separated as summary vs. full content, so there is no real ambiguity.
All tool names follow a consistent verb_noun pattern: list_folders, create_folder, list_messages, get_message, move_message, send_email. This makes the toolset predictable and easy to navigate.
Six tools is a well-scoped size for an email-focused server. Each tool covers an essential part of the core workflow without unnecessary bloat or redundancy.
The core email flows are covered: listing folders and messages, reading, moving, sending, and creating folders. However, obvious operations like deleting messages, marking read/unread, and renaming or deleting folders are missing, creating notable gaps for full mailbox management.