Gmail MCP
Related Servers
Alternatives to Gmail MCP
- AlicenseNot gradedqualityCmaintenanceStreamable HTTP MCP server for Gmail that enables AI agents to search threads, read messages, manage drafts, and organize the inbox via OAuth authentication.181 npm10MIT
- AlicenseNot gradedqualityCmaintenanceA self-hostable Gmail MCP server that enables Gmail search/read, sending, replies, drafts, labels, and attachment downloads via MCP tools with OAuth authorization. Supports stdio and streamable HTTP transports.MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceA local-first MCP server for managing multiple Gmail accounts with separate OAuth grants, supporting search, retrieval, labels, drafts, and attachments while deferring direct send and destructive actions for safety.MIT
- AlicenseNot gradedqualityBmaintenanceConnects any number of Gmail accounts to Claude or another MCP client, enabling search, reading, sending, drafting, labeling, and trashing mail across one account or all of them at once. Runs entirely locally, so OAuth tokens never leave the user's machine.MIT
- AlicenseNot gradedqualityBmaintenanceA local MCP server that gives Claude access to multiple Gmail accounts simultaneously for search, read, draft, send, label, and a scheduled cross-inbox digest, with enforced send policies per mailbox.MIT
- AlicenseNot gradedqualityCmaintenanceA self-hosted MCP server that gives an AI client read, search, triage, drafting, attachment/export and label-management access to several Gmail or Google Workspace accounts at once, with each call naming an explicit account. Sending is disabled unless armed twice, mail deletion is impossible, and tokens, exports and audit data stay local.MIT
- AlicenseNot gradedqualityDmaintenanceA read-only, multi-account Gmail MCP server for Claude Code that lets Claude search threads, read messages, and list labels across authorized Gmail accounts.181 npmMIT
- FlicenseNot gradedqualityBmaintenanceSelf-hosted Gmail gateway MCP server that enables searching and fetching emails from multiple authorized Gmail mailboxes via a single backend authorization boundary.-
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action: search_messages vs get_message vs get_thread are clearly delineated by the descriptions, and create_draft vs send_draft vs modify_message_labels have separate, non-overlapping purposes. An agent can reliably pick the right tool without confusion.
All tools follow a consistent snake_case verb_noun pattern (list_accounts, search_messages, get_message, create_draft, send_draft, modify_message_labels). No mixing of conventions or vague verbs.
Nine tools is well-scoped for a Gmail server, covering accounts, reading, searching, attachments, labels, and the draft/send/modify workflow without bloat or redundancy. Each tool clearly earns its place.
Read, search, thread, attachment, label, and draft/send workflows are well covered, with archive/read/star achievable via modify_message_labels. However, there is no explicit delete/trash operation and no label creation/management, leaving minor gaps for a full Gmail lifecycle.