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 brand:
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 pick a brand. That’s it: Brew is its own OAuth 2.1 authorization server, so the token is issued and scoped to that brand for you (revocable anytime in Settings → MCP).
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 a brand-scoped API key as a bearer header instead.

​
3. Run Your First Workflow

Ask your agent to call get_brew_capabilities first. It returns the connection’s scope, the tool catalog by topic, the conventions for errors, retries, and pagination, and the end-to-end workflows. Paid tools say so in their own descriptions. The server also ships guided prompts (launch_email_campaign, build_segment_and_send, …) that your client can surface directly. A first campaign, end to end:
  1. create_email: generate an on-brand email from a prompt. If it comes back generating, poll get_email with the emailId and runId. Calling create_email again starts a second billed design.
  2. send_email with test: true and your own address in to to QA it. A test to anyone else asks for approval first.
  3. list_domains with sendableOnly: true and sendingPurpose: "marketing" for a verified sender, then list_audiences (or create_audience).
  4. On the recommended OAuth connection, call send_email with the emailId, subject, audienceId, domainId, and a unique idempotency_key, but omit confirmed. Brew returns confirmation_required without sending.
  5. Show the preview and exact recipient count (list_audiences with the audienceId and include: ["count"] if needed) and get explicit approval.
  6. Only after approval, call send_email again with the same inputs, confirmed: true, and the confirmation_id from step 4.
  7. get_email_analytics with report: { kind: "sends", sendId } to measure (omit sendId to list recent sends).
Brand API-key connections are intended for programmatic use and do not pause at the 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 explore it further with ChatGPT or Claude.