A1 Gmail MCP
Related Servers
Alternatives to A1 Gmail MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Gmail through natural language, including sending, reading, searching, labeling emails, managing attachments, and performing thread operations.3MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with Gmail through natural language, supporting email sending/reading, searching, draft management, label organization, and batch operations with secure OAuth authentication.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Gmail through natural language interactions, including sending, reading, searching emails, and managing labels with auto authentication support.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Gmail through natural language interactions with auto-authentication, including sending, reading, searching, and organizing emails and labels.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage Gmail emails, including sending, searching, and organizing with labels and attachments via OAuth2.28 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to send, read, list, and reply to emails via the Gmail API.Apache 2.0
TDQS
Scored across 24 tools
Tools are cleanly separated by resource and action: message vs thread vs draft vs label vs trash each have their own verb set, and the auth tools are explicitly sequenced (setup_instructions → set_client → start_login → finish_login). A few pairs need the descriptions to disambiguate — setup_instructions vs set_client vs start_login, and list_messages vs list_threads — but the descriptions make the boundaries explicit. No two tools genuinely appear to do the same thing.
Overwhelmingly consistent snake_case verb_noun (get_message, list_drafts, update_draft, send_draft, manage_labels, modify_thread). Minor deviations are noun-style or bare-verb names: auth_status, setup_instructions, logout, raw_request. The pattern is still predictable enough that an agent can guess names correctly.
24 tools sits at the upper end of the reasonable band, but the surface is well-partitioned: ~6 onboarding/auth tools plus 18 Gmail operations covering messages, threads, drafts, labels, trash and an escape hatch. Each tool has a distinct job, though the multi-step OAuth onboarding block is heavy relative to the mail operations. Slightly over-scoped but not bloated.
Near-complete lifecycle coverage: full draft CRUD (create/list/get/update/send/delete), message and thread read/modify/trash/restore, label management plus label application, profile, and auth lifecycle including logout. Intentional omissions (no permanent delete, no attachment byte download) are documented and covered by manage_trash safety and the raw_request escape hatch.