reply — agent cold email MCP Tool
reply
(reply) is one of 28 tools on the
agent cold email
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call reply from your client
- Claude Code agent cold email reply run in your project directory
- Claude Desktop agent cold email reply ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agent cold email reply ~/.cursor/mcp.json
- VS Code agent cold email reply .vscode/mcp.json
- Zed agent cold email reply ~/.config/zed/settings.json
- Windsurf agent cold email reply ~/.codeium/windsurf/mcp_config.json
- Cline agent cold email reply ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agent cold email reply ~/.gemini/settings.json
- Grok agent cold email reply .mcp.json (in your project root)
- ChatGPT agent cold email reply Settings → Connectors → Advanced → Developer mode
- Claude.ai agent cold email reply Settings → Connectors → Add custom connector
- LangChain agent cold email reply pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-cold-email https://agent-cold-email-api.yaakovscher.workers.dev/mcpOther tools on this server
- setup_infrastructure
- infrastructure_status
- launch_campaign
- campaign_results
- metrics
- inbox
- thread
- mark
- pause
- pause_all
- account
- remove_mailboxes
- get_dashboard
- configure_dashboard
- label_thread
- list_campaigns
- activity
- get_webhooks
- configure_webhook
- get_byo_domains
- configure_byo_domain
- suppress_lead
- update_lead
- list_leads
- list_messages
- ack_message
- contact_operator
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.