@mcp-z/mcp-gmail
Related Servers
Alternatives to @mcp-z/mcp-gmail
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA 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
- 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 gradedqualityBmaintenanceMCP server for Gmail that enables searching, reading, archiving, and managing email from any MCP client.46 npm1MIT
- AlicenseNot gradedqualityDmaintenanceStreamable HTTP MCP server for Gmail enabling search, read, draft management, and inbox organization.22 npmISC
- FlicenseNot gradedqualityDmaintenanceMulti-account Gmail MCP server for reading threads, managing labels, and creating drafts across multiple Gmail accounts.-
- AlicenseNot gradedqualityAmaintenanceMCP server that reads and organizes several Gmail accounts (labels, filters, archiving, drafts) and can never send or delete mail.141 npmMIT
TDQS
Scored across 15 tools
Most tools are clearly scoped by resource prefix (message-, label-, account-), but categories-list and labels-list both surface label-like data and could be confused. message-send and message-respond also overlap slightly, though the descriptions clarify the reply behavior.
Names follow a consistent resource-action pattern with lowercase hyphenation, such as message-get, label-add, and account-list. Minor inconsistencies exist: labels-list and messages-export-csv use plurals while label-add and message-get use singular, and account-me uses a pronoun instead of a verb.
15 tools sits at the top of the well-scoped range, but each tool covers a meaningful operation across accounts, labels, and messages. There is no obvious filler or redundancy that makes the set feel bloated.
Core message operations are covered well (send, get, search, reply, trash, mark-read), but the label lifecycle is incomplete: there is no way to create a label, and label-add has no counterpart for removing a label from a message. Trash also lacks a restore operation.