Home / Email for Bolt
For BoltBolt gets you from prompt to a deployed full-stack app fast. The one thing it can't hand you is email on your own domain - the hello@yourapp.com that sends your password resets and catches your contact-form leads. Mektup adds real two-way email to the domain your Bolt app already runs on, with one plain API call to send and a real inbox behind it to receive.
Most "add email to your app" guides stop at outbound: fire a request, mail goes out. That's fine for a receipt, but your Bolt app also needs to receive - the reply to a welcome email, a message from your contact form, a bounce notification. A sending-only API has no inbox behind your address for any of that to land in. Mektup runs real mail infrastructure, so hello@yourapp.com is both the address you send from and a real mailbox you (or your app) can read.
// from your app's server route or serverless function const res = await fetch("https://api.usemektup.com/v1/emails", { method: "POST", headers: { Authorization: `Bearer ${process.env.MEKTUP_API_KEY}`, "Content-Type": "application/json", }, body: JSON.stringify({ from: "hello@yourapp.com", to: "customer@example.com", subject: "You're in", text: "Welcome aboard.", }), });
It's a plain HTTPS POST, so it drops into whatever backend Bolt generated - a Node route, an edge function, a serverless handler - with no SDK to install.
Add the domain your Bolt app uses (or any domain you own) to Mektup through the dashboard or the API. You get back the exact MX, SPF, DKIM, and DMARC records.
Paste them wherever your domain's DNS lives. Only MX and TXT records change - the records serving your Bolt app (on Netlify, Vercel, or wherever you shipped it) are untouched, so the site keeps working.
Create hello@yourapp.com, generate an API key, and set MEKTUP_API_KEY in your deployment's environment variables.
Send with the snippet above. Replies and form submissions land in the same mailbox - read them in Mektup's webmail, over IMAP/SMTP, or through the API if you want them surfaced inside the app.
Mektup also has a native MCP server, so an AI coding agent can register the domain, create the mailbox, and set up sending and receiving itself - the same operations as the API, exposed as tool calls.
Getting started is free - 1 domain, 1 mailbox, 3,000 emails a month, 300 a day, and contact forms, no credit card. See the full pricing.
No. Email uses MX and TXT records; your deployed app is served through separate A/CNAME records. They're independent, so you add Mektup email on the same domain without touching how or where the app is hosted.
No. Mektup's send endpoint is one JSON POST request that works from any backend or serverless function with plain fetch(). See the full REST API reference.
Yes. A Mektup mailbox is a real inbox, so contact-form leads and customer replies arrive somewhere real - read them in Mektup's webmail, over IMAP/SMTP, or through the API to power a support view inside your app.