> ## 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 Claude

> Connect Claude Desktop, web, or Claude Code to Brew with browser sign-in, then verify your brand and troubleshoot the connection.

Connect Claude to Brew to create branded emails, work with your audiences, and read results from the same conversation. Start with a read-only brand check, then ask for one editable draft.

Use the custom connector steps for **Claude Desktop or Claude web**. If you work in a terminal, follow [Claude Code](#connect-claude-code) below.

## Requirements

* A Brew account with access to your brand
* A Claude account that can add custom connectors, or Claude Code installed for the terminal path
* A browser to sign in with Brew and approve access

Free Claude accounts are limited to one custom connector. Team and Enterprise members need their organization to add the connector first. See [Claude's connector setup](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) for current account requirements.

## Connect Claude Desktop or Web

<Steps>
  <Step title="Add the Brew connector">
    Open **Customize → Connectors → + Add → Add custom connector**. If Brew is already listed, use that connection instead.

    Name the connector **Brew** and enter:

    ```text theme={null}
    https://brew.new/api/mcp
    ```

    Select **Continue** and review the detected authentication settings. Choose **Sign in now** or **Sign in when needed**. If Claude offers an **OAuth client** choice, select **Register automatically** for Brew's automatic client registration.

    Finish adding the connector. This path uses browser sign-in, so leave fixed API-key headers empty.

    <Note>
      On Team or Enterprise, an authorized administrator adds Brew first: **Organization settings → Connectors → Add → Custom → Web**. Members then connect individually.
    </Note>
  </Step>

  <Step title="Sign in with Brew">
    Select **Connect** on the Brew connector. In the browser, sign in with Brew and choose the brand you want Claude to use. Review the requested access before approving it.

    <Warning>
      Brew's `brew:all` OAuth scope includes read and write access to your selection. Choose one brand unless you need the whole organization. A read-only prompt limits Claude's task, not its credential.

      [Review scopes and confirmation](/api-reference/mcp/authentication-and-scoping).
    </Warning>
  </Step>

  <Step title="Enable Brew in your conversation">
    Return to Claude. Open the conversation's **+ → Connectors** menu and enable Brew.

    Paste the verification prompt below before asking Claude to create anything.
  </Step>
</Steps>

## Verify Your Brand

Replace the brackets and send:

```text wrap theme={null}
Use the Brew connector for [brand name] ([website]).
Call get_brew_capabilities and report the connection scope.
Then call get_brand with include: ["identity"].
Confirm the brand name, website, and readiness from the results.
State which tools succeeded. If the brand differs, stop.

Keep this read-only. Do not create or edit anything, import contacts,
generate emails, spend Brew credits, schedule, or send.
Do not change domains or unsubscribe settings.
```

Check that the returned brand is yours. The connector being enabled doesn't establish that a tool call succeeded. If the brand is still being extracted, wait until it is ready before generating an email.

An organization connection requires a `brand_id` for brand-scoped tools. Ask Claude to list your brands and use the selected ID, or reconnect to one brand. [MCP Authentication and Scoping](/api-reference/mcp/authentication-and-scoping#brand-scoping) owns those rules.

## Connect Claude Code

Run this in your terminal:

```bash theme={null}
claude mcp add --transport http --scope user brew 'https://brew.new/api/mcp'
```

`--scope user` makes the server available across your projects. Omit it for the current project's local configuration.

Start Claude Code and open **/mcp**. Select Brew and complete browser authentication, choosing your brand. Confirm that Brew is connected, then run the [brand verification prompt](#verify-your-brand).

Adding the server URL saves configuration; authentication and a successful tool call complete the setup. See [Claude Code's MCP guide](https://code.claude.com/docs/en/mcp) for client configuration and policy options.

<span id="create-and-review-a-draft" style={{ scrollMarginTop: "8rem", display: "block" }} />

<span id="set-your-approval-boundaries" style={{ scrollMarginTop: "8rem", display: "block" }} />

## Use Brew After Setup

Follow [Run Your Email Ops from an AI Agent](/recipes/run-brew-from-an-ai-agent) to draft, edit, review, test, and send an email. It has the shared copyable prompts and troubleshooting steps.

Read the [approval and retry instructions](/recipes/run-brew-from-an-ai-agent#approval-and-retry-instructions) before delivery. They cover paid checks, test emails, send confirmation, and reuse of the same retry key.

## Watch the Walkthrough

[Connect Claude with MCP](/brew-university/connect-claude-with-mcp) shows the connector, brand authorization, email creation, and a scheduled send. It was recorded before Brew MCP 3.0; the video page explains the changed contact tools. Use this guide and the current [tool catalog](/api-reference/mcp/tools) for today's behavior.

## Troubleshooting

| What you see | What to do |
| - | - |
| No option to add a connector | Check your Claude plan and workspace permissions. A Team or Enterprise administrator may need to add Brew first. |
| Brew is listed but Claude can't use it | Select **Connect**, finish browser sign-in, then enable Brew through **+ → Connectors** in the conversation. |
| OAuth setup fails before Brew sign-in | Check the exact server URL. If an OAuth client setting is offered, use **Register automatically**. Report the error if it still fails. |
| Claude Code lists Brew but tools require authentication | Open **/mcp**, select Brew, and complete browser sign-in. Configuration alone isn't authentication. |

## Disconnect Brew

Remove the custom connector from **Customize → Connectors** when you no longer want it in Claude. Revoke the matching authorization in Brew under **Settings → MCP → Connected via OAuth** to end that grant.

For Claude Code configuration, use `claude mcp remove brew --scope user` if you added it with user scope. Revoke its Brew grant too.

## Related

* [Connect Your MCP Client](/api-reference/mcp/connect-your-client): other clients and the API-key alternative
* [MCP Tools](/api-reference/mcp/tools): available operations and costs
* [MCP Authentication and Scoping](/api-reference/mcp/authentication-and-scoping): access, confirmation, and revocation
* [QA an Email Before a Big Send](/recipes/qa-before-a-big-send): checks before delivery
* [Use Brew with Grok Bot](/integrations/ai-agents/grok-bot): the Grok Bot desktop walkthrough

## 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:

<Tabs>
  <Tab title="Self-Service Tools">
    <CardGroup cols="2">
      <Card title="Search Documentation" icon="magnifying-glass" color="#c44925">
        Type in the "Ask any question" search bar at the top left to instantly find relevant documentation pages.
      </Card>

      <Card title="Ask ChatGPT or Claude" icon="robot" color="#c44925" href="#top" className="ask-ai-card">
        Click here to open the **Copy page** menu at the top of this page, then send the page to ChatGPT, Claude, or your editor.
      </Card>
    </CardGroup>
  </Tab>

  <Tab title="Talk to Our Team">
    <CardGroup cols="2">
      <Card title="Schedule a Call" icon="calendar" color="#c44925" href="https://calendar.google.com/calendar/u/0/appointments/schedules/AcZssZ1iYoRUG1J792XQpbuQLjSRRDupr7MwraFK-HQRCtTYdBmrQi8nZu2qXfzKQigb8gbKJK3KN3-R">
        Book time with our founders for personalized guidance on strategy, best practices, or complex implementation questions.
      </Card>

      <Card title="Call Us Directly" icon="phone" color="#c44925">
        Need immediate assistance? Reach us at **+1-(332)-203-2145** for urgent issues or time-sensitive questions.
      </Card>

      <Card title="Slack Channel" icon="slack" color="#c44925">
        Our preferred support channel. You'll receive an invite after signup for direct founder support and fast responses.
      </Card>

      <Card title="Email Support" icon="envelope" color="#c44925" href="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.
      </Card>
    </CardGroup>
  </Tab>
</Tabs>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.