How to connect a mailbox from Claude
How-to guide Updated 12 July 2026
How do you connect a mailbox to cold email software?
Connect the HotHawk MCP server to Claude, then ask it to add your sending mailbox over IMAP and SMTP. Give it the email, the IMAP host and the SMTP host, and Claude connects the account, checks it can send and receive, and confirms it is live. Warmup and rotation then start on their own.
No credit card required.
Before you start
You need a HotHawk account and the HotHawk MCP server connected to Claude. It takes a couple of minutes and no code. Full setup is on the MCP server page.
Step by step
-
1
You ask Claude
Connect my sending mailbox [email protected] over IMAP and SMTP.
Claude callsmcp__hothawk__mailboxes_connect_imap_createClaude adds the mailbox, checks it can send and receive, and reports back the moment it is live in your workspace.
-
2
You ask Claude
Add the other five inboxes on that domain too.
Claude callsmcp__hothawk__mailboxes_connect_imap_createemail 5 more inboxes imapHost imap.acme-outbound.com smtpHost smtp.acme-outbound.comAll five connect in one go. You have gone from one sending account to six in the time it took to type the sentence.
-
3
You ask Claude
Show me every mailbox now connected.
Claude callsmcp__hothawk__mailboxes_listworkspaceId current workspaceClaude lists the lot, flags any that failed to connect, and tells you which ones warmup has already started on.
More mailboxes is the whole game
Cold email is a volume problem before it is anything else. One inbox can only send so much in a day before its reputation starts to wobble, so the teams sending real numbers do not lean on one account. They spread the load across many, each sending a modest, human amount. That pool is your sending infrastructure, and adding to it is the single most useful thing you can do.
The catch has always been the faff. Connecting a mailbox means digging out IMAP and SMTP hosts, app passwords and port settings, then repeating it for every account. Do that thirty times and you see why people put it off. Running it from Claude turns the whole chore into a sentence, and the batch of five you were dreading connects in one call.
What connecting actually does
When you ask Claude to add a mailbox it runs mailboxes_connect_imap_create, the same endpoint the app hits when you click through the setup screen. It checks the account can send and receive, then reports back. Nothing is hidden. You can ask to see the full list at any point and Claude will tell you which mailboxes are live and which failed, and why.
The bit that matters comes next, and it happens without you. A new mailbox starts warming straight away, on a real Google or Microsoft inbox rather than a bot or a raw SMTP relay, because warmup only means anything when the reputation it builds is real. Attach the mailbox to a campaign and rotation folds it into the pool automatically, so the sending spreads and no single account carries too much.
Adding capacity, not accounts
Think of each mailbox as a slice of daily headroom. Six inboxes on one domain, each sending a sensible amount, add up to far more than one inbox flogged to its limit, and they spread the risk while they do it. This is how a HotHawk workspace sends 40,000 emails a day and beyond: dozens of warmed inboxes each carrying a modest share, not one account carrying the lot.
So when a campaign needs more room, you do not rebuild anything. You add mailboxes. From the same chat you can check which ones are healthy, attach a fresh pool to a campaign, or spin up the campaign itself, each one a sentence away.
The HotHawk tools behind this
Every action here is a real endpoint. Claude reaches it over the MCP server, and you can hit the same endpoints directly from the REST API if you would rather build it into your own stack.
-
mcp__hothawk__mailboxes_connect_imap_createAdd a sending mailbox over IMAP and SMTP -
mcp__hothawk__mailboxes_listConfirm what is connected and its status -
mcp__hothawk__reconnect_mailboxRe-authenticate a mailbox if its credentials change
Frequently asked
What do I need to connect a mailbox?
The email address, the IMAP and SMTP host, and an app password for the account. Have those to hand and Claude does the rest. Google and Microsoft inboxes both work, and so does any provider that supports IMAP and SMTP.
Does warmup start on its own once a mailbox is connected?
Yes. A new mailbox begins warming as soon as it is live, and once a campaign is attached, rotation shares the sending across every mailbox you have added. You do not switch either on by hand.
Are the deliverability protections still on when I add a mailbox from a chat?
They are, and they are the same as adding one in the app. Warmup runs on real Google and Microsoft inboxes, not bots or raw SMTP, sending rotates across your mailboxes, and open and link tracking stay off. Claude cannot turn any of that off.
How many mailboxes can I connect?
As many as your plan allows, and most serious outbound teams run dozens. Rotation is what lets that pool send 40,000 emails a day and more without leaning too hard on one domain, so adding capacity is the point.
Do I need to write code?
No. You add HotHawk as a connector in Claude once, then connecting a mailbox is one plain sentence. The same endpoint is in the REST API if you would rather script bulk imports into your own stack.