How to build a cold email workflow with MCP

Define what success looks like

Start with a narrow objective: prepare a campaign for a specific audience using an existing mailbox. Do not begin with an unlimited instruction to find everyone and keep sending. Write down what qualifies a company, how many prospects belong in the pilot and which facts support the offer.

For a first run, success means the right contacts and exact messages are saved in the product, ready for inspection. Sending and customer acquisition are later outcomes. This makes connection or data-quality failures easier to find before they affect real recipients.

Connect and verify account access

Use ColdPegion's connection guide and authenticate the client. Ask for the account overview, available mailboxes and campaigns. Confirm the workspace is the one you intended to use.

If a scheduled run is part of the plan, test its tool access in that environment too. Tools available in an interactive chat are not proof of access in another runtime. A missing connection should produce a clear blocker, not a claim that a campaign was created.

Build an evidence-backed prospect list

Store the company's public source URL, the relevant observation and the date. Deduplicate by address and company. Keep research separate from a sending list until the contact satisfies your outreach criteria.

For a verified-only workflow, require a verification result that establishes mailbox evidence. A syntactically correct address, published contact page or working MX record does not establish that mailbox. UNKNOWN and catch-all results stay outside the sending gate.

Prepare a specific message for each person

Give the assistant your product brief and source observations. Ask for a short subject, one concrete connection between the company's work and your offer, and a single next step. Add a clear opt-out. Never manufacture a relationship, business result or event that did not happen.

ColdPegion's external preparation tools let the client supply individual subjects and bodies. Read the saved records back after preparation. Check recipient, message step and content, especially if a prior tool call failed and had to be retried.

Read my ColdPegion overview and mailboxes. Prepare a draft for these five authorized test contacts. Use only the supplied facts. Write a distinct first email per person, save the messages, and show the exact recipients, subjects and bodies. Do not launch.

Launch within the campaign's authority

Use the selected review process before launch. Preserve suppression records, daily limits and schedules. If the campaign is in a review mode that requires exact-message approval, a general instruction to automate does not replace that approval.

After launch, inspect the actual state. Queued messages may be waiting on a schedule or a limit. Sent means a sending operation occurred; it does not prove inbox placement. Count interested replies and activated accounts only when the evidence supports them.

Make the second run safer than the first

Save the campaign ID, processed contacts, message IDs and last outcomes. Before the next run, read existing state and exclude contacts already handled. If you cannot tell whether a mutation succeeded, inspect the records instead of blindly recreating the campaign.

The reusable prompt pack includes research, drafting, review and reporting prompts so each step can be tested independently.