Integrations

MailKite works with any app that speaks SMTP — point it at smtp.mailkite.dev and you're sending. For platforms that support webhooks, you can also receive inbound email as clean JSON at your endpoint. For AI agents, connect via MCP — one command to give your agent its own inbox.

Every integration uses the same API key, the same verified domains, and the same SMTP connection details. No extra setup beyond publishing your DNS records.

AI agents — MCP-native

MailKite is MCP-native — every agent platform that speaks Model Context Protocol gets full access to MailKite's API: send email, read inbound messages, manage domains, and run inbox agents. One command to add, zero config to use.

Frameworks & SDKs

Official client libraries for every major language. Same method surface, same JSON over HTTPS — pick your stack and install.

SMTP connection details

These are the same for every platform. Your password is your API key — there's no separate SMTP credential to create.

Platform tutorials

Step-by-step guides for the most popular platforms. Each one covers sending email through MailKite, and where applicable, receiving inbound email at a webhook.

Custom integrations

Step-by-step guides for every platform. Each one covers sending email through MailKite, and where applicable, receiving inbound email at a webhook.

Don't see your platform?

If your app has an SMTP settings panel, it works with MailKite — just point it at smtp.mailkite.dev with your API key. If it uses webhooks, point them at your inbound webhook endpoint. If you're building an AI agent, add the MCP server and your agent gets its own inbox. For anything else, email us and we'll help you wire it up.

See the SMTP relay docs for the full connection reference, the client libraries for SDKs, or the Send API for programmatic sending.