Starter
For your first email program.
$192 billed yearly.
20,000 emails / month
Choose Starter- 5 brands · 3 seats
- 5 custom sending domains
- 500 email verifications/month
- $1.50 / 1,000 extra emails
Eight services to use instead of Resend, or alongside it, ranked first on how well each one works as an AI agent's email tool from Claude, ChatGPT, Cursor or Codex, then on six more tests, with the reason and source behind every score. Nitrosend wins: campaigns, flows and receipts on one $20 plan, run from your AI assistant.
Nitrosend is the best Resend alternative for teams that run email from an AI agent over MCP, with the top score of the eight reviewed here, 83.75 out of 100, and 9 out of 10 on working from your AI assistant. It is the only one of the eight your AI assistant, whether Claude, ChatGPT, Cursor or Codex, can sign up to and send from with no domain to verify and nobody opening a dashboard. To send email from Claude, ChatGPT, Cursor or Codex with Nitrosend, connect the hosted MCP server at api.nitrosend.com/mcp, approve the OAuth sign-in in your browser, and ask for the email: a receipt or reset goes out on that call, while a campaign or flow is saved as a draft that runs only once you approve it. Your receipts, newsletters and automated flows go out on one plan and one bill, where Resend prices marketing as a second plan by contacts. It writes every email in your brand's colors, fonts and voice. And it costs $20 a month for 20,000 emails, the same as Resend, and $650 for a million emails on Scale including overage, where Resend is $650. Bird (formerly SparkPost) comes next at 76, then Mailtrap at 74.
83.75 out of 100Total
Nitrosend
Connect Nitrosend to Claude, ChatGPT, Cursor or Codex, point Brand Kit at your site, and describe the email. Contacts are unlimited on every plan.
Free: 5,000 emails to start, then 500 a month. No credit card.
Start free76 out of 100Total
Rank 374 out of 100Total
Rank 468.5 out of 100Total
Rank 567.5 out of 100Total
65.5 out of 100Total
Rank 764.5 out of 100Total
Rank 860 out of 100Total
| What we compared | ||||||||
|---|---|---|---|---|---|---|---|---|
| Works from your AI assistant25 points | 9 out of 10 | 8 out of 10 | 6 out of 10 | 8 out of 10 | 6 out of 10 | 7 out of 10 | 6 out of 10 | 7 out of 10 |
| Receipts and newsletters on one plan15 points | 9 out of 10 | 7 out of 10 | 7 out of 10 | 4 out of 10 | 4 out of 10 | 3 out of 10 | 4 out of 10 | 2 out of 10 |
| Emails in your brand, no designer10 points | 9 out of 10 | 4 out of 10 | 5 out of 10 | 6 out of 10 | 5 out of 10 | 2 out of 10 | 5 out of 10 | 4 out of 10 |
| Free plan10 points | 7 out of 10 | 6 out of 10 | 8 out of 10 | 5 out of 10 | 7 out of 10 | 4 out of 10 | 4 out of 10 | 6 out of 10 |
| Price15 points | 8.5 out of 10 | 10 out of 10 | 9 out of 10 | 8 out of 10 | 8 out of 10 | 10 out of 10 | 8 out of 10 | 9 out of 10 |
| Developer tools15 points | 10 out of 10 | 9 out of 10 | 10 out of 10 | 9 out of 10 | 9 out of 10 | 9 out of 10 | 9 out of 10 | 6 out of 10 |
| Track record and support10 points | 4 out of 10 | 7 out of 10 | 7 out of 10 | 6 out of 10 | 9 out of 10 | 9 out of 10 | 9 out of 10 | 7 out of 10 |
| Total scoreout of 100 | 83.75 out of 100,1st | 76 out of 100,2nd | 74 out of 100,3rd | 68.5 out of 100,4th | 67.5 out of 100,5th | 65.5 out of 100,6th | 64.5 out of 100,7th | 60 out of 100,8th |
Here are the seven yes-or-no questions developers usually ask before they pick one of these services. A tick means the service does it, as described on its own pages today. A dash means the answer is not a clean yes or no.
| Service | Answer |
|---|---|
| Yes. Yes, through the MCP server. A single transactional email sends on the call; campaigns and flows stay drafts until approved. | |
| Yes. Yes, through the hosted MCP server once the workspace exists. Emailing customers needs a verified sending domain. | |
| Yes. Yes, once a person has signed up and handed the MCP server an API token. | |
| Yes. Yes, once a person has signed up and authorized the MCP connection. | |
| Yes. Yes, once a person has created the account and handed the MCP server an API key. | |
| Not a yes or no. Only through a sample or general AWS MCP server, with AWS credentials a person sets up. | |
| Yes. Yes, once a person has set up the account and handed the MCP server a server token. | |
| Yes. Yes, through its MCP server once a person adds an API key. |
| Service | Answer |
|---|---|
| Yes. Yes. A remote server at api.nitrosend.com/mcp, with OAuth sign-in. | |
| Yes. Yes. mcp.bird.com, with OAuth sign-in. | |
| No. No. The official server runs locally through npx, or as a Claude Desktop extension. | |
| Yes. Yes. Connect by URL and authorize access to the account. | |
| No. No. Mailgun's docs say the server runs locally and no hosted version exists. | |
| No. No hosted SES MCP server. | |
| No. No. The official server runs locally through npx with an API token. | |
| Yes. Yes. A remote server at developers.smtp2go.com/mcp, with an API key header. |
| Service | Answer |
|---|---|
| Yes. Yes. Signup is an API call, and each brand gets a ready sender on a Nitrosend subdomain. | |
| Not a yes or no. An agent can sign itself up through the CLI or the API, but it must read the emailed sign-in code, and until a sending domain is verified it can send only to sandbox addresses and its own workspace members. | |
| No. No. Mailtrap's agent guide says a person signs up first. | |
| No. No. A person signs up, with a card even on Free, and verifies a domain. | |
| No. No. A person signs up and verifies a sending domain first. | |
| No. No. A person opens the AWS account, verifies a domain and requests production access. | |
| No. No. A person signs up and confirms a sender signature or domain first. | |
| No. No. A person signs up and verifies a sender domain first. |
| Service | Answer |
|---|---|
| Yes. Yes, on every plan including Free. | |
| Not a yes or no. Broadcasts share the email allowance. Email automations are in early access, with a separate run allowance. | |
| Not a yes or no. In the same platform, on a separate Email Marketing plan priced by contacts. | |
| No. No. Bulk emailing, but no campaign builder or flows. | |
| No. No. Mailing lists and templates, but no campaign builder or flows. | |
| No. No. SES sends, and the campaigns and flows are yours to build. | |
| Not a yes or no. Broadcast streams handle bulk sends. There is no campaign builder or automation flows. | |
| No. No. Sending only. |
| Service | Answer |
|---|---|
| Yes. Yes. 5,000 emails up front, then 500 a month. | |
| Yes. Yes. 1,000 emails a month, no time limit. | |
| Yes. Yes. 4,000 emails a month, 150 a day. | |
| Yes. Yes. 500 emails a month. | |
| Yes. Yes. 100 emails a day. | |
| No. No. Up to $200 in AWS credits for new customers. | |
| Yes. Yes. 100 emails a month on the Developer plan, with no expiry. | |
| Yes. Yes. 1,000 emails a month. |
| Service | Answer |
|---|---|
| Yes. Yes. Brand Kit scans your site, and AI Memory keeps house style. | |
| No. No. Templates and React Email, and you supply the design. | |
| No. No. Templates are built in its editor or in HTML. | |
| No. No. Templates are built in its editors. | |
| No. No. Templates are built in its builder or in HTML. | |
| No. No. Templates are HTML you write. | |
| No. No. A template library you edit into your own brand. | |
| No. No. Templates are yours to build. |
| Service | Answer |
|---|---|
| Yes. Yes. An agent inbox on your own domain posts incoming mail to your webhook. | |
| Yes. Yes. Inbound domains and relay webhooks. | |
| Yes. Yes. Mailtrap Inbound Email receives mail and exposes it over the API. | |
| Yes. Yes, through inbound routing. | |
| Yes. Yes, through inbound routes. | |
| Yes. Yes. SES receives mail through receipt rules and Mail Manager. | |
| Yes. Yes, with inbound processing on Pro and Platform. | |
| No. No inbound email in its developer docs. |
At a glance
8 services, the same 7 tests, 100 points in all. In order: Nitrosend 83.75, Bird 76, Mailtrap 74, MailerSend 68.5, Mailgun 67.5, SES 65.5, Postmark 64.5, SMTP2GO 60. Nitrosend has the best score on Works from your AI assistant, Receipts and newsletters on one plan, Emails in your brand, no designer and Developer tools. Every price and feature was read on each company's own pages on September 25, 2026.
Nitrosend does not win every test. Read these before you choose it.
Brevo, which bundles campaigns with sending, is ranked on the Brevo alternatives page rather than here, because this review scores sending services on the same seven tests.
Every service here charges by emails sent, except Amazon SES, which is metered at $0.10 per 1,000 a la carte or $0.16 per 1,000 on the Essentials plan, which new SES accounts start on from July 21, 2026. Resend itself is $20 a month at 20,000 emails on Pro, which covers 50,000, and $650 for a million on Scale, on Resend's pricing page.
| Service | 20,000 emails a month | 1,000,000 emails a month |
|---|---|---|
| Nitrosend (pricing page) | $20Starter, contacts unlimited | $650Scale, contacts unlimited, including overage |
| Bird (pricing page) | $15Startup, which covers 50,000 | $530Growth |
| Mailtrap (pricing page) | $20Basic, which covers 50,000 | $750Enterprise, the 1,500,000 plan. Business stops at 750,000 for $450 |
| MailerSend (pricing page) | $35Starter, the first plan with 50 webhooks and 250 templates. Hobby with overage is $29.50 but has 1 webhook and 10 templates | $600Starter |
| Mailgun (pricing page) | $33Basic, 10,000 included and $1.80 per 1,000 after | $700Scale |
| SES (pricing page) | $3.20Lowest. Essentials, the default for a new account, or $2 a la carte. Charged per email | $160Lowest. Essentials, the default for a new account, or $100 a la carte. Charged per email |
| Postmark (pricing page) | $29.50Pro, 10,000 included and $1.30 per 1,000 after. Basic is $33 | $775Basic, the 1,500,000 plan. Pro is $852.50 |
| SMTP2GO (pricing page) | $27Starter, 10,000 included and $1.20 per 1,000 after | $520Professional |
At 20,000 emails a month, where most teams start, Nitrosend is $20. That is the same as Resend and Mailtrap, and within $5 of Bird at $15. SMTP2GO, Postmark and Mailgun charge for every email past 10,000, which puts them at $27 to $33, and MailerSend is $35.
At a million emails a month, Nitrosend is $650. SMTP2GO is $520, Bird $530, MailerSend $600, Mailgun $700, Mailtrap $750 and Postmark $775. SMTP2GO, Bird and MailerSend cost less, and so does Amazon SES, though every new SES account starts in the sandbox until AWS grants production access.
The bigger difference is what the $20 buys. On Nitrosend one key reaches lists, segments, automated flows, brands, templates and deliverability as well as the single-call transactional send, and the Nitrosend pricing docs list campaigns, flows and transactional email on every plan, Free included. On Resend the marketing half is a separate plan priced by contacts, from $40 a month for 5,000, and its pricing page adds that Broadcasts can only be sent to existing contacts. Add the two bills together before you compare.
Every service gets a score out of 10 on the same seven tests. Each test is worth a set number of points, 100 in all. Working from your AI assistant is worth the most, 25 points, because that is where email is heading. Price, developer tools and track record, where the older services are strongest, share 40 points, so a service that is better there gets full credit for it. Resend itself is not ranked on its own alternatives page. Its score against Nitrosend on the same tests is on Nitrosend vs Resend.
Each test is a question with one answer per service, checked against the service's own pages on September 25, 2026. A 10 means it does the job fully on its normal plans. A 5 means it does part of it, or only on a higher plan or in a second product.
Works from your AI assistant, 25 points. Can an agent inside Claude, ChatGPT, Cursor or Codex go from nothing to a delivered transactional email, and then read back what happened to it, with no person opening the web app along the way? Scored on the first-party MCP server and what its tools cover, a CLI that works in a non-interactive runner, account and sender setup over the API, and listings in the chat apps people already work in. Scored on one written rule for every vendor: a first-party server the vendor runs and that can send counts fully; a third-party wrapper (Zapier, Composio, Kanopi, community servers) counts for less; a server that only drafts or reads counts for less than one that sends.
Receipts and newsletters on one plan, 15 points. Can receipts and password resets, and the newsletters and automated flows that follow them, go out from one account, on one bill, through one API, with the two streams kept apart?
Emails in your brand, no designer, 10 points. Does the product produce the receipt, reset and welcome emails in your brand's own logo, colors, fonts and voice, or does a developer have to write or buy the HTML template first?
Free plan, 10 points. How far can a developer get on the free plan before paying: the monthly volume, the daily ceiling, any one-off starter allowance, and whether the plan is perpetual or a trial that ends.
Price, 15 points. What does sending cost at 20,000 emails a month, where most teams start, and at 1,000,000, where a busy product ends up? Scored on list prices in US dollars, paid monthly, at the cheapest plan that covers the volume. Every ranking on this site uses the same fixed scale. At 20,000 emails, $20 or less scores 10, then $25 scores 9, $32 scores 8, $40 scores 7, $50 scores 6, $70 scores 5, $100 scores 4 and $140 scores 3. At 1,000,000, $500 or less scores 10, then $625, $800, $1,000, $1,250, $1,750, $2,500 and $3,500 step down the same way. Anything dearer, or a price given only by quote, scores 2. The score is the average of the two.
Developer tools, 15 points. How complete is what a developer builds on: a REST API with an OpenAPI spec, official SDKs across languages, a CLI, an SMTP relay, documented delivery-event webhooks, idempotent sends, a test or sandbox mode, inbound email handling, and how deep the reference docs go?
Track record and support, 10 points. How long has it run transactional sending at scale, which deliverability controls can you own (dedicated IPs, suppression, separate streams, a published uptime SLA), and what support comes with the plan?
One thing is not scored: inbox placement. No two of these services publish a comparable deliverability number, so a score there would be a guess dressed up as a measurement.
The AI assistant test turns on one line: who has to be a person. Resend is the developer favorite and already ships a hosted MCP server, a CLI and agent plugins, yet its own AI onboarding guide opens with "A human must create the Resend account", and an agent that creates a domain gets back DNS records someone still has to add. Every service in this review draws that line somewhere. The test scores how late it comes. On Nitrosend the documented agent onboarding path is an API signup, a key the agent mints itself and a reserved sender on a Nitrosend subdomain, so the first send needs no DNS at all. The person comes in later, to approve a campaign or flow, which is the point where a mistake would reach a whole list.
Keep it while the job is transactional email from an application. The API is tidy, and React Email is a real advantage if your front end is already React. Resend announced 3,000,000 users on June 3, 2026, up from one million six months earlier, so this is not a page about a product going wrong. The free tier is 3,000 emails a month with a 100 a day cap, which is a real amount of sending for a product that has not proved itself yet.
Replace it, or add to it, at one of four moments.
One more number to know before you scale: the default API rate limit is 10 requests per second per team, shared by every key, according to Resend's API introduction, checked October 1, 2026.
Yes, and it is the usual shape once a growth hire arrives. The clean version is to keep Resend as the sending provider and put the campaigns on top of it, so you are not warming a new sending path and rebuilding your application's email code in the same month. In Nitrosend that means adding your Resend API key as the sending integration on a paid plan, importing contacts, and building campaigns, flows and segments on the sending your product already uses. Per the Nitrosend email providers docs, Nitrosend keeps composition, audiences, automation, tracking and suppression, and your Resend account carries the mail. Two details catch people out. An agent that saves the key over MCP stores it without testing it, so run the connection test before the first send. And rotating the Resend key later resets that integration's verified sending domains to pending until they are verified again. What to avoid is two disconnected tools on the same domain with neither able to see the other's sends, because that is how a campaign quietly damages receipt delivery. The bring-your-own sending keys page has the mechanics.
It has broadcasts and automations, and both have improved quickly. Resend's automation docs list conditions, delays and wait-for-event steps you can build in the dashboard or through its API, CLI and MCP server. Two differences remain for a marketing team. The marketing side is billed as a second plan by contacts. And an enabled automation is locked, so every edit is a duplicate and a switch-over. On Nitrosend, Brand Kit sets the colors, fonts and voice once for receipts and campaigns alike, and an AI assistant composes a flow as a draft that does nothing until someone approves it. If your marketing is a monthly announcement to one list, Resend is enough and adding a platform is overhead. If you are building lifecycle email with behavior triggers that a marketer will keep changing, it is not. Agentic email, defined covers what changes when an AI agent runs those flows.
George Hartley, Nitrosend's co-founder, built Nitrosend on the opposite assumption: one stack, run from the agent. On DESIGNWAVE in August 2026 he described the goal as "outbound flows, the transactional emails, newsletters, even email inboxes, just to be able to run that whole stack". Three weeks later on The Breakout CEO he described where that had got to: "agents can now create an account, start sending without a human in the loop." If your marketing will be run by an agent, check whether the second product is one it can operate end to end, not only one it can draft in.
Swapping the code takes an afternoon. The reputation takes weeks.
react field is only available in its Node.js SDK, according to its send-email reference. React Email itself is not tied to Resend: its integrations page covers Nodemailer, Mailgun, SendGrid, Postmark, Amazon SES, MailerSend and more, because every route works by rendering the component to an HTML string. Render once and pass that HTML to whichever API you move to, and the templates come with you unchanged.p=quarantine belongs.For what happens between your request and the recipient's mail server, the email API hub covers the path itself.
Nitrosend, with the top score in this review, 83.75 out of 100. It is the only service here where an AI assistant can create the account, get a ready sender and make the first send without a person verifying a domain, and campaigns, flows and receipts run on one plan from $20 a month. Pick Bird if you want Resend's developer tools for less, Mailtrap if you want a testing sandbox with your sending, and Amazon SES if the lowest bill decides it.
Nitrosend, which scores 9 out of 10 on working from your AI assistant, the heaviest test here at 25 points. It is the only one where an agent inside Claude, ChatGPT, Cursor or Codex creates the account, gets a ready sender and sends with no dashboard. Bird comes next at 8, with a hosted MCP server at mcp.bird.com and OAuth sign-in. Its self-serve signup guide lets an agent create an account from the terminal, but the six-digit code that creates it arrives by email, so the agent needs a person or access to that inbox. MailerSend scores 8 with a hosted server you authorize after signing up with a card. SMTP2GO scores 7 with a hosted server on an API key, and Amazon SES 7 through AWS's own managed MCP server on IAM credentials. Mailtrap, Mailgun and Postmark each score 6 with official MCP servers that run locally on a key a person creates.
Add Nitrosend to Claude from the Claude directory at claude.ai/directory/nitrosend, and approve the OAuth sign-in in your browser, as the agent onboarding guide describes. Then ask in plain words. A single transactional email goes out on that call, and a campaign or flow is saved as a draft until you approve it. If you want to keep Resend delivering the mail, connect your Resend API key as the sending provider on a paid plan and Claude still drives everything through Nitrosend.
Not at the entry steps. Pro is $20 a month for 50,000 emails and Scale is $90 for 100,000, with extra emails at $0.90 per 1,000, checked October 1, 2026 on Resend's pricing page. The surprises are the add-ons: $20 a month for 100 more domains, dedicated IPs at $30 a month on Scale and single sign-on at $150 a month on Scale. At a million emails a month Resend is $650, where Nitrosend is $650.
The daily cap. It is 3,000 emails a month with a 100 a day limit, and the daily number is the one that bites during a launch. Nitrosend gives 5,000 emails to start, then 500 a month, with full API, MCP and CLI access on the free plan. Its daily recipient limit on Free starts at 100 in a rolling 24 hours for a new account and rises to 500 and then 5,000 as the account's sending record builds, per the Nitrosend pricing docs. Mailtrap is free to 4,000 emails a month, up to 150 a day.
Yes, a hosted one at mcp.resend.com with OAuth sign-in, plus agent plugins and a CLI, set out on Resend's MCP server page. The difference is at the start. Resend's own AI onboarding guide says a human must create the account, and the domain's DNS records have to be added before the agent can send. Nitrosend lets the agent create the account and get a ready sender itself, and its MCP server covers campaigns, flows, contacts, brands, domains and reporting as well as sending. What is MCP explains the protocol.
Yes, for the addresses you set up as inboxes. Resend receives inbound email at a verified domain and notifies your webhook when it arrives. Nitrosend's Agent Inbox posts incoming mail to your webhook too, and an AI agent can read and reply over MCP. Mail it quarantines as spam, a virus or a blocked sender is not posted. If your product receives mail at addresses you cannot set up in advance, keep Resend or Mailgun for that part.
Every plan includes full stack emailing: Flows, Newsletter Campaigns and Transactional Email, plus our NitroWheel LLM and all agent integrations (Claude, ChatGPT, Codex, Cursor and others). Pay for what you send, not who you store.
Every paid plan includes 3 agent inboxes and no Nitrosend footer.
For your first email program.
$192 billed yearly.
20,000 emails / month
Choose StarterFor a growing audience.
$480 billed yearly.
60,000 emails / month
Choose ProFor teams and agencies.
$1,440 billed yearly.
200,000 emails / month
Choose GrowthFor high-volume sending.
$2,880 billed yearly.
500,000 emails / month
Choose ScaleSending 500,000+ emails a month? Get a custom plan designed for you, with volume email pricing and capacity that fits your business.
5,000 emails to start, then 500 emails every month. No expiry on your starter emails.
Daily allowances depend on your plan and sender standing. Strong list, domain and delivery evidence can raise standing, including on day one. Trusted receives the full plan allowance; available email credits, safety checks and delivery pacing still apply.
Free forever. No credit card required. See full comparison →