agent-cold-email
Advanced tools
CLI for agent-cold-email, agent-native cold-email infrastructure: provision isolated branded domains and mailboxes, run sequences, and manage replies with one bearer token. Run `npx agent-cold-email demo` for a no-signup sandbox demo, no card, no real ema
The agent-cold-email command-line client for the agent-cold-email cold-email
infrastructure API (see the repo root README.md / AGENTS.md for what the
platform is). Nine of the ten commands are thin wrappers over the HTTP
facade — no logic beyond argument parsing and printing; every one hits
https://agent-cold-email-api.yaakovscher.workers.dev (or $AGENT_COLD_EMAIL_API)
directly. The tenth, mcp, bridges MCP-over-stdio to the same hosted API's
/mcp endpoint — see below.
Live. Published on npm as
agent-cold-email@0.2.1. The API it talks to is live in production, including real sending (Gmail API, HTTPS/443);demostill runs against sandbox vendor adapters only (no real domains, mailboxes, or sends) — see Pricing below and the repo rootREADME.mdfor full status.
npx agent-cold-email demo
The demo command above is free, today — no signup, no card, no waitlist.
Real sending is live in production: starts at $99/month for 5 provisioned
mailboxes, then $10/month per additional mailbox (a $49 platform fee +
$10/mailbox, 5-mailbox minimum) — all-in, $0 per-send fees; the subscription
charge tracks your provisioned mailbox count (minimum 5), not a number you
pass at checkout time. No send quota — sends are not the billing meter.
Live billing (Stripe, self-serve checkout) is live; going live is self-serve
(POST /checkout returns a hosted Stripe payment link), and real mailbox
provisioning is fully self-serve and automatic — mailbox send-authorization
completes on our side after provisioning, and you don't wait on a queue or
do anything. Full ladder and calculator:
coldrig.dev/pricing.
npx agent-cold-email demo
Mints a disposable demo tenant, provisions sample branded domains and
mailboxes, and runs the accelerated sandbox pipeline end to end: warmup,
sends respecting per-mailbox caps, replies, bounces, and a stop-on-reply
proof — all against a fault-injecting simulator, never a real domain,
mailbox, or inbox. Ends with an honest line: this ran in a sandbox, no real
emails were sent — real sending is live in production, and going live on
your own account is self-serve (POST /checkout, pay, done); mailbox
send-authorization then completes on our side after provisioning, and you
don't wait on a queue or do anything. Building from source instead
(e.g. to test an unreleased change)? Run node dist/index.js demo after
the build steps in How to run below.
| Command | What it does |
|---|---|
demo | The hero command — see above. |
signup --brand <name> --email <email> | POST /signup; prints the tenant id + bearer token. |
setup [--brand ...] [--domains N] [--inboxes-each N] ... | POST /setup-infrastructure. |
status | GET /infrastructure-status. |
campaign launch --file <campaign.json> | POST /campaigns with the file as the request body. |
campaign results <campaignId> | GET /campaigns/{id}/results. |
inbox | GET /inbox. |
inbox thread <id> | GET /threads/{id}. |
inbox reply <id> <body> | POST /threads/{id}/reply. |
inbox mark <id> <read|unread|archived> | POST /threads/{id}/mark. |
metrics | GET /metrics. |
pause <campaignId> / pause --all | POST /campaigns/{id}/pause / POST /campaigns/pause-all. |
account | GET /account. |
mcp | Serve MCP over stdio, bridged to the hosted endpoint — see below. |
Every authed command needs a token: pass --token <token> or set
AGENT_COLD_EMAIL_TOKEN (demo and signup are the only exceptions — they
mint their own tenant).
mcp — stdio MCP serveragent-cold-email mcp serves MCP over stdio, bridged to the hosted
streamable-HTTP endpoint (the standard "mcp-remote" pattern, built on the
official @modelcontextprotocol/sdk). This is what makes the npm package
directly installable as an MCP server, per the registry
quickstart,
as an alternative to pointing a client straight at the hosted remote (see
the repo root llms-install.md).
Client config (e.g. claude_desktop_config.json / mcp.json):
{
"mcpServers": {
"agent-cold-email": {
"command": "npx",
"args": ["-y", "agent-cold-email", "mcp"],
"env": {
"AGENT_COLD_EMAIL_API_KEY": "<your bearer token>"
}
}
}
}
Without a key, initialize/tools/list still work (the hosted endpoint
allows unauthenticated introspection) but tools/call fails with a
JSON-RPC error until one is set — get one with signup or demo above.
Prefer to skip the stdio bridge and point Codex straight at the hosted
remote endpoint instead? Add this to ~/.codex/config.toml (set
COLDRIG_TOKEN to your bearer token first):
[mcp_servers.coldrig]
url = "https://agent-cold-email-api.yaakovscher.workers.dev/mcp"
bearer_token_env_var = "COLDRIG_TOKEN"
Same remote-endpoint setup for Claude Code, Cursor, and Cline at coldrig.dev/connect.
AGENT_COLD_EMAIL_API — API base URL for the REST commands. Default: https://agent-cold-email-api.yaakovscher.workers.dev.AGENT_COLD_EMAIL_TOKEN — bearer token for the REST commands, used when --token isn't passed.AGENT_COLD_EMAIL_API_KEY — bearer token for mcp mode.AGENT_COLD_EMAIL_BASE_URL — API base URL override for mcp mode. Default: same as AGENT_COLD_EMAIL_API's default.npm install # from repo root (npm workspaces)
npm run typecheck -w agent-cold-email
npm run build -w agent-cold-email # emits dist/ (tsc, NodeNext ESM)
node packages/cli/dist/index.js demo
src/client.ts — the one HTTP client (request(), pollUntil(), token/base-URL resolution).src/flags.ts — a minimal dependency-free --flag value / positional-arg parser.src/commands/*.ts — one file per command group, each a thin request() wrapper (except mcp.ts, the stdio↔streamable-HTTP bridge).src/index.ts — the #!/usr/bin/env node bin entry; dispatches process.argv to a command.test/ — behavior tests for mcp mode (node --test); the nine REST commands have no test lane yet (thin wrappers, covered indirectly by the platform's own HTTP tests).The nine REST commands: nothing beyond Node's built-in fetch/fs (Node
=18). No
@coldstart/*workspace dependency — they only ever talk HTTP, matching the "one bearer token, no vendor SDKs" pitch inAGENTS.md.
mcp mode is the one exception: it depends on the official
@modelcontextprotocol/sdk to speak stdio↔streamable-HTTP MCP correctly
(hand-rolling that framing would be exactly the kind of protocol
reimplementation the SDK exists to avoid). This is the package's only
runtime dependency.
FAQs
CLI for agent-cold-email, agent-native cold-email infrastructure: provision isolated branded domains and mailboxes, run sequences, and manage replies with one bearer token. Run `npx agent-cold-email demo` for a no-signup sandbox demo, no card, no real ema
We found that agent-cold-email demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A misconfiguration gave three Anthropic models internet access, and one, believing it was in a simulation, shipped a credential-stealing package to PyPI.
Security News
/Company News
Socket has joined the new Composer and Packagist sponsorship program as a launch sponsor, supporting the team that keeps PHP's package ecosystem secure.
Research
/Security News
Benign-looking npm packages split malicious functionality across a dependency chain that deploys a cross-platform RAT targeting Alibaba developers.