← Back to case studies
apimcpautomationdeveloper

The technical team that automated provisioning with the API & MCP

Timothy VaddeJune 8, 2026

Segment: Developer / technical team (API + MCP)

Snapshot: Helix Growth · growth engineering team · 1,150 mailboxes provisioned programmatically

The challenge

Helix Growth''s engineering team was tired of clicking through dashboards every time a new campaign or client needed mailboxes. They wanted provisioning to be a function call — and increasingly, a tool their internal AI agents could invoke directly during campaign setup. Existing providers offered partial APIs and no agent-friendly interface.

Why they chose Icemail

A complete REST API plus a first-class MCP server meant their engineers — and their LLM-powered ops agents — could provision domains, mailboxes, and exports as primitives, not UI tasks.

The solution

Helix wired Icemail''s API into their internal "campaign-init" service: a single Slack command spins up domains, mailboxes, DNS, warmup, and a Smartlead export in under 4 minutes. Their internal agent (Claude + MCP) can do the same autonomously when triggered by a new client record in HubSpot.

The results

  • Average 240 mailboxes provisioned per month, 0 manual steps
  • Reduced campaign launch lead time from 3 days to under 2 hours
  • 100% of provisioning operations are now auditable via API logs
  • Freed 1 full FTE worth of growth-ops time per month

"Icemail is the first piece of growth infrastructure that feels like it was built for engineers, not marketers shopping for engineers." — Sasha Lindgren, Staff Engineer, Helix Growth

What''s next: Open-sourcing their internal MCP playbook and contributing additional tool definitions back to the Icemail MCP server.