gmail-mcp-server
Related Servers
Alternatives to gmail-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables an AI agent to search, read, and create Gmail drafts for user review, with no capability to send, delete, archive, or relabel mail.4MIT
- AlicenseNot gradedqualityDmaintenanceProvides read-only access to Gmail, enabling email search, unread listing, message and thread retrieval, and draft reply preparation without sending.ISC
- FlicenseNot gradedqualityDmaintenanceEnables searching contacts, drafting, and sending emails via the Gmail API with explicit user approval required before sending.-
- AlicenseAqualityBmaintenanceEnables AI agents to search, read, and draft replies to Gmail messages and threads using least-privilege OAuth access, while never sending, deleting, labeling, or archiving mail.4MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to search, read, draft, and send Gmail messages, as well as manage labels and trash using natural language.24127 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables natural-language interaction with Gmail, including reading, searching, drafting, and managing emails, with safety features like read-only mode and bounded reads.Apache 2.0
TDQS
Scored across 4 tools
Each tool targets a clearly distinct operation: searching messages (returns IDs), listing labels, reading a single message by ID, and creating a draft. There is no plausible way to confuse search_emails with read_email since one locates and the other fetches content, and list_labels is orthogonal to all of them.
All four tools follow a strict verb_noun snake_case pattern (search_emails, list_labels, read_email, create_draft) with the verb accurately reflecting the action (search/list/read/create). No mixing of conventions.
Four tools is thin for a full Gmail integration — the surface is essentially 'read + draft'. It is not bloated, but most real email workflows would need more than this, putting it on the borderline of under-scoped.
Core read path is covered (search → read) plus labels and draft creation, but there are notable gaps: no send_email, no reply/forward, no label application or modification, no delete/archive, and no thread listing. The draft-only design may be deliberate for safety, but agents attempting to actually send a message will hit a dead end.