Agent-native cold-email infrastructure: domains, mailboxes, warmup, sequences, replies via 17 tools
Agent-native cold-email infrastructure: domains, mailboxes, warmup, sequences, replies via 17 tools. Exposed over MCP by the agent mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
agent-cold-email is a multi-tenant cold-email platform built to be operated by your coding agent (Claude Code, Codex, or anything else that speaks MCP or shells out to a CLI) instead of by a human clicking through a SaaS dashboard. Sign up, hand your agent one API token, and it drives the whole lifecycle: buy branded lookalike domains, provision and warm mailboxes, launch sequences, manage replies, and report metrics — through a curated set of 25 high-level tools, not a 100+ tool vendor re-export.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Everything the assistant can do here goes through one of these:
setup_infrastructure — Buy branded lookalike domains, provision mailboxes, kick off warmupinfrastructure_status — Provisioning + warmup progress, per-mailbox health, send-readiness datelaunch_campaign — Create and activate a sequence against a lead listcampaign_results — Per-campaign sends, replies, bounces, complaintsmetrics — Account-wide deliverability + warmup healthinbox — Unified reply inbox across all mailboxesthread — One thread's full message historyreply — Send a reply on a thread (stop-on-reply is automatic)mark — Mark a thread read / unread / archivedaccount — Usage, billing, and quotaremove_mailboxes — Downgrade: release your N newest live mailboxes now and lower the billed quantityget_dashboard — List/fetch the tenant's saved dashboard views (layout JSON)You will need one environment variable: COLDRIG_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Agent's toolset — setup_infrastructure, infrastructure_status, launch_campaign and 11 more — is a fair guide to whether it matches your workflow. It is maintained by YS-projectcalc; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Agent's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| setup_infrastructure | Buy branded lookalike domains, provision mailboxes, kick off warmup |
| infrastructure_status | Provisioning + warmup progress, per-mailbox health, send-readiness date |
| launch_campaign | Create and activate a sequence against a lead list |
| campaign_results | Per-campaign sends, replies, bounces, complaints |
| metrics | Account-wide deliverability + warmup health |
| inbox | Unified reply inbox across all mailboxes |
| thread | One thread's full message history |
| reply | Send a reply on a thread (stop-on-reply is automatic) |
| mark | Mark a thread read / unread / archived |
| account | Usage, billing, and quota |
| remove_mailboxes | Downgrade: release your N newest live mailboxes now and lower the billed quantity |
| get_dashboard | List/fetch the tenant's saved dashboard views (layout JSON) |
| configure_dashboard | Create/update/delete a dashboard view — the agent controls the human dashboard's layout |
| label_thread | Set/clear an intent label (interested, not-now, OOO, …) on a reply thread |
{
"mcpServers": {
"agent-cold-email": {
"url": "https://api.coldrig.dev/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| COLDRIG_TOKEN | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.