> ## 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 an editable draft.

This guide covers **Claude Desktop and Claude web** through a custom connector. 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

**1. Add the Brew connector**

Open **Customize → Connectors → + Add → Add custom connector**. If Brew is already listed, use that entry instead of adding a duplicate.

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

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.

**2. Sign in with Brew**

Select **Connect** on the Brew connector. 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 Claude 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).

**3. Enable Brew in your conversation**

Return to Claude. Open the conversation's **+ → Connectors** menu and enable Brew. Send the [verification prompt](#verify-your-brand) below before asking Claude to create anything.

An enabled connector alone doesn't prove that sign-in or a tool call succeeded.

## 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.
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. If the brand is still extracting, wait until it's ready before generating an email.

An organization connection needs a `brand_id` for brand-scoped tools. Ask Claude to list your brands and use the selected ID, or reconnect to one brand. See [Brand Scoping](https://docs.brew.new/api-reference/mcp/authentication-and-scoping.md#brand-scoping).

## 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, complete browser sign-in, and choose your brand. Confirm that Brew is connected, then send the [verification prompt](#verify-your-brand).

Adding the server only saves configuration. Setup is done when sign-in and a tool call succeed. [Claude Code's MCP guide](https://code.claude.com/docs/en/mcp) covers client configuration and policy options.

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

## Watch the Walkthrough

[Connect Claude with MCP](https://docs.brew.new/brew-university/connect-claude-with-mcp.md) shows the connector, brand authorization, email creation, and a scheduled send. It was recorded before Brew MCP 3.0, and the video page explains the changed contact tools. Use this guide and the current [tool catalog](https://docs.brew.new/api-reference/mcp/tools.md) 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**. For Claude Code, run `claude mcp remove brew --scope user` if you added it with user scope.

Removing the connector or local configuration doesn't end Brew's access. Revoke the matching authorization in Brew under **Settings → MCP → Connected via OAuth**.

## Related

* [Connect Your MCP Client](https://docs.brew.new/api-reference/mcp/connect-your-client.md): other clients and the API-key alternative
* [MCP Tools](https://docs.brew.new/api-reference/mcp/tools.md): available operations and costs
* [MCP Authentication and Scoping](https://docs.brew.new/api-reference/mcp/authentication-and-scoping.md): access, confirmation, and revocation
* [QA an Email Before a Big Send](https://docs.brew.new/recipes/qa-before-a-big-send.md): review before delivery
* [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 Cursor](https://docs.brew.new/integrations/ai-agents/cursor.md): the Cursor walkthrough
* [Use Brew with Grok Bot](https://docs.brew.new/integrations/ai-agents/grok-bot.md): 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:

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