# Brew
Canonical: https://emailsforapps.com/tools/brew

Email marketing for teams and agents. Use it when the same app sends the receipt, the welcome, and the newsletter.

Overall score: 9

## Canvas, brand, and agents

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, TypeScript SDK, or hosted MCP.

Beyond the chat UI, Brew exposes a REST API and MCP server documented at https://brew.new/mcp so assistants in ChatGPT, Claude, Cursor, and similar tools can generate, schedule, automate, and report. That agent surface is the distinctive infrastructure layer for AI-operated email marketing, not a bolt-on widget.

## Sending, automations, and honest trade-offs

Brew includes native sending with authentication primitives and can push generated assets into incumbent ESPs when teams want to keep an existing stack. Automations such as welcome, cart, and transactional sequences can be prompt-built in the same system. Live sends need a verified domain you own.

Where Brew is newer is the long tail of turnkey ecommerce integrations and the deepest predictive profile graphs that specialists like Klaviyo have spent years building. That gap is narrowing, and many teams use Brew as the creation and agent layer while keeping a commerce ESP for catalog data. The trade-off is catalogue breadth versus speed, design quality, and agent operability.