Skip to main content
Connect Brew to your MCP client in two steps, no API key required.

​
1. Add the Connection URL

The connection URL is clean and the same for every credential scope:
Create a plugin in ChatGPT, add it as a custom connector in Claude, Grok, or Manus, or drop it into the client’s MCP config (Cursor, VS Code, Codex, and most others):

​
2. Sign In with Brew

On first connect the client opens your browser: sign in with Brew and choose one brand. Organization admins can instead choose All brands to manage the whole organization. The connection is revocable anytime in Settings → API.
Per-client steps for ChatGPT, Claude Desktop, Claude Code, Grok, Cursor, VS Code, Windsurf, Cline, Goose, OpenCode, Codex, and Manus are on Connect your client. Headless or CI setup with no OAuth UI? Use an API key as a bearer header instead.

​
3. Run Your First Workflow

Ask your agent to call get_brew_capabilities first. It returns the catalog (scopes, credit costs, the error envelope) plus the end-to-end workflows. The server also ships guided prompts (launch_email_campaign, build_segment_and_send, …) that your client can surface directly. On an organization connection, bootstrap a brand before running a brand workflow:
  1. list_brands
  2. create_brand if needed
  3. get_brand_status until the brand is ready or failed
  4. Pass the returned brandId as brand_id to brand-scoped tools
A first campaign, end to end:
  1. create_email_design: generate an on-brand email from a prompt.
  2. send_email with test: true to QA it.
  3. list_domains (a verified sender) + list_audiences (or create_audience).
  4. On the recommended OAuth connection, call send_email with the audienceId, domainId, and a unique idempotency_key, but omit confirmed. Brew returns confirmation_required without sending.
  5. Show the preview and exact recipient count (load the audience count if needed) and get explicit approval.
  6. Only after approval, call send_email again with the same inputs and confirmed: true.
  7. get_send_analytics + get_campaign_analytics to measure.
API-key connections are intended for programmatic use and do not pause at the OAuth confirmation gate. Obtain approval before the first real send_email call and call it only once.
That’s the full create → send → analyze loop. See Workflows for more, including composing with a CRM MCP for intelligent segments.

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