Tratto MCP Server
OfficialRelated Servers
Alternatives to Tratto MCP Server
No user-submitted related servers found.
Related Servers
AlicenseBqualityBmaintenanceEnables AI agents to send and manage email, read threaded replies, run campaigns and automations, and handle approvals through the Model Context Protocol from any compatible client.45709 npmMIT
@sendbyte/mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to send emails and manage sending domains, templates, analytics, and content checks through the SendByte platform using the Model Context Protocol.119 npmMIT- FlicenseNot gradedqualityCmaintenanceEnables AI agents to programmatically manage email outreach campaigns, leads, domains, senders, and webhook events, as well as send emails, through the Model Context Protocol over HTTP.-

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.80 npm661MIT- FlicenseNot gradedqualityDmaintenanceEnables AI agents to read, filter, send emails, and check unread counts via the Model Context Protocol using Gmail SMTP/IMAP.-
- FlicenseBqualityAmaintenanceEnables reading and writing email through IMAP and SMTP accounts using natural language via the Model Context Protocol.16615 npm-
TDQS
Scored across 2 tools
send_email and list_emails have completely distinct purposes: one initiates an outgoing email, the other retrieves a list of previously sent emails. There is no overlap or ambiguity between the two.
Both tool names follow the consistent verb_noun pattern using snake_case: send_email and list_emails. The naming is predictable and uniform.
With only 2 tools, the server feels thin for an email-related service. While the core actions of sending and listing are covered, the small number of tools is borderline and may leave users wanting more functionality.
The server provides the fundamental lifecycle of sending and listing emails, but lacks a dedicated get_email or delete_email operation. This minor gap could be worked around if list_emails returns full details, but a single-email lookup is a common need.