> ## 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 desktop to Brew from chat, approve browser sign-in, and verify your brand with a read-only check before creating emails. Connect Grok Bot to Brew to create branded emails and manage your email program from chat. Start with a read-only brand check, then ask for an editable draft. This guide covers **Grok Bot desktop**. For Grok web and Grok Build, see [Connect Your MCP Client](https://docs.brew.new/api-reference/mcp/connect-your-client.md). ## Requirements * A Brew account with access to your brand * Grok Bot desktop, signed in and allowed to add remote MCP connections * A browser to sign in with Brew and approve access This setup uses OAuth, so you don't need an API key. You need a verified sending domain only for a production send, not to connect or create a draft. ## Connect Brew **1. Ask Grok Bot to add 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. 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. **2. Sign in with Brew** Grok Bot displays a Brew connection card. Select **Authorize**. In your browser, sign in with Brew, choose your brand, and review the access request before approving it. > [!WARNING] > > Brew's `brew:all` OAuth scope gives Grok Bot read and write access to your selection. Choose one brand unless you need the whole organization. A read-only prompt limits the task, not the credential. > > [Review scopes and confirmation](https://docs.brew.new/api-reference/mcp/authentication-and-scoping.md). If the browser then asks **Open Grok Bot?**, open the app to finish the return from sign-in. **3. Verify the brand through Brew tools** 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`: the brand name, website, and readiness A **Connected** badge alone doesn't prove that a tool call succeeded. Check that the returned brand is yours. If the brand is still extracting, wait until it's ready before generating 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. Report the scope, brand name, website, and readiness. Keep this read-only. ``` > [!NOTE] > > Checked on October 19, 2026: Grok Bot added Brew from chat and completed browser authorization. It reported successful discovery and brand reads. > > That check didn't exercise draft creation, previews, or delivery. The next steps use Brew's documented MCP tools. Availability can vary by Grok Bot build and workspace policy. ## Use Brew After Setup Follow [Run Your Email Ops from an AI Agent](https://docs.brew.new/recipes/run-brew-from-an-ai-agent.md) to draft, edit, review, test, and send an email. It has the shared copyable prompts and troubleshooting steps. Read the [approval and retry instructions](https://docs.brew.new/recipes/run-brew-from-an-ai-agent.md#approval-and-retry-instructions) before delivery. They cover paid checks, test emails, send confirmation, and reuse of the same retry key. To reuse those working instructions, ask your Bot to save them as a named skill. Confirm the skill appears in your skill library before relying on it in later tasks. See [Save a skill](https://docs.x.ai/grok-bot/skills-routines-and-automations#save-a-skill). ## 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`. Report any tool error instead of assuming setup succeeded. | | 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. To end Brew's access, revoke the matching authorization in Brew under **Settings → MCP → Connected via OAuth**. If you set up Grok Bot routines that use Brew, pause them before revoking. [Grok Bot's skills and routines guide](https://docs.x.ai/grok-bot/skills-routines-and-automations) covers its scheduling controls. ## Related * [Connect Your MCP Client](https://docs.brew.new/api-reference/mcp/connect-your-client.md): Grok web, Grok Build, and other clients * [MCP Tools](https://docs.brew.new/api-reference/mcp/tools.md): available operations and costs * [MCP Workflows](https://docs.brew.new/api-reference/mcp/workflows.md): sends, audiences, automations, and analytics * [Use Brew with AI Agents](https://docs.brew.new/integrations/ai-agents/use-brew-with-ai-agents.md): CLI, SDK, and API integration paths * [Use Brew with ChatGPT and Codex Desktop](https://docs.brew.new/integrations/ai-agents/chatgpt-codex-desktop.md): the OpenAI desktop walkthrough * [Use Brew with Claude](https://docs.brew.new/integrations/ai-agents/claude.md): the Claude walkthrough * [Use Brew with Cursor](https://docs.brew.new/integrations/ai-agents/cursor.md): the Cursor walkthrough * [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: > [tab] Self-Service Tools > > > [card] Search Documentation > > > > Type in the "Ask any question" search bar at the top left to instantly find relevant documentation pages. > > > [card] [Ask ChatGPT or Claude](#top) > > > > Click here to open the **Copy page** menu at the top of this page, then send the page to ChatGPT, Claude, or your editor. > [tab] Talk to Our Team > > > [card] [Schedule a Call](https://cal.com/team/brewdotnew/brew-demo) > > > > Book time with our founders for personalized guidance on strategy, best practices, or complex implementation questions. > > > [card] Call Us Directly > > > > Need immediate assistance? Reach us at **+1-(332)-203-2145** for urgent issues or time-sensitive questions. > > > [card] Slack Channel > > > > Our preferred support channel. You'll receive an invite after signup for direct founder support and fast responses. > > > [card] [Email Support](mailto:support@brew.new) > > > > 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.