Coldrig MCP MCP server

Coldrig provides an agent-controlled cold-email infrastructure with 28 MCP tools. It enables agents to handle the entire outreach lifecycle, including infrastructure setup, domain and mailbox provisioning, campaign launching, and reply management. The server supports live sending via Gmail API and offers a fault-injecting sandbox for testing.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Coldrig

MCP endpoint (Streamable HTTP)

https://api.coldrig.dev/mcp

Vendor documentation

What you can do with it

Provision domains and mailboxes for cold outreach
Launch and manage multi-step email campaigns
Monitor campaign metrics and activity logs
Reply to and manage email threads

Tools advertised by the last live check:

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
configure_byo_domain
suppress_lead
update_lead
list_leads
list_messages
ack_message
contact_operator

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http coldrig-mcp https://api.coldrig.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add coldrig-mcp --url https://api.coldrig.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable coldrig-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "coldrig-mcp": {
      "url": "https://api.coldrig.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "coldrig-mcp": {
      "type": "streamableHttp",
      "url": "https://api.coldrig.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start coldrig-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "coldrig-mcp": {
      "type": "http",
      "url": "https://api.coldrig.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http coldrig-mcp https://api.coldrig.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "coldrig-mcp": {
      "url": "https://api.coldrig.dev/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "coldrig-mcp": {
      "serverUrl": "https://api.coldrig.dev/mcp"
    }
  }
}

See all 347

Do you run Coldrig MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing