gmail-mcp
Related Servers
Alternatives to gmail-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude to read, search, send, and manage Gmail messages and threads through natural language.253 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables Claude to read and manage your Gmail account, including listing, searching, sending, drafting, replying to, archiving, labeling, and trashing emails via the Gmail API.-
- AlicenseNot gradedqualityDmaintenanceEnables Gmail integration with Claude Code for reading, sending, searching emails, and managing labels through natural language.253 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables reading, sending, searching, and managing Gmail through Claude using the official Google Gmail API.89 npm3MIT
- FlicenseNot gradedqualityDmaintenanceProvides Claude with Gmail capabilities including sending emails, managing drafts, and searching messages.-
- AlicenseNot gradedqualityDmaintenanceConnects Claude Code to Gmail for reading, searching, drafting, and managing emails with features like labels, filters, and smart workflows.132 npmMIT
TDQS
Scored across 20 tools
Each tool targets a distinct resource or lifecycle stage, and the descriptions clearly separate listing from fetching, drafting from sending, and trashing from archiving. The main ambiguity is between convenience wrappers like archive, trash, and mark_read, all of which ultimately manipulate message state, but their effects are explained precisely.
The gmail_ prefix is consistent and most tools follow a clear verb_noun pattern such as list_drafts, get_message, create_label, and send_draft. A few bare-verb names like gmail_trash, gmail_archive, gmail_search, and gmail_profile deviate slightly, but the overall style remains readable and predictable.
At 20 tools, the server is on the larger side, but each tool maps to a meaningful Gmail capability covering search, messages, threads, drafts, labels, sending, and mailbox state. The count feels slightly heavy but justified for the domain rather than bloated.
The surface covers most of the email lifecycle: search, read, thread viewing, draft CRUD, sending, trash/restore, labels, and profile. Notable gaps are attachment content retrieval and label renaming, but these are minor and do not create dead ends for core workflows.