---
ref: tool:brew/generate-email
name: Generate an email
company: company:brew
workflows: [workflow:content-download-nurture, workflow:webinar-follow-up, workflow:outbound-demo-engine, workflow:free-to-paid-activation]
access: [mcp, cli, api]
tags: [capability:write-copy, category:email, has:api, has:cli, has:mcp]
docs: https://docs.brew.new/api-reference/public-v1/emails/generate-an-email-design
updated: 2026-10-11
---

# Generate an email

Generates an on-brand email design from a prompt; a ready result identifies the design and version, while a generating result needs polling.

Note: Costs credits and requires a ready brand. If generating, poll get_email. Keep emailId and emailVersionId; pass both to a send or automation to pin the design.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "brew": { "url": "https://brew.new/api/mcp" } } }
```

Call the MCP tool `create_email`.

Server URL: https://brew.new/api/mcp

### CLI (official)

Install the command, then confirm it runs.

```sh
brew install getbrew/tap/brew-cli
brew-cli --version
```

Run `brew-cli emails generate`.

Set `$BREW_API_KEY` in your environment first (get a key: https://brew.new/settings/api).

### API (official)

- Base URL: https://brew.new/api
- Endpoint: `POST /v1/emails`
- Auth: send the header `Authorization: Bearer $BREW_API_KEY`
- Get a key: https://brew.new/settings/api
- Docs: https://docs.brew.new/api-reference/api/api-introduction

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.