configure_byo_domain — agent cold email MCP Tool
configure_byo_domain
(configure byo domain) 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 configure_byo_domain from your client
- Claude Code agent cold email configure_byo_domain run in your project directory
- Claude Desktop agent cold email configure_byo_domain ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agent cold email configure_byo_domain ~/.cursor/mcp.json
- VS Code agent cold email configure_byo_domain .vscode/mcp.json
- Zed agent cold email configure_byo_domain ~/.config/zed/settings.json
- Windsurf agent cold email configure_byo_domain ~/.codeium/windsurf/mcp_config.json
- Cline agent cold email configure_byo_domain ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agent cold email configure_byo_domain ~/.gemini/settings.json
- Grok agent cold email configure_byo_domain .mcp.json (in your project root)
- ChatGPT agent cold email configure_byo_domain Settings → Connectors → Advanced → Developer mode
- Claude.ai agent cold email configure_byo_domain Settings → Connectors → Add custom connector
- LangChain agent cold email configure_byo_domain pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-cold-email https://api.coldrig.dev/mcp
Other tools on this server
- setup_infrastructure
- infrastructure_status
- launch_campaign
- campaign_results
- metrics
- inbox
- thread
- reply
- mark
- pause
- pause_all
- account
- remove_mailboxes
- get_dashboard
- configure_dashboard
- label_thread
- list_campaigns
- activity
- get_webhooks
- configure_webhook
- get_byo_domains
- 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.