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

> Connect Cursor to Brew with project or global MCP settings, sign in through your browser, and verify the brand before creating emails.

Connect Cursor to Brew to create branded emails and work with your email program alongside your code. Start with a read-only brand check, then ask for an editable draft.

## Requirements

* A Brew account with access to your brand
* Cursor with remote MCP connections available
* A browser to sign in with Brew and approve access

This setup uses OAuth, so no API key goes into your project. Your workspace can restrict MCP servers. If you can't add Brew, ask your administrator.

## Connect Brew

**1. Add the server**

Use [Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=brew\&config=eyJ1cmwiOiJodHRwczovL2JyZXcubmV3L2FwaS9tY3AifQ), or add the configuration below manually. If Brew is already configured, use that entry instead of adding a duplicate.

Choose one location:

| Scope | File |
| - | - |
| All your projects | `~/.cursor/mcp.json` |
| This project | `.cursor/mcp.json` in the project root |

Merge this entry into the file and keep any other servers:

```json mcp.json theme={null}
{
  "mcpServers": {
    "brew": {
      "url": "https://brew.new/api/mcp"
    }
  }
}
```

Keep the URL exactly as shown. OAuth doesn't need a fixed token or an API-key header.

**2. Sign in with Brew**

Open **Customize → MCP** and select Brew. Use its sign-in action if prompted. In your browser, sign in with Brew, choose your brand, and review the access request before approving it.

> [!NOTE]
>
> Older Cursor builds call this settings section **Tools & MCP**. [Cursor's MCP documentation](https://cursor.com/docs/mcp) covers current configuration locations and workspace controls.

> [!WARNING]
>
> Brew's `brew:all` OAuth scope gives Cursor 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 and verify it**

Confirm that Brew is enabled and its tools appear in **Customize**. Open a Cursor agent conversation and send the [verification prompt](#verify-your-brand) below.

A saved server entry 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 MCP server 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. Stop if the brand differs.

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 Cursor 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).

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

Cursor's tool approvals and Brew's send confirmation are separate controls. Review both when prompted.

## Troubleshooting

| What you see | What to do |
| - | - |
| Brew doesn't appear | Check the chosen `mcp.json` location and JSON syntax. Merge into the existing `mcpServers` object and enable Brew in **Customize**. |
| Brew appears but asks for authentication | Select its sign-in action and finish browser authorization. Saving the URL alone doesn't sign you in. |
| The workspace blocks Brew | Ask your administrator whether `https://brew.new/api/mcp` is allowed. |

## Disconnect Brew

Disable or remove Brew in Cursor's MCP settings. If you configured it manually, remove only its entry from the relevant `mcp.json` file.

Removing the 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): configuration reference and API-key alternatives
* [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): audiences, automations, and analytics
* [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 Claude](https://docs.brew.new/integrations/ai-agents/claude.md): the Claude 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.