Dove
Related Servers
Alternatives to Dove
- -licenseNot gradedqualityNot gradedmaintenanceGoogle Calendar integration in Cursor IDE. This server enables AI assistants to manage Google Calendar events through natural language interactions.13 npm5ISC
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, manage, schedule, and analyze email across multiple IMAP/SMTP accounts through a single MCP server. Also supports drafts and templates, provider-aware labels and bulk operations, calendar extraction, real-time mailbox watching, and OAuth2 sign-in for Gmail and Microsoft 365.31 npmISC
- AlicenseNot gradedqualityAmaintenanceA self-hosted MCP server that unifies multiple IMAP/SMTP mailboxes into one agentic inbox, enabling agents to list, search, read, and send email through MCP tools.MIT
- AlicenseNot gradedqualityDmaintenanceA self-hosted, multi-mailbox MCP server that exposes IMAP/SMTP operations as tools for AI agents, enabling email management like listing folders, reading, searching, sending, and moving messages via natural language.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to work with existing IMAP/SMTP mailboxes through a native MCP endpoint, with granular token scopes for reading, searching, organizing, drafting, sending, and managing folders plus optional AI-assisted summaries and replies. Drafts are saved to real IMAP Drafts folders, and permissions are enforced by the shared mail engine.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceAn open-source MCP server that provides AI agents with secure access to read, search, and manage emails via Microsoft 365 and Gmail. It features security-first defaults like recipient allowlists and markdown content conversion to facilitate safe agent interaction with mailboxes.7Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, read, organize, and draft replies in any IMAP mailbox, with messages sent only after explicit approval. Supports multiple isolated mailboxes, OAuth-based access, and keeps no mail content in its database.5MIT
TDQS
Scored across 25 tools
Tools are largely distinct and descriptions explicitly route between close variants (get_message vs get_thread vs batch_read, send_draft vs request_send, search_messages vs digest). A few boundaries are nuanced—especially digest versus threaded search results and the generic batch_read multiplexer—but they are explained well enough to avoid most misselection.
Almost all names use consistent snake_case verb_noun patterns (list_accounts, get_message, create_draft, delete_watch, search_messages). The main deviations are digest and batch_read, which are not verb_noun names, though the overall convention remains readable and predictable.
At 25 tools this is at the heavy end of the scale; the email domain is broad and most tools earn their place across messages, drafts, requests, and watches. Still, the set is large enough to feel borderline, with some tools (batch_read, digest, separate request tools) that could potentially be consolidated or contextualized.
The surface covers the core email lifecycle very well: account/label discovery, search, reading threads and attachments, message updates/moves, full draft lifecycle, send/access requests, and watch events. Minor gaps remain, such as label creation/management, updating a watch in place, and permanent message deletion, but these are workable around or intentionally delegated.