gmail-read-mcp
Related Servers
Alternatives to gmail-read-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables read-only access to a single pinned Gmail mailbox through the Gmail API, allowing users to search and read messages and threads, list labels, and save attachments to local files without sending, modifying, or deleting mail.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides read-only access to Gmail, enabling email search, unread listing, message and thread retrieval, and draft reply preparation without sending.239 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables reading, sending, archiving, and managing Gmail emails and labels through Google OAuth authentication, acting as an OAuth proxy to the Gmail API.239 npm12MIT
- AlicenseNot gradedqualityCmaintenanceEnables searching and reading Gmail messages, listing labels, and creating email drafts without sending or deleting emails.298 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only Gmail access via MCP, allowing users to list and retrieve email messages with query and pagination support.4MIT
- AlicenseAqualityBmaintenanceEnables authenticated Gmail access across several Google accounts at once, unifying them into a single mailbox view for searching, reading whole threads and attachments, and organizing messages with archive, read-state, spam, label and filter operations. Also composes and manages drafts and sends, replies, forwards mail only through an explicit send action, with opt-in safety policies and audit logging.14Apache 2.0
TDQS
Scored across 2 tools
The two tools, list_emails and read_email, have clearly distinct purposes—one for enumerating emails and the other for fetching full details of a specific email. There is no overlap or confusion possible.
Both tool names follow the consistent verb_noun pattern: 'list_emails' and 'read_email'. The naming is predictable and aligns with the server's read-only scope.
With only two tools, the server is minimal but well-suited for a read-only Gmail interface. While the count feels thin relative to typical multi-purpose servers, the narrow scope justifies the small surface.
For a read-only mail server, the two tools cover the core workflow: listing emails with metadata and reading a full email by ID. There are no apparent gaps that would impede an agent from retrieving email data.