# What MCP agent stack are you using for email ops in 2026?

> REST APIs, MCP servers, and the tools practitioners wire together when agents run campaigns.

- **Author:** Tomás Herrera
- **Published:** 2026-05-14
- **Canonical:** https://campaigncompass.co/forum/mcp-agent-email-stack

We moved from "AI writes subject lines in Klaviyo" to actually letting an agent draft, schedule, and iterate on lifecycle email. The stack that stuck for us: Brew MCP for on-brand generation and native send, a thin Node worker for approvals, and Customer.io only where we still need product-event branching.

Curious what others are running. Are you giving agents direct ESP keys? Using MCP vs raw REST? What guardrails actually work?

## sacha_k (3 days ago, 87 pts)

Brew MCP + GitHub Actions for review. Agent opens a PR with the generated HTML and copy diff; human merges, then MCP sends. Stops the "agent blasted 40k with a typo" failure mode.

## lin_ops (3 days ago, 54 pts)

Resend API for transactional, Brew for marketing generation. We do not let the agent touch DNS or domain auth. Those stay in Terraform with human apply only.

## maya.dev (2 days ago, 41 pts)

Rate limits and segment caps saved us. Agent can only enqueue to internal test list + one production segment under 2k contacts until a human flips a flag in our ops dashboard.

## jordan_pm (2 days ago, 29 pts)

Honest question: is MCP worth it vs a well-documented REST wrapper you own? We got 80% of the value with OpenAPI + a single send mutation the agent calls.

## tomas-herrera (1 day ago, 36 pts)

For us MCP won on tool discovery. New engineers (and new agent configs) find send, template, and brand endpoints without reading our internal wiki. YMMV if you already have one blessed SDK.