MailKite
OfficialRelated Servers
Alternatives to MailKite
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEmail for AI agents. Create inboxes, send and receive emails without phone or CAPTCHA.2 npmMIT
- -licenseCqualityCmaintenanceGives on-the-fly inboxes to AI agents. Agents / LLM's can send, receive, and take action in isolated inboxes. Built for AI unlike Gmail. Check us out at agentmail.to10101-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to autonomously create email accounts, verify domains, send and receive emails, and monitor delivery events without requiring human sign-up or payment.1-
- AlicenseNot gradedqualityBmaintenanceOpen-source, self-hosted Inbox-as-a-Service API for AI agents. It enables agents to manage email inboxes, send/receive emails, search messages, and wait for replies via REST or MCP.29Apache 2.0

Sendmux Email Inbox API +official
AlicenseAqualityAmaintenanceSendmux is an email inbox API and email API for AI agents. Use this MCP server to let authorised agents work with Sendmux mailboxes, inbound email, clean JSON parsing, webhooks, outbound sending, provider routing, logs, billing, and team controls.3265MIT
AgenticMailofficial
AlicenseAqualityAmaintenanceReal email and SMS for AI agents. Run a local mail server with disposable inboxes — agents send and receive real email, fetch verification codes, and drive a real inbox without going through any third-party email API.100225MIT
TDQS
Scored across 92 tools
Most tools target distinct resources and actions with detailed descriptions that prevent confusion. A few overlapping pairs exist (e.g., send_event vs start_sequence, agent vs route), but the descriptions explicitly clarify when to use each.
The vast majority follow a consistent `mailkite_verb_noun` pattern (list_domains, create_trigger, delete_broadcast). A few outliers like `agent`, `route`, `me`, and `semantic_search` break the convention, but they are rare and the pattern is otherwise strong.
At 92 tools, the surface is far beyond the typical 3–15 range and even exceeds the 25+ threshold for 'too many'. While the broad scope of a full email platform justifies many endpoints, this count still overwhelms an agent's selection process and feels excessive.
The toolset covers a wide range of email functionality (sending, sequences, templates, domains, webhooks, lists, broadcasts, suppressions, keys). However, notable gaps exist: templates lack update/delete, routes have no update or get, and there is no standalone contact management beyond list membership.