> ## 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 by verifying your brand, then ask for an editable draft.

## Requirements

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

Your workspace can restrict MCP servers. Ask your administrator if Brew's server isn't allowed. This guide uses OAuth, so no API key needs to go into your project.

## Connect Brew

<Steps>
  <Step title="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 the existing entry.

    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, preserving other servers:

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

    Keep the URL exactly as shown. OAuth doesn't require a fixed token or an API-key header.
  </Step>

  <Step title="Sign in with Brew">
    Open **Customize → MCP** and select Brew. Use its sign-in action if prompted, then complete Brew authentication in your browser. Choose the brand you want Cursor to use 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.
    </Note>

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

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

  <Step title="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 below.

    A saved server entry alone doesn't verify authentication or a successful tool call.
  </Step>
</Steps>

## 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 with include: ["identity"].
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. Wait for brand extraction to finish before generating an email.

On a brand connection, tools act on that brand. An organization connection needs a `brand_id` for brand-scoped work. Ask Cursor to list brands and use the selected ID, or reconnect to one brand.

[Brand Scoping](/api-reference/mcp/authentication-and-scoping#brand-scoping) covers the full rules.

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

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.

Revoke the matching authorization in Brew under **Settings → MCP → Connected via OAuth** to end its access. Removing local configuration and revoking authorization are separate steps.

## Related

* [Connect Your MCP Client](/api-reference/mcp/connect-your-client): configuration reference and API-key alternatives
* [MCP Tools](/api-reference/mcp/tools): available operations and costs
* [MCP Workflows](/api-reference/mcp/workflows): audiences, automations, and analytics
* [QA an Email Before a Big Send](/recipes/qa-before-a-big-send): review before delivery
* [Use Brew with Claude](/integrations/ai-agents/claude): the Claude walkthrough
* [Use Brew with ChatGPT and Codex Desktop](/integrations/ai-agents/chatgpt-codex-desktop): the OpenAI desktop walkthrough
* [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.