Resend in Claude Code: Setup Steps and an Option for Non-Developers

You asked Claude Code to make your SaaS send emails, and it suggested Resend. Now you're partway through a Claude Code Resend setup, looking at DNS records and API keys, and want to know what's left to do.

This guide walks through what Resend is, every step of setting it up with Claude Code, and the spots where non-developers usually get stuck. At the end, you'll see when SimpleSends, an email service built for people who don't code, is the better fit, and when Resend is.

What is Resend, and does it work with Claude Code?

Resend is a transactional email service built for developers, and yes, it works well with Claude Code. Transactional emails are the ones your SaaS sends automatically when someone does something: a welcome email after sign-up, a password reset link, a receipt.

Resend has its own MCP server. MCP (Model Context Protocol) is a standard way for AI tools to connect to outside services; you can read more in what MCP is, in plain English. Resend hosts its server for you, and you connect by signing in to your Resend account. Once connected, Claude Code can send test emails, add and check domains, create API keys, manage email templates and look at request logs, all from the chat.

Resend also offers an official Claude Code plugin that bundles that server with Resend's own instructions for Claude, and a one-click connector in Claude's connector directory.

One thing to understand early: the connector is for while you're building. When your SaaS is live and a customer resets their password at 3am, Claude Code isn't involved. Your project sends that email to Resend directly, using a secret key and a small piece of sending code.

Resend's prices, checked October 2026:

Paid plans charge $0.90 for each extra 1,000 emails. Prices checked October 2026.

What does a Claude Code Resend setup involve?

A Claude Code Resend setup has four pieces: an account, a verified domain, an API key and sending code. Every transactional email service needs these same building blocks, SimpleSends included. Here's how each one works with Resend.

1. Create a Resend account. Sign up on Resend's website. This part happens in your browser, not in the chat.

2. Connect Resend to Claude Code (optional, but helpful). In Claude Code, open Customize, then Connectors. Find Resend in the connector directory, or choose Add, then Add custom connector, and enter the server URL https://mcp.resend.com/mcp. When prompted, sign in to Resend and approve access. Resend's own Claude Code page is written for developers, so the on-screen route here is usually easier to follow.

3. Verify your sending domain. Your domain is your web address, like yourcompany.com. Verifying it proves you own it, so inbox providers trust your emails. Resend recommends sending from a subdomain such as mail.yourcompany.com, which keeps your email reputation separate from your main domain. (See how to choose a sending domain.)

   You add Resend's records in your DNS settings, which live wherever your domain is registered or managed. DNS is the internet's address book. Resend generates the exact values; the records look like this:

   Type	Name	What it's for
   TXT	resend._domainkey	DKIM: a digital signature proving emails really came from you
   MX	send	SPF: lets bounce messages come back to Resend
   TXT	send	SPF: lists Resend as allowed to send for your domain

   Verification often finishes within 15 minutes, though it can take up to 72 hours. If your domain is on Cloudflare, Resend can add the records for you after you sign in to Cloudflare. For a full walkthrough, see how to verify a domain for email.

4. Create an API key. An API key is a secret password your project uses to prove it's allowed to send through your account. (Here's what an API key is.) You can create one in Resend's dashboard, or, with the connector set up, ask Claude Code to create it. Resend suggests "Sending access" rather than full access. You can only view a key once, so it needs storing straight away: in your project's .env file (a private settings file) and in your hosting platform's settings. Read where to put API keys before you paste one anywhere.

5. Have Claude Code write the sending code, then test it. Claude Code adds Resend's SDK (a ready-made toolkit for talking to Resend) and the code that sends each email.

I've set up Resend and verified mail.yourcompany.com. Please add email sending to my project using Resend, with the key stored safely. Start with a welcome email for new sign-ups, and send a test to me so I can see it.

Expect Claude Code to explain what it's adding, ask for anything it's missing, and send you a test email. For a slower, screen-by-screen version of these steps, see how to set up Resend.

Where do non-developers get stuck with Resend?

Most people get stuck on the DNS records and the API key, not on Claude Code. These are common snags:

What is working with Resend like day to day?

After setup, you'll use Resend's dashboard and Claude Code side by side. The dashboard is where you check sent emails, manage keys and domains, and edit templates. With the connector, you can also ask Claude Code to look at request logs, update a template or send a test.

Resend is polished and popular, and you can get it working without writing code yourself. But its docs, examples and dashboard are made for people who write code. You'll meet terms like SDK, React Email and webhooks, and you'll often need to know what to ask Claude Code for.

How is SimpleSends different for people who don't code?

SimpleSends works much like Resend under the hood: you still need an account, a verified domain, a key and sending code. The difference is who it's built for and what working with it feels like.

• Built for people who aren't developers. Sign-up, connecting and help are written in plain English, without developer jargon.
• Everything after sign-up happens in the chat. You don't need a dashboard for day-to-day work. You brief Claude Code the way you'd brief a person.
• Claude Code does the whole job. It designs, writes, builds and changes every transactional email, from welcome emails to receipts. See how this works in transactional emails in Claude Code.
• Problems get sorted in plain English. Claude Code can read your send logs and delivery status through SimpleSends, so "did my user get the reset email?" is a question you ask in the chat. (More on checking whether an email was sent.)

To connect SimpleSends:

1. Sign up on the SimpleSends website and follow the steps there to set up the email address you'll send from. To send from your own domain, this includes adding a few DNS records where your domain is registered.
2. In Claude Code, open Customize, then Connectors, choose Add, then Add custom connector. Name: SimpleSends. MCP server URL: https://mcp.simplesends.com/mcp
3. When Claude prompts you to connect, log in to SimpleSends.
4. Back in the Claude Code chat, tell Claude Code you've connected it.

I've connected SimpleSends for all transactional email. Please work out which emails my SaaS needs, design and write each one in a friendly style that matches my site, and show me previews before anything goes live.

Resend or SimpleSends: which should you choose?

Choose Resend if you're comfortable with developer tools or want to edit code yourself. Choose SimpleSends if you don't code and want to handle email by talking to Claude Code.

Still weighing options? Compare Resend vs SendGrid and Resend vs Loops, or browse Resend alternatives for people who don't code.