Personalized Outbound Strategy
Get The Right Outbound Strategy In Minutes
Enter your email to get a custom plan & stack recommendation for your business
It's being carefully crafted by AI
Please check your mailbox in 5 minutes
Setting up cold email infrastructure usually means buying domains, creating mailboxes, configuring SPF, DKIM, and DMARC, and then warming everything up before sending. Doing this manually takes time and requires switching between multiple tools.
With Claude + MCP, you can do this in one flow. You can create mailboxes using Primeforge, check warmup using Warmforge, and monitor infrastructure directly from Claude.
In this guide, I’ll show you exactly how to set up cold email infrastructure in 10 minutes with Claude Code + MCP, from connecting the MCP server to creating mailboxes and checking which inboxes are ready to send.
Here’s a quick look at how to setup cold email infrastructure with Claude Code + MCP:
The setup is fast because everything runs through one workflow, but sending should only start after the mailboxes are properly warmed up.
Claude Code acts as the interface, while MCP (Model Context Protocol) connects it to your cold email infrastructure tools. Instead of logging into different platforms to create domains, set up mailboxes, and check warmup, you give instructions to Claude.
When you send a prompt like “create 10 mailboxes” or “check warmup status,” Claude routes that request through MCP to the connected tool. The actual work, like, domain setup, mailbox provisioning (Google Workspace or Microsoft 365), DNS configuration, and warmup tracking, is handled by those tools through their APIs.
Once the action is completed, Claude returns the result, such as created mailboxes or warmup status.
This turns cold email infrastructure setup into a single workflow, where setup and monitoring happen from one place instead of multiple dashboards.
Before starting, you need a few things ready. Claude does not host infrastructure. It connects to your tools through MCP and runs actions using their APIs. So these requirements are needed to set up and manage cold email infrastructure properly.
Once your setup requirements are ready, the next step is to connect Claude Code to your infrastructure tools through MCP and run the setup step by step.
Each step is done through prompts, while the actual actions are executed by the connected tools through the MCP server.
The steps below show exactly how to set up and verify your cold email infrastructure.
Before you can set up cold email infrastructure, you need to connect Claude Code to your tools through an MCP server. For this setup, you can use the Forge MCP Server.
The Forge MCP Server gives Claude access to the actual infrastructure actions needed for cold email, such as:
It works as a single endpoint that connects all these tools, so you don’t have to set up each system separately. Once connected, Claude can run these actions through prompts instead of you manually using different dashboards.
To connect Claude to the Forge MCP Server, you need API keys from the tools you want to use.
Only include API keys for the tools you will use. These will be added in the next step when configuring the MCP connection.
Now you need to connect Claude Code to the Forge MCP Server using the API keys you generated in Step 1.
Run this command in your terminal:
claude mcp add salesforge \
--transport streamable-http \
--url https://mcp.salesforge.ai/mcp \
--header "X-Salesforge-Key: YOUR_SALESFORGE_API_KEY" \
--header "X-Primeforge-Key: YOUR_PRIMEFORGE_API_KEY" \
--header "X-Warmforge-Key: YOUR_WARMFORGE_API_KEY"
Replace each API key with your actual key. Only include headers for the tools you are using. If you don’t use a tool, remove its header.
This command connects Claude Code to the Forge MCP Server, which exposes your infrastructure tools through a single endpoint. After running the command, restart Claude Code and test it with simple prompts:
If the setup is correct, Claude will return real data from your account.
Once Claude is connected to the MCP server, you can start creating your cold email infrastructure. Instead of manually setting up domains and inboxes, you can trigger mailbox provisioning through Claude using MCP-connected tools.
For example:
Claude sends this request through MCP, and the connected infrastructure tools handle domain setup, mailbox creation, and DNS configuration in the background. Once completed, Claude returns the created mailboxes and their details.
At this point, your cold email infrastructure is created, but it is not ready for sending yet. New mailboxes need to go through warmup before they are used in live campaigns.
Once your mailboxes are created, you need to check if they are ready to send. This is done through the Forge MCP Server, which exposes warmup data from your connected tools. After connecting MCP in Step 2, you can directly ask Claude Code to fetch warmup data.
For example, run prompts like:
Claude sends these requests through the Forge MCP Server, which pulls data from the warmup tools and returns:
This works because MCP exposes warmup stats and placement tests as callable tools.
After your mailboxes are warmed up and in use, you need to check their performance regularly. This is part of the weekly workflow for managing cold email infrastructure. Using Claude Code with the Forge MCP Server, you can fetch mailbox performance data through prompts.
For example:
Claude sends these requests through MCP and retrieves mailbox analytics from the connected tools.
At this point, your cold email infrastructure is set up. Now you need to verify that everything is working correctly through the MCP connection. Using Claude Code, run these checks:
Claude sends these requests through the Forge MCP Server and returns the current state of your infrastructure from the connected tools.
Setting up cold email infrastructure used to take hours across multiple tools. Domains, mailboxes, DNS, warmup, everything was handled separately.
With Claude Code + MCP, the setup becomes a structured workflow. You connect once, add your keys, and run the setup through prompts.
The setup itself can be done in minutes. What takes time is warmup and preparation. That’s an important difference. If you follow the steps above, you’ll have a system that is:
Even during setup, small mistakes can create problems later. These usually happen when steps are rushed or skipped.
Most setup problems come from missing connections, wrong keys, or poor planning. If the setup is done properly, the rest becomes much easier to manage.
The Forge MCP Server connects all the tools needed for cold email through one endpoint. Each product handles a specific part of the workflow.
Cold email starts with mailboxes you can actually send from.
All of this runs through MCP, so the workflow stays connected.
Enter your email to get a custom plan & stack recommendation for your business
Please check your mailbox in 5 minutes
If your goal is to set up cold email infrastructure with Claude Code + MCP, the workflow is straightforward. You connect Claude to the Forge MCP Server, add the API keys for the tools you want to use, create your mailboxes, and then check warmup and mailbox health from the same workflow.
That removes most of the manual setup work that usually happens across different dashboards.
The important part is understanding what the 10 minutes refer to. You can connect the system and create the infrastructure fast. But that does not mean you should start sending right away.
New mailboxes still need to warm up before they are used in live campaigns. So the real advantage here is not instant sending. It is being able to set up and manage the full cold email infrastructure in a much cleaner way.
For cold email, the base layer is always the mailbox setup. If that part is weak, the rest of the workflow breaks.
That is why tools like Primeforge matter in this setup. It gives you the Google Workspace or Microsoft 365 mailboxes and domain setup that the rest of the system depends on.
From there, you warm them up, monitor them, and only then move into campaigns.
Claude Code + MCP helps you set up cold email infrastructure faster, but the quality of that infrastructure still depends on proper mailbox setup, warmup, and monitoring. That is what actually makes the system usable.