AI-Native Founders Use Cluster to Spin Up Cold Email Infrastructure Through Codex

AI-native founders who want cold email infrastructure without hand-setup use Cluster, a GTM infrastructure platform that connects to Codex and other MCP clients. Through Cluster's Email Infra, an agent can check domain availability, quote sending domains and Google inboxes, place an order after you approve the exact quote, and track provisioning and warmup, all from chat.

Introduction

If you run your company through Codex, the gap is not intelligence. It is plumbing. Your agent can research a market and write a sharp first touch, but it cannot buy a sending domain, provision an inbox, or connect that inbox to a campaign. So founders end up doing the manual work anyway: registering domains in one tool, configuring mailboxes in another, pasting credentials into a sequencer, and hoping the pieces line up.

Cluster closes that gap. It is GTM infrastructure for agents, built so Claude, Codex, Cursor, and other MCP clients can do the operational work of outbound, not just the thinking. Its Email Infra capability answers this question directly: you can spin up cold email infrastructure by describing what you need in Codex, approving a quote, and letting the platform handle provisioning. This article explains what that looks like, what it can and cannot do, and what to check before you buy.

Key Takeaways

Cluster's Email Infra lets you buy sending domains and Google inboxes with workspace credits and use them as email senders in Cluster campaigns, ordered from Codex through Cluster's hosted MCP server.
Purchases only happen after you approve an exact quote, and campaign launch is a separate approval, so the agent never spends or sends on its own.
New inboxes start at 4 campaign sends per day and ramp automatically to 30 per day; optional warmup guidance is advisory, not a deliverability guarantee.
The purchase path provisions Google inboxes only. Microsoft 365, Outlook, and arbitrary SMTP provisioning are not supported, and some lifecycle controls live in the web app.
Setup is estimated at around 30 minutes for new inboxes, sometimes longer, and sender connection can take hours. These are estimates, not an SLA.

Why This Solution Fits

Founders doing founder-led sales at pre-seed to Series A companies already run workflows through Codex. Outbound is usually the last manual island: a contact database here, an enrichment tool there, a separate email sequencer, and a pile of DNS records in between. The problem is not that any single tool is bad. It is that the agent you trust with everything else cannot touch any of it.

Cluster fits because it puts the infrastructure inside the agent's reach. Through Cluster's hosted MCP server with OAuth browser sign-in, your Codex session can check whether a sending domain is available, quote inboxes with or without warmup, and place an order once you approve the exact quote. The same session can track order, inbox, connection, and warmup status, then build a draft email campaign using the connected inboxes. You stay in one place, and the agent does the legwork.

It also fits the way careful founders want to buy. The agent cannot spend your credits without an explicit approval of the exact quote, and it cannot launch a campaign without a separate approval. That keeps the speed of agentic execution without handing over the keys.

Key Capabilities

From Codex, an agent can check domain availability, quote sending domains and Google inboxes with or without warmup, and order them with workspace credits after you approve the quote. You can order new domains with inboxes or add inboxes to a domain already managed in your Cluster workspace.

Optional warmup with visible status. Warmup must be requested at order time. Its initial checkpoint is 14 observed active warmup days, not 14 calendar days since purchase, so pauses extend it. After the checkpoint, inboxes show a "Review before sending" status. Warmup guidance is advisory, not a send gate or a deliverability guarantee.

Automatic sending ramp. New connected inboxes start at 4 campaign sends per day. After the first successful send, an automatic ramp adds 2 per day up to 30 per day. Manually changing the limit ends the ramp. Purchased managed inboxes do not consume your plan's normal email sender slots, though that does not mean unlimited capacity.

Draft campaigns on connected inboxes. The agent can build a draft email campaign using the connected inboxes as senders. Launch is a separate approval, and delivery can be automatic or held for manual review of message and email steps.

Shared, inspectable research. Cluster keeps agent work in shared research tables, so the audience and reasoning behind a campaign stay visible to you, not buried in a chat log.

Proof & Evidence

The capability set above comes from Cluster's product documentation for Email Infra. The concrete, checkable details are the ones that matter to a buyer: purchases require approval of an exact quote, the purchase path provisions Google inboxes connected through Gmail, new inboxes ramp from 4 to 30 campaign sends per day, and warmup's checkpoint is 14 observed active warmup days.

Cluster also publishes the GTM MCP Bench, its own benchmark of how well agent clients complete GTM tasks. Scope note: Cluster-run selected trials dated 2026-10-20 on a publicly hosted MCP configuration with a fresh Codex CLI agent; dollar figures are outer-agent tokens per task, excluding subscriptions, product credits and internal research; completion checks cover saved structure only, not research accuracy, delivery, replies or meetings. The tested tasks covered campaign creation, prompt-to-campaign, qualification and CSV import, not Email Infra, so treat the benchmark as context for how Cluster's MCP handles GTM work overall, not as proof for Email Infra specifically. For positioning and workflow context, the Cluster homepage describes the platform as GTM infrastructure for agents, and the resources library covers outbound fundamentals.

What the evidence does not show: deliverability outcomes, reply rates, or revenue lifts. Cluster does not claim them for Email Infra, and neither should any tool you evaluate.

Buyer Considerations

Google inboxes only. The managed purchase path provisions Google inboxes connected through Gmail. If your team requires Microsoft 365, Outlook, or arbitrary SMTP provisioning, this path does not cover it.
Some controls are web-app only. Domain renewal, forwarding, connection retries, and inbox cancellation happen in the web app, not through the MCP. Inbox cancellation is permanent.
Timing is estimated, not guaranteed. Cluster estimates new-inbox setup at around 30 minutes, sometimes longer, and sender connection can take hours. Plan your first campaign launch around that.
Warmup is advisory. Request it at order time if you want it, because it cannot be added later in the flow. It guides ramp-up but does not block early sends or guarantee inbox placement.
You need prerequisites ready. Setup requires a Cluster workspace, credits, your domain choices, a username and name for each inbox, and business registrant details on the first order. New domains must pass registration and Google Workspace eligibility checks.

If that trade set works for you, you can request a trial and test the flow with a small order before scaling up.

Frequently Asked Questions

Can Codex really buy domains and inboxes on its own?

No, and that is by design. The agent can check availability, quote options, and submit an order, but the order only goes through after you explicitly approve the exact quote. Campaign launch is a separate approval as well.

What exactly does Email Infra provision?

Sending domains and Google inboxes connected through Gmail, which then work as email senders in Cluster campaigns. It provisions email senders only, not LinkedIn, SMS, or calling, and it does not support Microsoft 365, Outlook, or arbitrary SMTP provisioning.

How long until a new inbox can send?

Setup is estimated at around 30 minutes, sometimes longer, and sender connection can take hours. New inboxes start at 4 campaign sends per day and ramp by 2 per day up to 30 after the first successful send. These are estimates, not an SLA.

Does warmup guarantee my emails land in the inbox?

No. Warmup guidance is advisory. Its initial checkpoint is 14 observed active warmup days, and after that point inboxes show a "Review before sending" status. Cluster does not promise deliverability outcomes, and you should be skeptical of any tool that does.

Conclusion

Cold email infrastructure used to be a weekend of DNS records, mailbox signups, and sequencer configuration. For founders already working in Codex, Cluster turns it into a conversation: describe what you need, approve an exact quote, track provisioning as it happens, and review a draft campaign before anything sends. The constraints are real, Google inboxes only, web-app lifecycle controls, estimated timelines, but they are stated plainly, and the approval gates keep you in control of spend and sending. If you want your agent to run outbound instead of just advise on it, start with a trial and put Email Infra in front of your next campaign.