Skip to main content
Connect Claude to Brew to create branded emails, work with your audiences, and read results from the same conversation. Start with a read-only brand check, then ask for one editable draft. Use the custom connector steps for Claude Desktop or Claude web. If you work in a terminal, follow Claude Code below.

Requirements

  • A Brew account with access to your brand
  • A Claude account that can add custom connectors, or Claude Code installed for the terminal path
  • A browser to sign in with Brew and approve access
Free Claude accounts are limited to one custom connector. Team and Enterprise members need their organization to add the connector first. See Claude’s connector setup for current account requirements.

Connect Claude Desktop or Web

1

Add the Brew connector

Open Customize → Connectors → + Add → Add custom connector. If Brew is already listed, use that connection instead.Name the connector Brew and enter:
Select Continue and review the detected authentication settings. Choose Sign in now or Sign in when needed. If Claude offers an OAuth client choice, select Register automatically for Brew’s automatic client registration.Finish adding the connector. This path uses browser sign-in, so leave fixed API-key headers empty.
On Team or Enterprise, an authorized administrator adds Brew first: Organization settings → Connectors → Add → Custom → Web. Members then connect individually.
2

Sign in with Brew

Select Connect on the Brew connector. In the browser, sign in with Brew and choose the brand you want Claude to use. Review the requested access before approving it.
Brew’s brew:all OAuth scope includes read and write access to your selection. Choose one brand unless you need the whole organization. A read-only prompt limits Claude’s task, not its credential.Review scopes and confirmation.
3

Enable Brew in your conversation

Return to Claude. Open the conversation’s + → Connectors menu and enable Brew.Paste the verification prompt below before asking Claude to create anything.

Verify Your Brand

Replace the brackets and send:
Check that the returned brand is yours. The connector being enabled doesn’t establish that a tool call succeeded. If the brand is still being extracted, wait until it is ready before generating an email. An organization connection requires a brand_id for brand-scoped tools. Ask Claude to list your brands and use the selected ID, or reconnect to one brand. MCP Authentication and Scoping owns those rules.

Connect Claude Code

Run this in your terminal:
--scope user makes the server available across your projects. Omit it for the current project’s local configuration. Start Claude Code and open /mcp. Select Brew and complete browser authentication, choosing your brand. Confirm that Brew is connected, then run the brand verification prompt. Adding the server URL saves configuration; authentication and a successful tool call complete the setup. See Claude Code’s MCP guide for client configuration and policy options.

Create and Review a Draft

Email generation uses Brew credits. After verification, ask for one draft:
Claude uses create_email. If it returns generating, Claude should poll get_email with the returned emailId and runId. Repeating creation starts another billed design. Open the preview and Brew link. Check the facts, branding, images, and links before approving further work. For a focused revision, send:
Content changes use edit_email and also use credits. A rename, subject change, or folder move alone uses the free update_email_metadata tool.

Set Your Approval Boundaries

Give Claude instructions for later work:
For production delivery, choose a sendable marketing domain and an opted-in audience. OAuth sends return a confirmation request first. After your approval, Claude repeats the exact call with confirmed: true and its confirmation_id. Always include idempotency_key in send_email, including test sends. Reuse the same key and send inputs when confirming or retrying that send. Use a fresh key for a separate intended send. See Safe Retries for the full contract. Run Your Email Ops from an AI Agent covers the full draft, review, test, and send workflow. MCP Workflows covers audiences, automations, and analytics. Neither a draft nor an accepted send proves inbox delivery.

Watch the Walkthrough

Connect Claude with MCP shows the connector, brand authorization, email creation, and a scheduled send. It was recorded before Brew MCP 3.0; the video page explains the changed contact tools. Use this guide and the current tool catalog for today’s behavior.

Troubleshooting

Disconnect Brew

Remove the custom connector from Customize → Connectors when you no longer want it in Claude. Revoke the matching authorization in Brew under Settings → MCP → Connected via OAuth to end that grant. For Claude Code configuration, use claude mcp remove brew --scope user if you added it with user scope. Revoke its Brew grant too.

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.