MailKite
Connect an external agent through MCP or signed inbound JSON, confine its email access, and keep outgoing messages behind an application approval step. These guides cover the bring-your-own-agent path; built-in inbox agents are a separate beta capability.
Start with the first guide, then choose a sending, receiving, or feedback task. Each walkthrough identifies permissions, operational checks, and the boundary between the service and MailKite. Refer to the official MailKite documentation for current platform requirements.
Explore the guides
Connect an agent to MailKite with bounded email access
Choose hosted MCP or an SDK-backed application, verify a dedicated domain, and avoid handing an agent unrestricted account credentials.
Triage MailKite incoming email before invoking an agent
Verify the webhook with the MailKite SDK, durably deduplicate incoming work, and pass bounded untrusted content to the model.
Send a reviewed agent reply through MailKite
Separate model-generated proposals from send authorization and submit only the exact approved reply through the MailKite SDK.