Drin MCP Server
Related Servers
Alternatives to Drin MCP Server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityAmaintenanceEnables agents to create and manage durable email workflows, templates, contacts, and enrollments over MCP.8 npm2AGPL 3.0- AlicenseNot gradedqualityBmaintenanceEmail capabilities for AI agents to receive, read, reply, and send through MCP.0ISC
- 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-
- AlicenseAqualityDmaintenanceEmail infrastructure for AI agents — create inboxes, send/receive email, search messages, and manage threads via MCP tools.109 npm2MIT
- AlicenseAqualityBmaintenanceEnables AI agents to send, receive, and reply to email through dedicated thread-aware mailboxes, with sandbox testing and compatibility across MCP clients.956 npmMIT

InboxAPI CLIofficial
AlicenseNot gradedqualityBmaintenanceProvides an AI agent with its own email address to send, receive, and manage emails via MCP. No email server setup required.39 npm12MIT
TDQS
Scored across 89 tools
Each tool targets a distinct resource and action, even at 89 tools. The descriptions clearly separate overlapping operations like render_template (saved templates) and preview_template (drafts).
All tool names follow a consistent verb_noun pattern with snake_case (e.g., list_templates, create_campaign, send_email). No mixed conventions or vague verbs.
89 tools is extremely high for an MCP server, likely overwhelming for agents. While the domain (email platform) is broad, the count far exceeds typical well-scoped servers (3-15 tools) and even the generous upper bound.
The tool surface covers nearly every aspect of the email platform: sending, receiving, templates, domains, contacts, campaigns, automations, webhooks, integrations, and more. Minor gaps like missing update_inbox or update_domain are negligible.