@sendraven/mcp
OfficialRelated Servers
Alternatives to @sendraven/mcp
No user-submitted related servers found.
Related Servers
FlicenseAqualityFmaintenanceLets AI tools send transactional emails, check status, and manage contacts through the Model Context Protocol.2-- FlicenseNot gradedqualityDmaintenanceEnables AI agents to read, filter, send emails, and check unread counts via the Model Context Protocol using Gmail SMTP/IMAP.-

KeyID Agent Kitofficial
AlicenseNot gradedqualityDmaintenanceProvides AI agents with a free, functional email address via the Model Context Protocol without requiring manual registration. It enables comprehensive email capabilities including sending, receiving, and managing messages, contacts, and automated settings.57 npm661MIT- FlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Gmail through natural language, including search, read, send, label, and draft operations via the Model Context Protocol.-
- FlicenseBqualityBmaintenanceEnables external AI agents to read, send, and manage email over IMAP/SMTP via MCP, including inbox listing, search, drafts, scheduled/batch sending, and operations like reply, archive, and labels.303-
- FlicenseBqualityAmaintenanceEnables reading and writing email through IMAP and SMTP accounts using natural language via the Model Context Protocol.16188 npm-
TDQS
Scored across 45 tools
Most tools pair a clear verb with a specific resource, and descriptions actively call out boundaries (e.g., delete_contact vs remove_from_audience). A few near-overlaps remain, such as list_scheduled_emails overlapping with list_emails' status filter and count_segment overlapping with preview_broadcast on audience sizing, so an agent could briefly hesitate between those choices.
Nearly all names follow a snake_case verb_noun pattern, with strong list_/get_/add_ families. Minor deviations like reply_to_message, decide_approval, suppress_many, and remove_from_audience use prepositions or non-resource nouns, making the pattern mostly consistent but not perfectly uniform.
45 tools is well above the heavy range and creates a large navigation surface for an agent. Some families could be consolidated, such as list_scheduled_emails vs list_emails, send_email vs send_template_email, and add_suppression vs suppress_many, so the count feels inflated relative to the added coverage.
The set is strong for reading state, sending messages, and managing contacts/suppressions, but core lifecycle operations are missing: there is no way to create/update/delete broadcasts, templates, or automations, audiences cannot be created, and webhooks/API keys are read-only. Agents trying to set up new campaigns or templates will hit a dead end.