Use Brew with ChatGPT and Codex Desktop

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.

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

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.

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.

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.

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.

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.

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

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:

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:

[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 covers shared configuration, project scope, and host-specific settings.

Create Your First Draft

Generation uses Brew credits. After verification, replace the brackets and request one draft:

Use Brew for [brand name].
Create one product update email for our opted-in subscribers.
Use our saved brand style and only these approved facts: [facts].
Goal: [what readers should do].
Main link: [destination URL].
Keep it as an editable draft. Show the preview and Open in Brew link.
Do not import contacts, run paid checks, schedule, or send.

The agent uses create_email. If generation is still running, it should poll get_email with the returned emailId and runId. Repeating creation starts another billed design. Open the preview and Brew link. Check the facts, branding, images, and links. If the client doesn’t display a preview, inspect the design in Brew before approving further work. To revise it, identify the existing design:

Edit this Brew email: [Brew link or emailId].
Shorten the introduction and change the button to "Read the update".
Keep the approved facts and destination link.
Show the updated preview. Do not send or schedule.

Content edits use edit_email and also use credits. A rename, inbox subject change, or folder move alone uses the free update_email_metadata tool.

Review Before Sending

Give the agent your approval boundaries:

Use Brew for [brand name]. Show previews and Brew links for all drafts.
Send marketing email only to people who explicitly opted in.
Ask before paid checks, contact imports, domain changes, or publishing automations.

Before any send or schedule, show the audience, recipient count, sender,
subject, timing and timezone, and final preview. Wait for my approval.
Test emails also need my approval before sending.
Use one idempotency_key per intended send, including test sends.
Reuse it with unchanged send inputs for confirmation and retries.
Use a new key for a different intended send.
Report tool errors instead of repeating a creation or send blindly.

For production delivery, choose a sendable marketing domain and an opted-in audience. OAuth sends return a confirmation request first. After approval, the agent repeats the exact call with confirmed: true and its confirmation_id. Always include idempotency_key in send_email, including test sends. Reuse the same key and send inputs when confirming or retrying that send. Use a fresh key for a separate intended send. See Safe Retries for the full contract. Run Your Email Ops from an AI Agent covers the complete workflow. MCP Authentication and Scoping owns the confirmation rules. A test is a separate email send, and an accepted send isn’t proof of inbox delivery.

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.
The wrong brand is returned	Stop and reconnect with the intended brand before creating anything.
The brand name is missing	Ask for `get_brand` with `include: ["identity"]`; the default read may show only the domain.
A preview doesn’t display	Open the returned Brew link and inspect the design there. Don’t generate another email just to obtain a preview.
A tool call fails	Report the exact error and check the current tool guidance before retrying.

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.

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 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
Talk to Our Team

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.

Overview

Send Through Your ESP

Trigger Automations from Events

Forms and Surveys

Productivity and Data

AI Agents

Use Brew with ChatGPT and Codex Desktop

Requirements

Add Brew in the Desktop App

Verify Your Brand

Use the Same Connection from the CLI or IDE

Create Your First Draft

Review Before Sending

Troubleshooting

Disconnect Brew

Need Help?

Search Documentation

Ask ChatGPT or Claude

Schedule a Call

Call Us Directly

Slack Channel

Email Support

​Requirements

​Add Brew in the Desktop App

​Verify Your Brand

​Use the Same Connection from the CLI or IDE

​Create Your First Draft

​Review Before Sending

​Troubleshooting

​Disconnect Brew

​Related

​Need Help?

Search Documentation

Ask ChatGPT or Claude

Schedule a Call

Call Us Directly

Slack Channel

Email Support

Requirements

Add Brew in the Desktop App

Verify Your Brand

Use the Same Connection from the CLI or IDE

Create Your First Draft

Review Before Sending

Troubleshooting

Disconnect Brew

Related

Need Help?