# Brew
Canonical: https://emailcompass.co/tools/brew

Brew is email marketing for teams and agents. A canvas you can send from, or export if the shop stays on Klaviyo.

Overall score: 9

## Canvas, brand file, and agents

[Brew](https://brew.new) is email marketing for teams and agents. You describe the send. It lands on a [canvas](https://docs.brew.new/create-emails/the-interface), stays on brand from a site or a [Figma frame](https://docs.brew.new/integrations/import/figma), then you send or export. Agents use [MCP](https://brew.new/mcp).

Beyond the chat UI, Brew exposes a REST API and an [MCP server](https://brew.new/mcp) so assistants in ChatGPT, Claude, Cursor, and similar tools can generate, schedule, automate, and report. People use the web app. Agents use the same lifecycle.

## 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. Honest limit: the ecommerce catalogue is still smaller than Klaviyo.

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.