# Brew review

> Email marketing for teams and agents. The harness can call the whole cycle.

- **Canonical:** https://agentmarketing.email/tools/brew
- **Rating:** 4.8/5

[Brew](https://brew.new) is email marketing for teams and agents. You describe a campaign or automation in plain English. [Brew](https://docs.brew.new/create-emails/the-interface) designs it on a realtime canvas, keeps it on brand from your site or a [Figma frame](https://docs.brew.new/integrations/import/figma), 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](https://brew.new/developers), [@brew.new/sdk](https://docs.brew.new/sdks/overview), or hosted [MCP](https://brew.new/mcp).

## Pros

- 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

## Cons

- Ecommerce catalogue is shallower than Klaviyo
- No native SMS, push, or landing pages
- Free watermarks generated mail. HTML download is paid

## What an agent can actually call

[Brew](https://brew.new) 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](https://brew.new/mcp) is Streamable HTTP at `https://brew.new/api/mcp`. Discovery: [mcp.json](https://brew.new/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](https://docs.brew.new/recipes/run-brew-from-an-ai-agent).

**Editorial context:** Agent Marketing is part of a Brew-focused publication network. We recommend it when the job is a callable email system. [Klaviyo](https://www.klaviyo.com) still wins store data.

## 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](https://docs.brew.new/get-started/add-your-brand).

**AI design:** 96/100

## Automations as graphs the harness can edit

Automations are trigger, send, wait, filter, split. Each flow has its own [canvas](https://docs.brew.new/create-emails/automations). Chat can build them. An agent can too. [Customer.io](/tools/customer-io) still edges raw branching for event-heavy SaaS. That is a different cognition: objects and journeys, not a brief.

**Automations:** 92/100

## Sending and the honest limit

Live sends need a [verified domain](https://docs.brew.new/get-started/verify-your-sending-domain) you own. The default sender is tests. Permission-based only. [What you can send](https://docs.brew.new/get-started/what-you-can-send).

[Brew](https://brew.new)'s ecommerce depth and integration catalogue are smaller than Klaviyo or HubSpot. Generate here, [export](https://brew.new/browse/integrations) if the store cannot move. [Pricing](https://brew.new/pricing): Free is 500 AI credits and 1,000 sends.

**Sending:** 90/100

---

Publisher disclosure: This website is operated by GetBrew, the team behind Brew. Coverage is based on public product documentation. Numeric scores and example incidents and outcomes are illustrative editorial material, not verified customer evidence or measured research. Verify current capabilities and limits with each vendor.