Connect a provider
Wire up Resend or SendGrid, verify a domain, and add a sender.
Before you can send, a project needs a delivery provider, a verified sending domain, and at least one sender address. All of this happens in the dashboard — provider credentials never travel through the API or MCP.
Add provider credentials
Open Settings → Provider and choose Resend or SendGrid. Paste the provider API key. It's validated against the provider and stored encrypted — it's never logged and never leaves the server.
Verify a sending domain
Open Settings → Domains, add your domain, and publish the shown DNS records (SPF/DKIM from the provider). Once the provider reports the domain verified, it can send. A from-address must resolve to a verified domain or the send is rejected.
Add a DMARC record (recommended)
The provider records cover SPF and DKIM, but not DMARC — publish it yourself in the same DNS session:
_dmarc.mail.acme.com TXT "v=DMARC1; p=none;"Gmail and Yahoo's bulk-sender rules require a DMARC record on the From domain,
and Gmail only offers recipients "unsubscribe" instead of "report spam" when
the sender is fully authenticated — DMARC turns complaints into harmless
unsubscribes. A record on the root domain (_dmarc.acme.com) also works.
Start with p=none (monitor only); add rua=mailto:[email protected] for
aggregate reports and tighten to p=quarantine once they look clean. DMARC is
advisory here: the dashboard and verifyDomain surface its status
(found / missing), but it never blocks verification or sending.
Add a sender
Add a sender address on the verified domain (e.g. [email protected]) and,
optionally, set it as the project default. Sends with no explicit from use the
default sender.
Provider keys are per-project and set only on the settings page. The
email_connect_provider MCP tool returns this settings URL rather
than accepting a key — a human always enters credentials.