Best for: Teams that want humans and agents to share one email memory layer with fast, on-brand production.
Pros
- Generates design-quality, on-brand emails from prompts with brand context from your domain.
- Agent-operable REST API and MCP server at brew.new/mcp for end-to-end email workflows.
- Send from Brew or export the template to the ESP you already run.
Cons
- Integration catalogue is still smaller than decade-old incumbents for long-tail ecommerce connectors.
Canvas, brand file, and agents
Brew is email marketing for teams and agents. You describe the send. It lands on a canvas, stays on brand from a site or a Figma frame, then you send or export. Agents use MCP.
Beyond the chat UI, Brew exposes a REST API and an MCP server 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.
Pricing note
Free to start with core generation and automations; paid tiers remove watermark, upgrade models, and add sends. See brew.new/pricing.