> ## 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 ChatGPT and Codex Desktop

> Connect ChatGPT or Codex desktop to Brew, authenticate in your browser, and verify your brand with desktop, CLI, and IDE setup options.

Connect your desktop app 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 **ChatGPT and Codex desktop** using a remote MCP server. ChatGPT web has a separate plugin setup in [Connect Your MCP Client](/api-reference/mcp/connect-your-client).

## Requirements

* A Brew account with access to your brand
* A desktop app with MCP server settings available
* A browser to sign in with Brew and approve access

Your workspace can restrict available servers. Ask your administrator if you can't add Brew. This setup uses OAuth, so you don't need to copy an API key.

## Add Brew in the Desktop App

<Steps>
  <Step title="Open MCP server settings">
    Open **Settings → MCP servers → Add server**. Some builds use **Settings → Plugins → MCPs → Add → Add MCP server**.

    If Brew is already listed, check its URL and authenticate that entry instead of adding a duplicate.
  </Step>

  <Step title="Enter the server details">
    Use these settings:

    | Setting | Value |
    | - | - |
    | Name | `brew` |
    | Transport | **Streamable HTTP** |
    | URL | `https://brew.new/api/mcp` |
    | Token and fixed headers | Leave empty for OAuth |

    Save the server and restart the connection when offered.
  </Step>

  <Step title="Authenticate with Brew">
    Select **Authenticate** on the Brew server. Sign in through your browser, choose your brand, and review the access request before approving it. Return to the desktop app afterward.

    <Warning>
      Brew's `brew:all` scope includes read and write access to your selection. Choose one brand unless you need access across your 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="Check the connection in chat">
    Open a chat on the host where you configured Brew. Type **/mcp** to inspect connected servers, then run the brand verification below.

    A saved server entry isn't proof that authentication or a tool call succeeded.
  </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 matches your selection. If extraction is still running, wait until the brand is ready before generating an email.

For an organization connection, brand-scoped tools need a `brand_id`. Ask the agent to list your brands and use the selected ID, or reconnect to one brand. See [Brand Scoping](/api-reference/mcp/authentication-and-scoping#brand-scoping).

## Use the Same Connection from the CLI or IDE

The desktop app, Codex CLI, and IDE extension share MCP configuration on the same Codex host. Different machines or execution hosts need their own configuration and authentication. ChatGPT web doesn't read this local configuration.

If you prefer terminal setup, add Brew with the CLI instead of the desktop form:

```bash theme={null}
codex mcp add brew --url https://brew.new/api/mcp
codex mcp login brew
```

Complete the browser sign-in and choose your brand. Run `codex mcp list` to inspect configuration, then verify the brand through an actual tool call.

For manual configuration, add this table to `~/.codex/config.toml` while preserving the rest of the file:

```toml theme={null}
[mcp_servers.brew]
url = "https://brew.new/api/mcp"
```

Use one configuration method. If the table already exists, review it rather than adding a second one. Authenticate with `codex mcp login brew` after configuring it.

[OpenAI's MCP guide](https://learn.chatgpt.com/docs/extend/mcp) covers shared configuration, project scope, and host-specific settings.

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

<span id="review-before-sending" 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.

## Troubleshooting

| What you see | What to do |
| - | - |
| No MCP server settings | Check your app version and workspace policy. ChatGPT web uses plugins rather than this desktop setup. |
| Brew is saved but needs authentication | Select **Authenticate**, or run `codex mcp login brew` on the same host. Complete browser sign-in. |
| Brew appears in the CLI but not the app | Check that both use the same host and configuration. Restart the server connection after changing its settings. |
| Brew works locally but not in a cloud chat | Verify the server's availability and authentication in that environment. Local setup doesn't establish cloud access. |

## Disconnect Brew

Remove Brew from the desktop app's MCP server settings when you no longer want it configured there. For a CLI-managed entry, use `codex mcp remove brew`.

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

## Related

* [Connect Your MCP Client](/api-reference/mcp/connect-your-client): ChatGPT web and other clients
* [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 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.