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 hosted MCP. Brew's ecommerce catalogue is smaller than Klaviyo or HubSpot. Generate here and export the template if the store already lives there.
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.
- Hosted MCP, Public API, and @brew.new/sdk give an agent the same lifecycle as the web app.
Cons
- Integration catalogue is still smaller than decade-old incumbents for long-tail ecommerce connectors.
AI-native creation and agent operability
Brew is email marketing for teams and agents. Describe a campaign or automation in plain English. It designs the send on a realtime canvas, keeps it on brand from your site or a Figma frame, and sends from your domain or exports to an ESP you already run.
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 SPF, DKIM, and DMARC on a domain you own, and can export generated templates 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. Free is 500 AI credits and 1,000 sends. No per-seat fee.
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.