Skip to content
Beta

Integrations for everything you ship

Frameworks, auth, AI builders, agents, tests and mail apps. Guides were run end to end; a tile that works today opens its snippet; coming soon means not built yet.

Guide6
We ran it end to end. A page with the steps, the code and a capture.
Works today28
Works now over SMTP, the API or MCP. The tile opens the snippet.
Coming soon3
Not built yet. Listed so you know it is planned.

The directory

37 tools

Frameworks11

  • GuideNext.jsSend from a route handler with the Resend SDK, the mailbay SDK or fetch.via API
  • GuidePythonCreate an inbox, wait for a code, send and read status with requests.via API

Auth4

AI builders5

AI agents6

Automation3

  • Coming soonZapierA Zapier app is planned. Not built yet.via API
  • Coming soonMakeA Make app is planned. Not built yet.via API

Testing2

Mail apps3

Email SDKs3

  • Coming soonmailbay (Node SDK)Our typed Node and edge SDK is written and documented; it is coming to npm.via SDK

Not listed? It still works.

Anything that can send over SMTP or make an HTTP request can use Mailbay. These are the two settings every tile above is built on.

SMTP

Host
smtp.mailbay.dev
Port
465 (TLS) or 587 (STARTTLS)
Username
mailbay
Password
An API key with sending access (mb_live_...)
From
Any address on a domain verified in the project
The API: POST /v1/emails
curl https://api.mailbay.dev/v1/emails \
  -H "Authorization: Bearer $MAILBAY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"from": "Acme <noreply@acme.com>", "to": "ada@example.com",
       "subject": "Welcome", "text": "Thanks for signing up."}'

The body is Resend compatible. Errors come back as JSON with a code, a message and a fix. Details in the Emails API docs. App built by an AI builder? Use the copy paste prompt.

How we test them

Every guide here was run end to end against a Mailbay stack before we wrote it up: the config is the config we used, the code is the code we ran, and the screenshots are captures of that run with test addresses and masked keys. Agent clients connect through the MCP server; everything else uses SMTP or the REST API described in the docs.

A tile marked works today says in its drawer what we ran and when, or that we have not run it yet. Product names and logos identify the tools Mailbay works with; they do not mean those companies endorse or partner with Mailbay. Logos are trademarks of their respective owners.

Switching from another service? The alternatives pages cover AgentMail, Mailosaur and Resend, and what changes in each move. What shipped recently is in the changelog. Not sure where to start? See who Mailbay is for.

Join the beta

Mailbay is in private beta and free while the beta runs: inboxes, sending, your own domains and MCP. We invite people in small batches and read every note on the form.

Join the betaRead the docs