mailwarden
Related Servers
Alternatives to mailwarden
- AlicenseBqualityDmaintenanceManage your emails effortlessly with a standardized interface for drafting, sending, retrieving, and organizing messages. Streamline your email workflow with complete Gmail API coverage, including label and thread management.64732 npm65MIT
- AlicenseNot gradedqualityBmaintenanceGmail MCP server — scope-gated tools (readonly / send / modify), path jails for attachments + downloads, hardened OAuth credentials, Sigstore-signed releases.490 npm18MIT
- AlicenseNot gradedqualityCmaintenanceRemote MCP server on Cloudflare Workers that exposes multiple Gmail accounts to Claude, replicating Anthropic's built-in Gmail connector with an added account parameter.283 npmMIT
Related Servers
- AlicenseAqualityBmaintenanceA local MCP server that provides Gmail tools (search, read, send, draft, label management) while keeping your emails only between your machine and Google, with no third-party access.6MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables Gmail integration, allowing users to manage emails (send, receive, read, trash, mark as read) directly through MCP clients like Claude Desktop.1MIT
- AlicenseAqualityDmaintenanceA Gmail MCP server with native multi-account support, enabling management of multiple Gmail accounts from a single server instance.79MIT
- AlicenseBqualityBmaintenanceMCP server that reads and organizes several Gmail accounts (labels, filters, archiving, drafts) and can never send or delete mail.23283 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Gmail that enables searching, reading, archiving, and managing email from any MCP client.24 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA standardized MCP server for managing Gmail, including sending, drafting, labels, threads, and settings via OAuth2 authentication.MIT
TDQS
Scored across 31 tools
Every tool has a distinct resource+action target, and the descriptions carry explicit USE WHEN / DO NOT USE sections that preempt exactly the confusions that would otherwise exist (list_subscriptions vs triage_digest vs follow_ups; list_unsubscribe vs unsubscribe vs bulk_unsubscribe; archive vs modify_labels remove INBOX; bulk_modify vs bulk_unsubscribe). Even the near-synonym pairs (mark_read/mark_unread, snooze/unsnooze/sweep_snoozed, undo_bulk_modify vs bulk_modify) are cleanly bounded by direction or by requiring an undo plan.
Consistent snake_case throughout, with a strong verb_noun pattern for most of the surface (list_labels, get_thread, create_filter, modify_labels, download_attachment, bulk_unsubscribe). A handful of bare verbs/nouns break the pattern (search, archive, trash, snooze, unsubscribe, what_changed, follow_ups), but they remain readable and unambiguous in context.
31 tools is heavy by any measure, though the domain (full mailbox triage, labeling, filters, snooze, attachments, unsubscribe, bulk operations with undo) genuinely spans that much surface. Several clusters could be consolidated — mark_read/mark_unread, archive/trash/untrash, and unsubscribe/bulk_unsubscribe all mirror single-call list variants — so the count is at the upper edge of justified.
Coverage is unusually complete: read/search/thread fetch, full label and filter CRUD, archive/trash/restore, snooze lifecycle with sweep, attachment read/download, thread export, incremental history, bulk operations with dry-run, preview tokens and exact undo. Gaps are minor and partly deliberate (no send/reply/forward — explicitly documented as an anti-exfiltration stance; no draft tools, no empty-trash/permanent delete).