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 over a remote MCP server. For ChatGPT web, which uses a separate plugin setup, see Connect Your MCP 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

This setup uses OAuth, so you don’t need an API key. Your workspace can restrict MCP servers. If you can’t add Brew, ask your administrator.

Add Brew in the Desktop App

1. 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 use that entry instead of adding a duplicate.

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

3. Sign in with Brew

   Select Authenticate on the Brew server. In your browser, sign in with Brew, choose your brand, and review the access request before approving it. Then return to the desktop app.

   Brew’s brew:all OAuth scope gives the app 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.

4. Check the connection in chat

   Open a chat on the host where you configured Brew. Type /mcp to inspect connected servers, then send the verification prompt 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:

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 the agent to list your brands and use the selected ID, or reconnect to one brand. See 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. Other machines or execution hosts need their own configuration and sign-in. ChatGPT web doesn’t read this local configuration.

To set up Brew from the terminal instead of the desktop form, run:

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 the configuration, then send the verification prompt.

To configure it by hand, add this table to ~/.codex/config.toml and keep the rest of the file:

[mcp_servers.brew]
url = "https://brew.new/api/mcp"

Use one configuration method. If the table already exists, review it instead of adding a second one. Then authenticate with codex mcp login brew.

OpenAI’s MCP guide covers shared configuration, project scope, and host-specific settings.

Use Brew After Setup

Follow Run Your Email Ops 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 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 instead of 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. For a CLI-managed entry, run codex mcp remove brew.

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: ChatGPT web and other clients
• MCP Tools: available operations and costs
• MCP Workflows: audiences, automations, and analytics
• QA an Email Before a Big Send: review before delivery
• Use Brew with Claude: the Claude walkthrough
• Use Brew with Cursor: the Cursor walkthrough
• Use Brew with 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:

Self-Service Tools

Search Documentation

Type in the “Ask any question” search bar at the top left to instantly find relevant documentation pages.

Ask ChatGPT or Claude

Click here to open the Copy page menu at the top of this page, then send the page to ChatGPT, Claude, or your editor.

Talk to Our Team

Schedule a Call

Book time with our founders for personalized guidance on strategy, best practices, or complex implementation questions.

Call Us Directly

Need immediate assistance? Reach us at [phone] for urgent issues or time-sensitive questions.

Slack Channel

Our preferred support channel. You’ll receive an invite after signup for direct founder support and fast responses.

Email Support

Contact us at [e-mail] for detailed inquiries or if you prefer not to use Slack.