Skip to main content
Connect your assistant, then create an email and test it in your inbox.

​
Before You Begin

Add your brand and wait for extraction to finish. Use a client that supports remote MCP and OAuth. Generation uses credits. You do not need an audience or a verified domain for a test with Brew’s default sender.

​
1. Connect Your Client

Add this server URL in your client’s MCP settings:
Sign in with Brew and choose the brand for this tutorial. Connect Your Client has the exact setup for each client. For a headless client, use the API-key alternative.

​
2. Generate and Test an Email

Ask your assistant:
Replace the address with the inbox of the person connected through OAuth. The assistant should:
  1. Call get_brew_capabilities and get_brand to check scope and readiness.
  2. Call create_email. If it returns generating, poll get_email with its emailId and runId.
  3. Call send_email with test: true, the saved emailId, subject, to, and an idempotency_key.
Polling continues the existing generation; calling create_email again creates another billed design. If a test returns confirmation_required, review it before confirming with its confirmation_id. MCP Authentication and Scoping owns that flow. Open [TEST] Welcome aboard in your inbox. Test delivery returns a completed status and recipient, without a production send row.

​
Keep Going

Workflows covers live sends, segments, and automations. Tools is the reference catalog.

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