Yahoo Mail MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for SSE mode (auto-set by Render) | 3000 |
| NODE_ENV | No | Environment: `development` or `production` | development |
| YAHOO_EMAIL | Yes | Your Yahoo Mail email address | |
| TRANSPORT_MODE | No | Transport mode: `stdio` or `sse` | stdio |
| OAUTH_CLIENT_ID | No | OAuth 2.0 client ID for MCP server authentication (generate with `openssl rand -hex 16`) | |
| YAHOO_APP_PASSWORD | Yes | 16-character app-specific password from Yahoo | |
| OAUTH_CLIENT_SECRET | No | OAuth 2.0 client secret for MCP server authentication (generate with `openssl rand -hex 32`) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_emailsA | List recent emails from a Yahoo Mail folder. Returns UIDs (permanent identifiers) and enriched metadata including size, flags, and attachment status. |
| read_emailA | Read email content using UIDs (permanent identifiers). UIDs don't change when emails are deleted. Get UIDs from list_emails or search_emails. |
| search_emailsA | Search emails using UIDs with advanced filters. Returns UIDs which are permanent identifiers that don't change when emails are deleted. Get UIDs from results for subsequent operations. |
| delete_emailsA | Move emails to Trash folder using UIDs (soft delete, recoverable). UIDs are permanent identifiers. |
| archive_emailsC | Move emails to Archive folder using UIDs for long-term storage. UIDs are permanent identifiers. |
| mark_as_readB | Mark emails as read using UIDs. UIDs are permanent identifiers. |
| mark_as_unreadC | Mark emails as unread using UIDs. UIDs are permanent identifiers. |
| flag_emailsB | Flag emails as important/starred using UIDs. UIDs are permanent identifiers. |
| unflag_emailsB | Remove flag/star from emails using UIDs. UIDs are permanent identifiers. |
| move_emailsA | Move emails to a specified folder using UIDs. UIDs are permanent identifiers. Use list_folders to see available folders. |
| list_foldersA | List all available IMAP folders/mailboxes in your Yahoo Mail account |
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 11 tools
Each tool targets a distinct action or resource: listing, reading, deleting, searching, archiving, moving, and modifying flags/read state. There is no overlap between tool purposes; even paired operations like mark_as_read/mark_as_unread are clearly delineated.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_emails, delete_emails, move_emails) with a few verb_as_adjective variants (mark_as_read, mark_as_unread). The naming is uniform and predictable across the entire set.
With 11 tools, the server provides a focused but comprehensive set of email management operations. The count is well within the ideal range and each tool serves a clear purpose without unnecessary redundancy.
The core email lifecycle (list, read, search, organize, flag, delete) is well covered. Missing send/compose and folder management (create/rename/delete) are notable gaps, but the available operations cover the primary use case of reading and organizing emails.