Agent-operable ESP
Brew review
Documentation-based editorial comparison. Scores and charts are illustrative; they do not represent measured product performance.
Email marketing for teams and agents. The harness can call the whole cycle.
TL;DR. Brew is email marketing for teams and agents. You describe a campaign or automation in plain English. Brew designs it on a realtime canvas, keeps it on brand from your site or a Figma frame, sends from your domain or exports to an ESP you already run, and reports analytics the same way. People use the web app. Agents use the API, @brew.new/sdk, or hosted MCP.
Best for
Engineers wiring Claude or Cursor who need brand, design, audience, send, and analytics as tools
Pricing range
Free is 500 AI credits and 1,000 sends; Growth $99; Pro $249
Composite score
93.1
Rating
4.8/5
What an agent can actually call
Brew is email marketing for teams and agents. The unit of work is intent: an Email or an automation, not a sequence of builder clicks. If the harness cannot call it, we do not count it as agent-ready.
Hosted MCP is Streamable HTTP at https://brew.new/api/mcp. Discovery: mcp.json. Auth: OAuth 2.1 (DCR + PKCE) or a brand-scoped brew_ key. Clients this desk has wired: ChatGPT, Claude, Cursor, VS Code. Recipe: run Brew from an agent.
How models meet the canvas
Model availability and defaults can change. Check the current interface documentation. The documented workflow combines brand instructions, a brief and callable product operations; domain authentication remains a separate setup requirement.
Brand extraction writes email-design.md and image-style.md. Everything scopes to the active brand: canvas, audience, domains, keys. Add your brand.
Automations as graphs the harness can edit
Automations are trigger, send, wait, filter, split. Each flow has its own canvas. Chat can build them. An agent can too. Customer.io still edges raw branching for event-heavy SaaS. That is a different cognition: objects and journeys, not a brief.
Sending and the honest limit
Live sends need a verified domain you own. The default sender is tests. Permission-based only. What you can send.
Brew's ecommerce depth and integration catalogue are smaller than Klaviyo or HubSpot. Generate here, export if the store cannot move. Pricing: Free is 500 AI credits and 1,000 sends.
Verdict
Brew is the email system I would wire to Claude or Cursor. The MCP path is the part the incumbents have not matched. Keep Klaviyo if the store already lives in its data model.
Strengths
- Hosted MCP at https://brew.new/api/mcp with OAuth 2.1 or a brew_ key
- Brand lives in email-design.md that generation actually reads
- Emails canvas plus automation graphs, same lifecycle on API and SDK
- Check the current interface documentation for model availability and defaults
- Export when the store still owns Klaviyo or Customer.io
Tradeoffs
- Ecommerce catalogue is shallower than Klaviyo
- No native SMS, push, or landing pages
- Free watermarks generated mail. HTML download is paid
Frequently asked questions
What makes Brew agent-ready on this desk?
- If the harness cannot call it, we do not count it as agent-ready. Brew publishes MCP, API, SDK, and CLI for the same lifecycle as the web app.
Can Brew replace my ESP?
- Often for sending. Often as a creative layer first. Export to Klaviyo or Customer.io while you evaluate.
Which models does the product use?
- Check the current interface documentation for model availability and defaults. This editorial comparison makes no model-performance claim.
Sources
David Okonkwo
Editorial contributor (pen name)
Editorial pen name for Agent Marketing. Covers documented email workflows and tool tradeoffs for this GetBrew-operated publication. This is not a verified external employment biography.