Nitrosend vs Woodpecker.

Lifecycle email, MCP on every plan, unlimited contacts, and a published price.

TL;DR

Woodpecker is a cold outbound platform. It sends from the mailboxes you connect, rotates across them, warms them, detects a reply and stops the sequence, with LinkedIn steps and a lead database sitting in the same workflow. If your job is running cold outreach to people who've never heard of you, it does that job and this page isn't going to argue otherwise.

Nitrosend is a different product, built for the email that starts once a prospect has answered: campaigns, flows, segments, and transactional sends, with every capability an email API endpoint and an MCP tool before it's a screen. Contacts are unlimited on every plan including Free, and BYO sending keys are available on Pro and above. A team whose whole email is cold outbound wants Woodpecker, and most teams end up running both. The comparison index covers the platforms that handle the second half.

Pricing math

What you actually pay.

Woodpecker bills on contacted prospects, not on emails sent, and the plan price is a floor rather than a total: connecting your own email accounts is unlimited, but mailboxes bought inside the product, warm-ups past the fourth, LinkedIn, the API bundle, and agency clients are all priced on top. Both columns are monthly.

Scenario	Nitrosend	Woodpecker
Getting started	Free: 8,000 emails to start, then 500/mo forever. Unlimited contacts, full MCP, API, and CLI	14-day trial or 100 cold emails, whichever comes first. No permanent free plan
500 prospects, 16,000 emails/mo	$20 Pro: 20,000 emails, unlimited contacts, 3 seats, BYO sending and AI keys	$35: 500 contacted prospects, 16,000 emails, four free warm-ups, unlimited connected email accounts and team members
The same, with API and MCP on	$20 Pro: the MCP, REST API, and CLI are on every plan including Free	$55: the $35 plan plus the $20/mo Integrations, API, webhooks, MCP, and CLI add-on
Five client accounts	$100 Ultra: 125,000 emails, 5 brands, 10 seats, unlimited contacts	$135/mo in Agency Panel fees at $27 per active client, plus white label, on top of the plan

Prices accurate as of August 2026. Check vendor sites for current rates.

Migration

How to switch (or run both).

This isn't a cutover. Woodpecker keeps running the outbound while Nitrosend picks up everything after the reply, and for most teams that overlap is the permanent arrangement.

Add and verify your sending domain in Nitrosend. DKIM and SPF sit alongside whatever your outbound mailboxes already use, so both platforms can send from the same domain during the overlap and neither disturbs the other.
Leave the cold outbound where it is. Woodpecker keeps the sequences, the inbox rotation, the warm-up, and the reply detection, all of which sit outside what Nitrosend does.
Move the prospects who replied. Import them with nitro_import_contacts: email, first and last name, and custom properties map across from a Woodpecker export, which is reachable through Woodpecker's own API and MCP rather than by hand.
Build the sequence that starts after the reply as a flow with nitro_compose_flow. Onboarding, nurture, and product notifications belong here. Woodpecker has no flow builder over an owned contact database, so this is usually the first time that sequence has existed as one object.
Decide what carries the sending. BYO sending keys on Pro and above route mail through Amazon SES, Resend, Postmark, Mailgun, or SendGrid, on a domain you already warmed, which is what makes the decision reversible.

Honest credit

What Woodpecker does well.

Choosing between these is a question of fit. Here's what Woodpecker does well, stated plainly.

The MCP server is official and first-party, documented by Woodpecker and published on both GitHub and Docker Hub rather than maintained as a community wrapper.
It runs two ways: hosted by Woodpecker, or self-hosted over Docker and stdio with your own API key.
Its campaign tools create, update, run, pause, stop, and delete campaigns, and read campaign statistics back into the conversation.
Sequence steps are editable as tools, so an agent can build a multistep sequence with A/B variants without anyone opening the builder.
Prospect tools cover bulk add, update, list, search, and delete, across both the prospect database and an individual campaign.
Unlimited email accounts and unlimited team members come with every plan, with no per-seat fee anywhere on the ladder.
Follow-ups don't count against the contacted-prospect limit, so the bill tracks the people you reached rather than the messages you sent.
Four warm-ups and catch-all email verification are included in the plan rather than sold as separate products.
Reply detection sits inside the sending algorithm, so a sequence won't email someone who has already answered.
Inbox rotation, adaptive sending, a Deliverability Monitor, and a domain audit all live inside the product instead of a second vendor.

What Nitrosend adds

Where we think we're better.

Campaigns, flows, segments, and transactional sends run in one platform, aimed at the email that starts once a prospect has answered.
Contacts are unlimited on every plan, including Free, so a list that grows without being mailed never moves the bill.
MCP-first is an architecture, not an integration: every capability is an API endpoint and an MCP tool before it's a screen.
The MCP, the REST API, and the CLI are on every plan including Free, rather than bundled into a paid add-on.
That agent surface reaches campaigns, flows, contacts, templates, and segments, because that's the shape of the platform behind it.
Deliverability, billing, tests, and approvals are tools too, and they're the four that usually stop an automation dead.
Reputation work sits in the same agent surface as the send, so it isn't a separate dashboard trip.
Transactional sends deliberately stay on the REST API, because a send that has to be fast shouldn't wait on a tool call.
BYO sending keys on Pro and above route mail through Amazon SES, Resend, Postmark, Mailgun, or SendGrid, on a domain you already warmed.
Every rung has a published price, including 500K to 4M+ emails a month, with no quote-only tier at the top.

Use case fit

When to pick which.

Pick Woodpecker if

Your email is cold outbound to people who have never heard of you. You need sends rotating across connected mailboxes with warm-up behind them, and you need the sequence to stop the moment somebody replies. Reply detection on its own is reason enough to stay, because Nitrosend is sender-side and doesn't touch your mailboxes. Add LinkedIn steps beside the email ones, or a white-labelled reporting panel for client work, and it's a straightforward call.

Pick Nitrosend if

Your email goes to people who already know you, and you want campaigns, flows, and transactional sends in one place instead of three. It's the right call when the whole platform has to answer to the agent you already run, on every plan rather than as an add-on, or when a contact count keeps moving a bill you can't predict. The sharpest case is a team already running outbound somewhere, with nowhere sensible for everything after the reply. Shortlists here usually also carry Zepic for lifecycle mail, Zoho Campaigns when the CRM is already Zoho, and ActiveCampaign when the automation is the point.

Woodpecker vs Nitrosend - common questions.

Can Nitrosend replace Woodpecker for cold outreach?

No. Nitrosend is sender-side: it doesn't connect your mailboxes, rotate sends across them, or detect a reply and stop a sequence, and cold outbound needs all three. What it does replace is everything after the reply, which is where campaigns, flows, segments, and transactional sends live.

Woodpecker has an MCP server. What's different about Nitrosend's?

Woodpecker's is official, documented, and published on GitHub, so this isn't a question of whether an agent can drive it. Two things differ. Ours is on every plan including Free rather than inside a $20/mo add-on bundle, and it reaches campaigns, flows, contacts, templates, segments, deliverability, billing, tests, and approvals, which is the whole platform rather than one motion inside it.

Can I move my campaign data out of Woodpecker?

Yes, and it needn't be a manual export. Prospects and campaign data are reachable through Woodpecker's own API and MCP server, though the self-hosted route needs the integrations add-on switched on. From there, <code>nitro_import_contacts</code> takes email, first and last name, and custom properties straight onto a Nitrosend contact record.

If both platforms send from one domain, whose sender reputation is it?

It's the domain's, and that's the reason to be deliberate about the split. Woodpecker sends cold outbound from the mailboxes you connect, so that traffic carries the reputation of those mailboxes alongside the domain's. Nitrosend sends from your verified domain, and BYO sending keys on Pro and above route it through Amazon SES, Resend, Postmark, Mailgun, or SendGrid, so the lifecycle stream sits on sending infrastructure of its own. Teams that want the two kept fully apart give the cold outbound its own domain.

Start with the free tier.

8,000 emails to start, then 500 a month, unlimited contacts, full MCP, API and CLI access. No credit card.