MCPEmails connects Gmail, Fastmail, and any IMAP inbox (iCloud, Yahoo, Zoho, Yandex, generic). Not every provider exposes the same APIs, so this table shows exactly what each one supports today.
Fastmail, iCloud, Yahoo, Zoho, Yandex, and Generic IMAP all connect over the same IMAP/SMTP transport (Fastmail and iCloud use an app-specific password) and share an identical feature set, including IMAP search syntax. The columns are shown separately for clarity.
| Feature | Gmail | Fastmail | iCloud | Yahoo | Zoho | Yandex | Generic IMAP |
|---|---|---|---|---|---|---|---|
| Core | |||||||
| Download original (.eml) | |||||||
| Read email | |||||||
| Search | |||||||
| Send email | |||||||
| Reply | |||||||
| Forward | |||||||
| Flags & state | |||||||
| Read/unread + starred flags | |||||||
| Folders & labels | |||||||
| Folders | |||||||
| Labels / tags | |||||||
| Move | |||||||
| Copy | |||||||
| Delete | |||||||
| Delete / trash | |||||||
| Permanent delete (expunge) | |||||||
| Drafts | |||||||
| Drafts (create / edit / send) | |||||||
| Contacts | |||||||
| Contact search (live scan) | |||||||
| Scheduling | |||||||
| Scheduled send | |||||||
| Signatures | |||||||
| Signatures (auto-applied on send) | |||||||
| Search | |||||||
| Search syntax | Gmail | IMAP | IMAP | IMAP | IMAP | IMAP | IMAP |
Gmail folders vs labels: Gmail uses a flat label system rather than hierarchical folders. "Move" is implemented as label add/remove. Native copy is not available via the Gmail REST API.
Permanent delete: Gmail moves to Trash when you delete, and permanent expunge is not exposed by their APIs. IMAP providers (Fastmail, iCloud, Yahoo, Zoho, Yandex, Generic) support both trash and hard expunge.
Contact search (live scan): All providers support contact_search, which finds matching correspondents with a live, header-only scan of a recent window of your matching mail. There is no contacts table: nothing is stored between calls, and counts reflect only matched messages in the scanned window.
Scheduling: Supported for all providers via a server-side scheduled_sends queue. Use the schedule tool's create, list, and cancel actions. Delivery uses each provider's existing send path, so no provider-native scheduling API is required.
Signatures: A per-inbox signature is appended server-side on every send, reply, forward, draft, and scheduled message. This works on all providers. Signatures support rich HTML formatting (bold, italic, headings, lists, colors, alignment, links) and a hosted logo/image; set them in the dashboard rich editor or via the signature MCP tool (which accepts signature_html). Images are referenced as hosted https URLs and render across every provider, though some clients (e.g. Gmail) may hide them until the recipient clicks "display images", which is normal for any hosted-image signature. Use signature_reply_mode to control whether the signature appears on replies and forwards. Per call, pass include_signature: false on email_compose or draft to skip it.
Free plan: one connected inbox, forever, no card required.