Model Context Protocol (MCP) server for Apollo.io API integration
Cold Email is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Generate hyper-personalized cold email sequences via AI.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http cold-email-mcp 'https://mcp.machfive.io/mcp/{api_key}'
# 2 — ask your agent for something these tools do
# list_campaigns, generate_sequence, generate_batch and 3 more
The address has parts to fill in — the marked ones, such as your key, token or project id — before you run this; its publisher’s source, linked at the top of its page, says where they come from.
Cold Email costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. The address has parts to fill in — the marked ones, such as your key, token or project id — before you run this; its publisher’s source, linked at the top of its page, says where they come from. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http cold-email-mcp 'https://mcp.machfive.io/mcp/{api_key}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List campaigns in the user's MachFive workspace. CALL THIS FIRST before generate_sequence or generate_batch — you need a campaign ID to generate emails. If the user hasn't specified a campaign, call this and ask them to pick one. Returns JSON array of campaigns with id, name, and created_at. Use the 'id' field as campaign_id in generate calls.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Search string to filter campaigns by name (case-insensitive substring match). Leave empty to list all. |
Generate a personalized cold email sequence for ONE lead. This is SYNCHRONOUS — the request takes 3-10 minutes because MachFive researches the prospect and crafts unique emails. Do NOT retry if it seems slow; wait for the response. You must have a campaign_id first. Call list_campaigns if you don't have one. If the request times out, use the returned list_id with get_list_status and export_list
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_id | string | yes | Campaign UUID from list_campaigns. |
| string | yes | Lead's email address (REQUIRED). | |
| name | string | no | Lead's full name (improves personalization). |
| title | string | no | Lead's job title (improves personalization). |
| company | string | no | Lead's company name (improves personalization). |
| company_website | string | no | Company URL for AI research. |
| linkedin_url | string | no | LinkedIn profile URL for deeper personalization. |
| email_count | integer | no | Number of emails in sequence, 1-5. |
| list_name | string | no | Display name for this list in MachFive UI. |
| email_signature | string | no | Signature appended to each email. |
| campaign_angle | string | no | Additional context/angle for personalization. |
| approved_ctas | string | no | Comma-separated CTAs, e.g. 'Direct Meeting CTA, Lead Magnet CTA'. Omit to use campaign defaults. |
Submit multiple leads for batch email sequence generation (ASYNC). Returns IMMEDIATELY with a list_id. Processing runs in the background. After calling this, poll get_list_status every 15-30 seconds until processing_status is 'completed' or 'failed', then call export_list. You must have a campaign_id first. Call list_campaigns if you don't have one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_id | string | yes | Campaign UUID from list_campaigns. |
| leads_json | string | yes | JSON array of lead objects. Each MUST have "email". Optional: name, title, company, company_website, linkedin_url. Example: '[{"email":"jane@acme.com","name":"Jane Doe"}]' |
| email_count | integer | no | Number of emails per lead, 1-5. |
| list_name | string | no | Display name for this batch in MachFive UI. |
| email_signature | string | no | Signature appended to each email. |
| campaign_angle | string | no | Additional context/angle for personalization. |
| approved_ctas | string | no | Comma-separated CTAs. Omit to use campaign defaults. |
List lead lists (batch jobs) in the user's MachFive workspace. Useful for browsing past batches, checking what's in progress, or finding a list_id to export. Results are ordered newest first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_id | string | no | Filter by campaign UUID. |
| status | string | no | Filter by processing status: 'pending', 'processing', 'completed', or 'failed'. |
| limit | integer | no | Max results to return, 1-100. |
| offset | integer | no | Pagination offset. |
Check the processing status of a lead list. Use this to POLL after calling generate_batch. Call every 15-30 seconds until processing_status is 'completed' or 'failed'. When completed, call export_list. When failed, submit a new batch.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | List UUID from generate_batch or generate_sequence response. |
Download the generated email sequences for a COMPLETED list. Only call this AFTER get_list_status shows processing_status = 'completed'. If the list is not yet completed, you'll get a 409 error — poll first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | string | yes | List UUID to export. |
| format | string | no | Output format: 'json' (structured data) or 'csv' (raw CSV for sending tools). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Cold Email or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Cold Email can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.