> ## Documentation Index > Fetch the complete documentation index at: https://docs.brew.new/llms.txt > Use this file to discover all available pages before exploring further. # Use Brew with Grok Bot > Connect Grok Bot to Brew, verify your brand, and create an editable email draft with browser sign-in and a separate approval before sending. Connect Grok Bot to Brew to create branded emails and manage your email program from chat. Start by connecting your account and reading your brand. Once that works, ask for an editable draft. This guide covers **Grok Bot desktop**. For Grok web and Grok Build, use [Connect Your MCP Client](/api-reference/mcp/connect-your-client). ## Requirements * A Brew account with access to the brand you want to use * Grok Bot desktop, signed in and allowed to add remote MCP connections * A browser to review and approve Brew access You don't need to copy an API key for this OAuth setup. A verified sending domain is needed later for a production send, not for connecting or creating a draft. ## Connect Brew Open a Bot conversation. Replace `[brand name]` and `[website]`, then paste: ```text wrap theme={null} Connect Brew so you can help with my email marketing. Read https://docs.brew.new/api-reference/mcp/connect-your-client and https://docs.brew.new/api-reference/mcp/authentication-and-scoping. Reuse my existing Brew MCP connection if available. Otherwise, propose adding https://brew.new/api/mcp with OAuth. Let me review and approve the connection in my browser. Choose only [brand name] ([website]). After authentication, call get_brew_capabilities and report the scope. Then call get_brand with include: ["identity"]. Confirm the brand name, website, and readiness from the results. State which tools succeeded. During setup, do not create or edit anything, import contacts, generate emails, spend Brew credits, schedule, or send. Do not change domains or unsubscribe settings. Do not ask for API keys in chat. If a step fails, report the exact error and stop. Do not switch to browser automation or another login method. ``` If Grok Bot asks to add the server, check that its URL is exactly `https://brew.new/api/mcp` before approving. Grok Bot displays a Brew connection card. Select **Authorize**, then complete Brew's browser sign-in and choose your brand. Brew's OAuth scope, `brew:all`, gives Grok Bot full access to the brand you select, including writes. A read-only setup prompt limits the task, not the credential. Choose one brand unless you need access across your organization. [Review scopes and confirmation](/api-reference/mcp/authentication-and-scoping). Review the access request before approving it. If the browser asks **Open Grok Bot?** afterward, open the app to finish the return from sign-in. The connection card should show **Connected**. Grok Bot should then report results from: * `get_brew_capabilities`: the connection scope and bound brand ID * `get_brand` with `include: ["identity"]`: the brand name, website, and readiness Check that the returned brand is yours. A connection badge alone doesn't verify that the Bot can use Brew's tools. If the brand is still being extracted, wait until it is ready before creating an email. If the Bot stops after sign-in, send: ```text wrap theme={null} Continue the Brew setup check. Call get_brew_capabilities, then get_brand with include: ["identity"]. Report the scope, brand name, website, and readiness. Keep this read-only. ``` Checked on October 19, 2026: Grok Bot added Brew from chat and completed browser authorization. It reported successful discovery and brand reads. Draft creation, previews, and delivery were not exercised in that check. The next steps use Brew's documented MCP tools. Availability can vary by Grok Bot build and workspace policy. ## Create Your First Draft Draft generation uses [Brew credits](/api-reference/api/credits). Once the connection check succeeds, replace the brackets and request one draft: ```text wrap theme={null} Use Brew for [brand name]. Create one welcome email for people who signed up on our website. Goal: help them [first useful action]. Use our saved brand style and only these approved facts: [facts]. Main link: [destination URL]. Keep it as an editable draft. Show its preview and Open in Brew link. Do not import contacts, run paid checks, schedule, or send. ``` Grok Bot uses `create_email`. If generation is still running, it should poll `get_email` with the returned `emailId` and `runId`. Repeating `create_email` starts another billed design. Open the preview and Brew link. Check the copy, branding, images, and destination links. If the preview isn't available, open the design in Brew before approving further work. For a focused change, identify the design by its Brew link or email ID: ```text wrap theme={null} Edit this Brew email: [link or emailId]. Shorten the introduction to two sentences and keep the existing offer. Show the updated preview. Keep it as a draft; do not send or schedule. ``` Content edits use `edit_email` and also use credits. [Run Your Email Ops from an AI Agent](/recipes/run-brew-from-an-ai-agent) covers drafting, review, testing, and delivery in more detail. ## Give the Bot Working Instructions After setup, you can ask the Bot to remember how you want it to work: ```text wrap theme={null} Use Brew for [brand name]. Work through the Brew MCP connection. Use our saved brand style and facts I provide or approve. Create editable drafts and show the preview and Brew link. Ask before paid checks, contact imports, domain changes, or publishing automations. Send marketing email only to people who explicitly opted in. Before any send or schedule, show the audience, recipient count, sender, subject, timing and timezone, and final preview. Wait for my approval. A test email also needs my approval before it is sent. If a tool fails, report the error. Do not switch to browser operation or repeat a creation or send to work around it without asking. ``` These are instructions for your Bot. They don't change its Brew permissions. Some Brew tools have an additional confirmation step; [MCP Authentication and Scoping](/api-reference/mcp/authentication-and-scoping#confirmation) describes which ones. ## Review Before Sending Use the [pre-send review](/recipes/qa-before-a-big-send) before approving a delivery. Creating a draft doesn't send it. A test email is a separate send, and paid audits or inbox previews are separate checks. For a production send, select a sendable marketing domain and an opted-in audience. On an OAuth connection, `send_email` returns a confirmation request first. Grok Bot should show you the details and wait for your approval. See [Launch a Campaign](/api-reference/mcp/workflows#launch-a-campaign) for the complete tool sequence. After delivery, ask the Bot to read the send's status and analytics. An accepted send isn't proof that it reached the inbox. ## Troubleshooting | What you see | What to do | | - | - | | Brew isn't in the connector catalog | Ask the Bot to propose the remote server URL in the setup prompt. A catalog listing wasn't needed in the checked setup. | | The connection still asks for authorization | Use **Authorize** on the Brew card and finish browser sign-in. If it still fails, report the error and Grok Bot version before retrying. | | The browser asks to open Grok Bot | Open the app to return from sign-in, then continue the read-only verification. | | Connected, but no brand result | Ask for `get_brew_capabilities` and `get_brand` with `include: ["identity"]`. Report any tool error rather than assuming setup succeeded. | | The connection covers the wrong brand or all brands | Reconnect and choose the intended brand. An organization connection needs a `brand_id` on brand-scoped tools. | | The brand name is missing | Ask for `get_brand` with `include: ["identity"]`. The default read may show only the domain. | | The Bot asks for an API key | This guide uses browser OAuth. Stop and check why that flow failed before choosing a different authentication method. | | The workspace blocks adding a remote server | Ask your administrator whether `https://brew.new/api/mcp` is allowed. | ## Disconnect Brew Use **Manage** on the Brew connection card to inspect the installed connection. Revoke the matching authorization in Brew under **Settings → MCP**, in **Connected via OAuth**, when you want to end access. If you set up Grok Bot routines that use Brew, pause them before revoking the connection. See [Grok Bot's skills and routines guide](https://docs.x.ai/grok-bot/skills-routines-and-automations) for its scheduling controls. ## Related * [Connect Your MCP Client](/api-reference/mcp/connect-your-client): Grok web, Grok Build, and other clients * [MCP Workflows](/api-reference/mcp/workflows): sends, audiences, automations, and analytics * [MCP Tools](/api-reference/mcp/tools): tool descriptions and costs * [Use Brew with AI Agents](/integrations/ai-agents/use-brew-with-ai-agents): CLI, SDK, and API integration paths * [Grok Bot Setup](https://docs.x.ai/grok-bot/get-started): installation and account requirements ## 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: Type in the "Ask any question" search bar at the top left to instantly find relevant documentation pages. Click here to open the **Copy page** menu at the top of this page, then send the page to ChatGPT, Claude, or your editor. Book time with our founders for personalized guidance on strategy, best practices, or complex implementation questions. Need immediate assistance? Reach us at **+1-(332)-203-2145** for urgent issues or time-sensitive questions. Our preferred support channel. You'll receive an invite after signup for direct founder support and fast responses. Contact us at **[support@brew.new](mailto:support@brew.new)** for detailed inquiries or if you prefer not to use Slack. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.