Skip to main content
Brew ships an MCP server with tools for design generation, editing, audiences, sends, automations, and analytics. Connect it to the AI client you already work in. Your email ops become part of the same chat where you plan them. This recipe walks through one session: draft a newsletter, request checks, review a test, and approve a send. Open Brew or your inbox when a step calls for it. The tool catalog lists everything else the server can do.
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:
These instructions set your workflow preferences; they don’t reduce the connection’s permissions. Brew’s own confirmation gate doesn’t apply to a test sent to the connected person. Confirmation has the server’s rules. The retry lines cover send_email, test sends included, and the other fail-closed tools such as audit_email and create_inbox_placement_test. Safe Retries has the full contract. For marketing consent, see What You Can Send with Brew.

2. Draft the Email

Generation uses Brew credits. After your brand is ready, replace the brackets and request one draft:
The agent calls create_email. If the result is still generating, it should poll get_email with the returned emailId and runId. Calling create_email again starts another billed design. Open the preview and the Brew link. Check the facts, branding, images, and destination links. If your client doesn’t display a preview, inspect the design in Brew before approving further work.

3. Iterate in the Same Chat

Identify the existing design by its Brew link or email ID:
Content edits use edit_email, create a version, and use credits. If the edit is still running, poll get_email with its returned IDs. You can restore an earlier version if needed. A rename, inbox subject change, language change, or folder move alone uses the free update_email_metadata tool, which creates no version.

4. QA with Agent Tools

The full pre-send routine is available as tools:
  • “Preview this across Gmail, Outlook, and iOS dark mode” runs test_email_rendering, which starts a paid rendering job and returns a previewId. The agent polls get_email_rendering with that previewId and returns a screenshot per client.
  • “Audit this before we send it” runs audit_email and 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” runs send_email with test: true, which sends a one-off test to your inbox and never touches your audience. Check your inbox after the tool accepts it.
  • “Check whether this lands in the inbox or spam” runs create_inbox_placement_test, a seed send across real providers. It returns queued or running, so ask the agent to poll get_inbox_placement_results with the emailId and testId until it completes.
  • “Validate the Newsletter subscribers audience before we send” reads all pages of the audience’s addresses with search_contacts, then checks them with validate_contacts 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:
On OAuth and organization connections, send_email returns a confirmation request before a production send. Review the recipients, sender, subject, preview, and timing. After approval, the agent repeats the exact call with confirmed: true and the returned confirmation_id. A brand API key skips Brew’s confirmation gate. Your working instructions still require approval before sending. MCP Authentication and Scoping describes the connection-specific behavior. Check the send’s status and your test inbox. An accepted send isn’t proof of inbox delivery.

6. Where This Goes Next

The same session can run the rest of your email program:
  • Audiences. “Create an audience of contacts on the Pro plan who joined this quarter” (create_audience).
  • Contact imports. “Import this CSV of webinar sign-ups” (import_contacts_csv, or import_contacts for rows the agent already holds). Missing contacts are created and existing ones updated, and the batch appears in Import History. On OAuth and organization connections the import returns a confirmation request first. Check how many contacts it would add as subscribed before you approve it.
  • Automations. “Build a 3-step welcome flow triggered by user signup” (save_automation), then test and publish it from chat.
  • Audience automations. “Run this follow-up sequence for Newsletter subscribers” (the run_audience_automation workflow, which ends with the run_automation tool). Review tests and a dry-run recipient count before approving the launch.
  • Analytics. Next week: “How did the newsletter perform against our last three sends?” (get_email_analytics with report: { kind: "sends" } for the per-send stats, or kind: "overview" for the totals, rates, and timeseries the app shows).
  • Design import. “Turn this Figma frame into an email” (import_email with source.kind set to figma), which converts one frame deterministically and for free.
  • Images. add_image can host an image from a public URL. A local file uses create_image_upload, a separate upload request, then add_image with the returned upload ID. 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 held and restarted with pause_email_send or resume_email_send, passing its sendId. cancel_email_send permanently stops 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.

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:

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.