Skip to main content
Brew ships an MCP server that exposes the whole platform as tools: design generation, editing, audiences, sends, automations, and analytics. Connect it to the AI client you already work in and your email ops become part of the same chat where you plan them. This recipe walks through one realistic session: draft a newsletter, QA it, test it, and send it, all from chat. The pattern extends to everything else the tool catalog covers.
Before you start. You need a Brew account, an AI client that supports MCP connectors (Claude, ChatGPT, Cursor, VS Code, and most agent tools), and a verified sending domain if you plan to send for real.

​
1. Connect Your Client

Add the connection URL as a custom connector (Claude, ChatGPT) or drop it into your client’s mcp.json (Cursor, VS Code, and most others): 
https://brew.new/api/mcp
On first connect your browser opens: sign in with Brew and pick a brand. The token is issued and scoped to that brand, and you can revoke it anytime in Settings → API. Per-client steps are on Connect your client.
Ask the agent “What can you do with Brew?” as your first message. It calls get_brew_capabilities and reports the tools and guided workflows available.

​
2. Draft the Email

Describe the send the way you’d brief a designer:
“Create this week’s product update newsletter. Three sections: the new inbox previews feature, the two bug fixes from the changelog, and a customer quote. Keep it text-forward with one CTA to the changelog.”
The agent calls create_email_design and returns an Open in Brew link. Click it to see the design in the app; email is visual, so review the render, never just the agent’s description of it.

​
3. Iterate in the Same Chat

Edits go through edit_email_with_ai, so revision is conversational:
“Shorten the intro to two sentences and swap the CTA button to say ‘Read the changelog’.”
Every edit creates a new version in Brew, so you can restore an earlier one if a change goes the wrong way.

​
4. QA Without Leaving Chat

The full pre-send routine is available as tools:
  • “Preview this across Gmail, Outlook, and iOS dark mode” runs preview_email_across_clients and returns a screenshot per client.
  • “Run an accessibility audit” runs audit_email_accessibility and returns a WCAG 2.1 score with the issues to fix.
  • “Send me a test” runs send_email with test: true, which delivers a one-off test to your inbox and never touches your audience.

​
5. Send It

Ask for the real send:
“Send it to the Newsletter subscribers audience tomorrow at 9am.”
A campaign send is irreversible, so Brew makes the agent stop first: send_email returns a confirmation request with the exact recipient count, the agent shows it to you, and the send only goes out after you approve. Treat that pause as part of the workflow, and read the count before you say yes.

​
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).
  • Automations. “Build a 3-step welcome flow triggered by user signup” (create_automation), then test and publish it from chat.
  • Analytics. Next week: “How did the newsletter perform against our last three sends?” (get_campaign_analytics).
For the full tool list see MCP tools, and for multi-step patterns see MCP workflows. If you’re wiring Brew into a coding agent that also builds your product, Use Brew with AI agents covers that side.

​
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.

ChatGPT/Claude Integration

Click “Open in ChatGPT” at the top right of any page to analyze documentation with ChatGPT or Claude for deeper insights.