mailmcp
Related Servers
Alternatives to mailmcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables Claude and ChatGPT to read, search, and organize mail in a user's own email account, including folders, threads, attachments, drafts, and optional sending, with per-user permission levels and OAuth-secured remote connections.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to search, read, and draft email across multiple linked Gmail and Google Workspace mailboxes per user, with per-user isolation and Google sign-in. Self-hosted, drafts-only today, so users send from Gmail themselves.MIT
- AlicenseAqualityBmaintenanceEnables searching, reading, drafting, and sending email across multiple Gmail accounts from Claude Desktop, Claude Code, and ChatGPT, including cross-account search and threaded replies.14985 npmMIT
- AlicenseNot gradedqualityCmaintenanceConnects Claude to any IMAP/SMTP mailbox so it can list folders, read and search messages, fetch attachments, and create or send drafts, with read/draft/send permission modes and built-in OAuth. Designed for mail hosts that lack a native Claude connector.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to search, read, send, reply to, organize, and bulk-delete email across multiple IMAP/SMTP mailboxes, with connection pooling and AES-256-encrypted credential storage. Supports 15+ providers through a web-based setup wizard and works with Claude, Cursor, and any MCP client.931 npmMIT
- AlicenseAqualityBmaintenanceHosted email for AI agents. Connect Gmail, Outlook / Microsoft 365 or any IMAP mailbox to Claude, ChatGPT, Cursor and other MCP clients, then read, search, send, organize, draft, schedule and auto-triage mail. Email is fetched live and never stored. Free for 1 inbox.2314AGPL 3.0
TDQS
Scored across 33 tools
The set has many adjacent tools whose boundaries rely heavily on long descriptions: search vs search_messages, fetch vs get_message, create_draft vs reply_draft, and send_message vs reply_send vs send_draft can still be confused. Most tools do have distinct roles once the description is read, but the overlap is substantial for an agent selecting a tool quickly.
Most names use snake_case and many follow verb_noun patterns, but the set mixes bare verbs such as fetch, search, triage, digest, unsubscribe, and snooze with noun-oriented and compound names like wake_snoozed. The convention is readable but not predictable enough for a strong 4 or 5.
With 33 tools, the surface is well past a comfortable scoped set for an MCP server and contains many specialized workflows such as bulk actions, templates, signatures, snoozing, follow-ups, and upload links. The breadth may be justified for a full mail client, but it is heavy for agent tool selection and risks overload.
The surface covers a broad email lifecycle: accounts, folders, search, message retrieval, attachments, drafts, replies, sending, forwarding, modify/trash, bulk operations, templates, signatures, follow-ups, snoozing, triage, and digest. Some gaps remain, such as explicit draft editing/listing and folder creation, but core workflows are well covered.