Yahoo Mail MCP Server
Related Servers
Alternatives to Yahoo Mail MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables reading, searching, composing, and managing Yahoo Mail emails via IMAP with OAuth support for both local and remote MCP clients.11 npmISC
- AlicenseAqualityBmaintenanceEnables MCP clients to read, search, and manage a Yahoo Mail mailbox over IMAP and send or forward messages over SMTP, with multiple accounts selectable per call and writes defaulting to drafts, trash, or dry-runs until explicitly confirmed.13MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Yahoo Mail over IMAP+SMTP that enables AI assistants to manage emails fully—listing, reading, searching, threading, flagging, moving, archiving, handling attachments, and sending/reply/forward/draft—using an app-specific password.MIT
- AlicenseAqualityBmaintenanceAn MCP server that provides full email management for Yahoo Mail via IMAP, including tools to list, read, search, delete, archive, flag, and move emails, with secure OAuth authentication and support for local and remote deployments.111MIT
- AlicenseAqualityFmaintenanceProvides full email management for Yahoo Mail via IMAP, including listing, reading, searching, deleting, archiving, and flagging emails.1127MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to read, organize, draft, and send Yahoo Mail email with user approval, integrating with various clients via a remote MCP endpoint.1-
TDQS
Scored across 15 tools
Tools target distinct actions on UIDs or drafts; delete/archive/move overlap slightly because delete and archive are specialized moves, but descriptions clarify intent. No two tools are indistinguishable.
Most tools follow verb_noun (list_emails, create_draft), but mark_as_read/mark_as_unread use a different pattern and read_email is singular while list/search use plural. Still readable and predictable overall.
15 tools is well-scoped for an email management server, covering message retrieval, flags, folders, attachments, and drafts without excessive surface.
Core read/manage/draft workflows are covered, but there is no send operation—agents can only create drafts—and no folder creation/deletion. This is a notable gap for an email client, though the draft-only design may be intentional.