Claude Code SendGrid Setup: A Non-Developer’s Walkthrough
A plain-English Claude Code SendGrid walkthrough: sign-up, sender verification, API key permissions and a test email, plus who SendGrid suits best.
Quick answer
A Claude Code SendGrid setup takes five steps: create a SendGrid account, authenticate your domain by adding four DNS records, create an API key with Mail Send access, ask Claude Code to store the key safely and write the sending code, then send a test. SendGrid’s free trial allows 100 emails a day for 60 days.
Last checked: October 2026
On this page
Claude Code has suggested SendGrid for your project's emails, you've opened the SendGrid dashboard, and now you're looking at sender identities, DNS records and API key permissions. If that sounds familiar, this Claude Code SendGrid walkthrough is for you.
You'll see what SendGrid is and what it costs, then set it up step by step, with plain-English messages to send Claude Code along the way. We'll slow down on the two parts that confuse most people, and finish with an even-handed look at whether SendGrid or SimpleSends fits you better.
You won't write any code. Every step is either a few clicks in SendGrid or a message to Claude Code.
What is SendGrid?
SendGrid is an email service that sends email for your project, from your own domain. It's owned by Twilio, and its website now lives on twilio.com. It handles both transactional emails (the ones your project sends automatically, like password resets and receipts) and, through a separate product, marketing campaigns.
Your project can't deliver email by itself. Claude Code writes the code that decides when an email should go out, and a transactional email service like SendGrid does the delivering.
SendGrid is built for developers and marketing teams. It's mature, it sends at huge scale, and it offers features bigger senders need, such as dedicated IP addresses. Here's what the Email API costs:
| Plan | Price | Good to know |
|---|---|---|
| Free trial | $0 for 60 days | 100 emails a day, no credit card needed |
| Essentials | From $19.95 a month | 3 days of searchable email activity |
| Pro | From $89.95 a month | 7 days of activity, a dedicated IP, subusers and single sign-on |
| Premier | Custom pricing | For very high volumes |
Prices checked October 2026 on SendGrid's pricing page. Taxes and overage charges may apply.
There's no permanent free plan, so plan for Essentials once your trial ends.
The Claude Code SendGrid setup, step by step
To set up SendGrid with Claude Code, you create an account, authenticate your domain, create an API key, hand the key to Claude Code to store and use, and send a test. Expect to spend most of your time on the domain step.
-
Create your SendGrid account. Sign up at signup.sendgrid.com. No credit card is needed for the trial.
-
Authenticate your domain. This proves you own the domain your emails come from, such as yourcompany.com. In SendGrid, go to Settings, then Sender Authentication, and under Domain Authentication choose Get Started. Fill in:
Setting What to choose Which DNS host do you use? The company where you manage your domain's settings, or "I'm not sure" Brand the links for this domain? No, for now (you can add it later) Domain You Send From yourcompany.com, with no "www" Use automated security Leave it checked SendGrid then gives you four DNS records to add. DNS records are settings that tell the internet how your domain works. Add them where you manage your domain, then come back and choose Verify. Changes can take up to 48 hours to show up. If your domain is with GoDaddy, SendGrid can add the records for you. For help with this step at any company, see our guide to verifying a domain for email or SendGrid's own domain authentication guide.
-
Create an API key. An API key is a secret code your live project uses to prove it's allowed to send through your account. Go to Settings, then API Keys, and choose Create API Key. Name it after your project, choose Custom Access, and turn on Mail Send. Copy the key as soon as it appears, because SendGrid shows it only once.
-
Ask Claude Code to store the key and write the sending code. Your key belongs in a private settings file called a .env file, and in your hosting platform's settings, never in the code itself. Each saved setting there is called an environment variable. Here's where API keys should go and why.
Tell Claude Code I've set up SendGrid for my transactional emails and created an API key with Mail Send access. My sending address is hello@yourcompany.com. Please set up a safe place for the key in my project, tell me exactly where to paste it, and remind me where to add it in my hosting settings. Then add whatever my project needs to send email through SendGrid.
What to expect: Claude Code adds a spot for the key, tells you where to paste it, and adds a small piece of sending code. It may ask before installing anything. That's normal, so approve it.
-
Send a test. Swap in your own email address:
Tell Claude Code Please send a test email through SendGrid to [your email address], from hello@yourcompany.com, with the subject "SendGrid test" and one line saying it works. Tell me if anything fails and what the error means in plain English.
What to expect: The email lands in your inbox within a minute or two. If it doesn't, Claude Code explains the error. A permissions error usually means Mail Send isn't turned on, and a sender error usually means your domain hasn't verified yet.
Our full guide to setting up SendGrid without getting lost in the dashboard has more detail on every screen.
The confusing parts: sender verification and API key permissions
These two steps trip up more people than anything else. Sender verification is confusing because SendGrid offers two ways to do it, and API keys because the permission names don't say what you need.
Sender verification
SendGrid won't send anything until it knows the "from" address is really yours. It offers two ways to prove it:
| Single sender verification | Domain authentication | |
|---|---|---|
| What you do | Fill in a form and click a link in a confirmation email | Add four DNS records where you manage your domain |
| What it covers | One email address | Any address on your domain |
| SendGrid's advice | For testing only | Use it before you go live |
Single sender verification looks easier, so many people start there. But SendGrid says it's for testing, and the form asks for a company postal address as well as your name and email. If you can get into your domain's settings, go straight to domain authentication. It also removes the "via sendgrid.net" label some inboxes show next to your name.
One common snag: some DNS companies, including GoDaddy and Namecheap, add your domain to the end of whatever you paste. If verification fails, check whether a record now ends in yourcompany.com twice. If it does, paste only the first part of the name.
API key permissions
When you create a key, SendGrid asks how much access it should have:
| Permission | What it allows |
|---|---|
| Full Access | Everything in your account |
| Custom Access | Only the areas you choose |
| Billing Access | Billing only |
| Email Address Validation Access | Checking email addresses only |
For a project that sends email, choose Custom Access and turn on Mail Send. Full Access works too, but if the key ever leaked, someone could change your whole account. A key with only Mail Send can do much less damage.
You can't see a key again after you leave the page, and SendGrid can't recover it. If you lose it, delete it and make a new one.
SendGrid vs SimpleSends: who is each one built for?
Setup is basically the same with both. Each needs an account, a verified domain, a secret key and a small piece of sending code. The difference is who each service is built for and what working with it is like once it's running.
SimpleSends is a transactional email service built for people who build with Claude Code but don't write code. You connect it to Claude Code as a connector, which is an MCP server: a standard way for AI tools to work with other services.
| SendGrid | SimpleSends | |
|---|---|---|
| Built for | Developers and marketing teams | People who build with Claude Code but don't code |
| Where day-to-day work happens | SendGrid's dashboard, plus your code | The Claude Code chat |
| Designing and writing emails | You, or Claude Code from your instructions | Claude Code, from a plain-English brief |
| Checking whether an email went out | Email activity in the dashboard (3 days on Essentials) | Ask Claude Code, and it checks the send logs for you |
| Marketing campaigns | Yes, as a separate product | No, transactional email only |
| Track record | Years of sending at very large scale | A newer service |
With either one, Claude Code doesn't take part when your live SaaS sends a real email. Your project sends it directly, using the key and sending code. With SimpleSends, the connector is what lets Claude Code set up, test and change your emails while you build.
Should you choose SendGrid or SimpleSends?
Choose SendGrid if you're comfortable in a developer dashboard, want marketing campaigns and transactional email in one place, or expect very high volumes and want features like dedicated IP addresses. It's a long-standing, reliable choice. If you're still comparing developer services, see Resend vs SendGrid or setting up Resend in Claude Code.
Choose SimpleSends if you'd rather brief Claude Code than learn a dashboard. After one sign-up, Claude Code designs, writes, builds and changes every transactional email, and checks the send logs when a user says an email never arrived. If you only need transactional email, see transactional vs marketing emails to be sure.
To connect SimpleSends:
-
Sign up on the SimpleSends website and follow the steps there to set up the address you'll send from. To send from your own domain, this includes adding a few DNS records where your domain is registered.
-
In Claude Code, open Customize, then Connectors, choose Add, then Add custom connector. Enter the name SimpleSends and the MCP server URL https://mcp.simplesends.com/mcp.
-
When Claude prompts you to connect, log in to SimpleSends.
-
Back in the Claude Code chat, send this message:
Tell Claude Code I've connected SimpleSends for all transactional email.
What to expect: Claude Code takes it from there, including adding what your project needs to send email.
Want to weigh up more options first? Our roundup of SendGrid alternatives for non-developers compares the main choices.
Frequently asked questions
Does SendGrid have an MCP server or Claude connector?
Twilio, which owns SendGrid, runs an official MCP server in public beta, and it’s listed as a Claude connector. It lets Claude Code search Twilio and SendGrid documentation. It can’t send email or change your SendGrid account, though Twilio says tools that can are planned. You still create the key and authenticate your domain in SendGrid’s dashboard.
Can I use my Gmail address as my SendGrid sender?
SendGrid shows a warning if you try to verify an address from some large inbox providers, because those emails may fail a security check called DMARC and get blocked. Send from an address on a domain you own, such as hello@yourcompany.com, instead.
Why do my emails say “via sendgrid.net”?
That label appears when your domain isn’t authenticated yet. Once you add SendGrid’s DNS records and the domain verifies, the label goes away and your emails show only your own address. If you used single sender verification to get started, switching to domain authentication fixes it.
What should I do if my SendGrid API key leaks?
Delete the key in SendGrid under Settings, then API Keys, so it stops working right away. Create a new key with the same permissions, then ask Claude Code to swap in the new key in your project and your hosting settings. If you can, tell Claude Code how the old key got out so it doesn’t happen again.
Can SendGrid send marketing emails too?
Yes. SendGrid has a separate product called Marketing Campaigns, with its own pricing, for newsletters and promotions. The Email API covered here is for transactional emails, the ones your project sends automatically when someone signs up, resets a password or pays you.
Sources (9)
- Email API Pricing (Twilio SendGrid)(checked October 4, 2026)
- SendGrid Email API and Email Marketing Campaigns (Twilio)(checked October 4, 2026)
- API Keys (SendGrid Docs)(checked October 4, 2026)
- Sender Identity (SendGrid Docs)(checked October 4, 2026)
- Authenticate a single sender (SendGrid Docs)(checked October 4, 2026)
- Configure domain authentication (SendGrid Docs)(checked October 4, 2026)
- Twilio MCP server (Twilio Docs)(checked October 4, 2026)
- Desktop application (Claude Code Docs)(checked October 4, 2026)
- Add a connector that isn’t in the directory (Claude docs)(checked October 4, 2026)
Keep reading
More on Claude Code + email →Claude Code Resend Setup: A Guide for Non-Developers
Claude Code Resend setup in plain English: the account, domain, API key and sending code, where people get stuck, and an option built for people who don’t code.
7 min read
Best MCP Servers for Claude Code (Non-Developer Picks)
The best MCP servers for Claude Code if you don’t code: our picks for email, database, payments, hosting and docs, and how to connect them in settings.
9 min read
Claude Code Transactional Emails: Plan, Design and Send
Claude Code transactional emails, start to finish: how Claude Code plans, designs, writes and builds your SaaS emails, then how your live project sends them.
11 min read