Before you start. You need a Brew account and an AI client that supports plugins or
remote MCP connections. ChatGPT, Claude, Grok, Cursor, Codex, VS Code, and
most agent tools do. A verified sending
domain is also required if you
plan to send for real.
1. Connect Your Client
Use the setup guide for your client, then complete its read-only brand check: Connect Your MCP Client covers ChatGPT web and other clients. MCP Authentication and Scoping explains brand access and revocation. For a new brand, follow Configure a Brand and Domain before starting this recipe.Approval and Retry Instructions
Give your agent these working instructions after setup:2. Draft the Email
Generation uses Brew credits. After your brand is ready, replace the brackets and request one draft:3. Iterate in the Same Chat
Identify the existing design by its Brew link or email ID:4. QA with Agent Tools
The full pre-send routine runs from the same chat:“Preview this across Gmail, Outlook, and iOS dark mode.”This starts a paid rendering job. The agent checks the job until it finishes, then returns a screenshot per client.
“Audit this before we send it.”The audit returns readiness, check coverage, size metrics, and the findings to fix. A partial result is free and does not establish readiness.
“Send me a test.”This sends a one-off test to your inbox and never touches your audience. Check your inbox after Brew accepts it.
“Check whether this lands in the inbox or spam.”This is a seed send across real providers. It starts out queued or running, so ask the agent to check the results until the test completes.
“Validate the Newsletter subscribers audience before we send.”The agent reads every page of the audience’s addresses, then checks them in batches of up to 100. Review the verdicts before sending. Validation doesn’t guarantee delivery. MCP Tools lists limits and costs.
5. Send It
Choose a sendable marketing domain and an opted-in audience, then ask the agent to prepare the send:6. Where This Goes Next
The same session can run the rest of your email program: Audiences. Save a filtered audience:“Create an audience of contacts on the Pro plan who joined this quarter.”Contact imports. The agent can import a CSV file or rows it already holds:
“Import this CSV of webinar sign-ups.”Missing contacts are created and existing ones updated, and the batch appears in Import History. On OAuth and organization connections, the agent asks you to approve an import first. Check how many contacts it would add as subscribed before you approve. Automations. Build a flow, then test and publish it from chat:
“Build a 3-step welcome flow triggered by user signup.”Audience automations. This follows the audience automation workflow, which ends by launching the run:
“Run this follow-up sequence for Newsletter subscribers.”Review tests and a dry-run recipient count before approving the launch. Analytics. Next week, ask how a send did:
“How did the newsletter perform against our last three sends?”The agent can return per-send stats, or the totals, rates, and timeseries the app shows. Design import. Converting one Figma frame is deterministic and free:
“Turn this Figma frame into an email.”Images. The agent can host an image from a public URL:
“Host the image at https://example.com/hero.png in Brew.”A local file takes a separate upload request first, then the same add step. That path needs an agent that can send file bytes. Attaching a file in chat alone does not complete the upload; Upload a Local Image covers the transfer. Send control. A gradual send already in flight can be paused and resumed:
“Pause the gradual send of the spring sale email.”Canceling instead permanently stops the remaining deliveries. For the full tool list see MCP Tools, and for multi-step patterns see MCP Workflows. Wiring Brew into a coding agent that also builds your product? Use Brew with AI Agents covers that side. If your agent runs shell commands, the Brew CLI offers a terminal path for supported operations.
Troubleshooting
From an Agent or Code
Before translating this recipe to HTTP or the terminal, check which operations each interface offers. Some MCP tools combine several API operations, and some are MCP-only. MCP Tools lists HTTP equivalents where available. CLI Commands lists terminal operations, and Build with Brew compares the four interfaces.Related
- Connect Your MCP Client: setup per client.
- MCP Workflows: the guided multi-step prompts.
- Use Brew with AI Agents: wiring Brew into an agent that also builds your product.
- Use the CLI from AI Agents: the same work from a coding agent’s terminal.
- QA an Email Before a Big Send: the full pre-send routine step 4 runs.
Need Help?
Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you:- Self-Service Tools
- Talk to Our Team
Search Documentation
Type in the “Ask any question” search bar at the top left to instantly find relevant documentation pages.
Ask ChatGPT or Claude
Click here to open the Copy page menu at the top of this page, then send the page to ChatGPT, Claude, or your editor.