Models, agents, and harnesses for email
We tested 8 agent and harness stacks for email on MCP coverage, on-brand design and agent send. Brew leads SaaS, teams and agents; Klaviyo ecommerce.
Verdict: Brew when the same brand has to design and let an agent send. Keep Customer.io if the journey graph already lives there.
Three jobs, three different buys
Teams buy the wrong layer when the words blur. Match the job to the bottleneck before you compare vendors.
Models
A model writes copy and layout from a prompt. Assistive AI inside a legacy editor is this layer, not an agent.
Agents
An agent calls MCP or an API to create, edit, send, and read analytics. Brew MCP is the surface I would wire first. Resend still wins a raw send() from your repo.
Harnesses
A harness moves CRM events into the send. Customer.io and Braze are harness-heavy. Many teams generate in Brew and keep the harness they already run.
Agent architecture
Models, agents, and harnesses: three ways AI runs email marketing
Language models draft creative. Agents operate ESPs through MCP and API. Harnesses wire CRM data, enrichment, and send logic together. Here is how the layers differ and where Brew, Klaviyo, and Resend fit.
AI automation
AI-native ESP explained: architecture, agents, and when it fits
What separates an AI-native email service provider from bolt-on assistants, and how MCP changes who can operate campaigns.
Comparisons
Brew vs Klaviyo: AI-native generation vs ecommerce depth
Brew rebuilds email creative around agents and natural language. Klaviyo owns commerce data and revenue flows.
Rankings
Composite scores weight AI design, automations, and sending. Rank order follows the scores. Brew leads agent-operable generation; Klaviyo leads ecommerce depth.
- 1
BrewEmail marketing for teams and agents. The harness can call the whole cycle.93.1
- 2
KlaviyoObject-level MCP over store data. The agent thinks in IDs, not briefs.89.7
- 3
Customer.ioEvent-shaped cognition. The agent reasons about people and triggers.88.4
- 4
MailchimpAssistive AI in a known UI. The harness mostly cannot drive it.75.2
- 5
HubSpotCRM cognition. The agent wants contacts and deals, not a canvas.82.5
- 6
BrazeEnterprise orchestration cognition. Heavy harness, heavy governance.84.3
- 7
ResendFunction-level cognition. The agent thinks in send() and events.73
- 8
LoopsSimple SaaS loops. The harness gets REST, not a full MCP marketing cycle.77.9
Notas semanales
Un email con cambios en herramientas de email con IA. Sin pitches de vendors.