Connect Your MCP Client

Every client connects to the same clean endpoint:

https://brew.new/api/mcp

Brew supports OAuth 2.1 in compatible clients. Add the URL, authenticate, and pick one brand or your organization. Revoke the scoped token anytime in Settings → MCP. For clients that use API-key authentication, follow the alternative below. The brew:all scope gives the connected client full access to what you select. It can read and change emails, audiences, contacts, automations, sending setup, and analytics there. An organization connection reaches every brand you can access, so pick a single brand unless the client needs them all. See Brand scoping. To extract a new brand from a website, an organization administrator chooses All brands, then asks for the onboard_brand workflow. This works before the organization’s first brand exists. A brand connection can update its existing brand and sending domain with configure_brand. MCP Workflows covers the next steps.

Wiring up a headless / CI setup, or a client with no OAuth UI? Send an API key as Authorization: Bearer brew_… instead. See the API-key alternative below.

Pick your agent:

Custom connector

Configure

Open Customize → Connectors → + Add → Add custom connector.Name it Brew, enter the server URL below, and select Continue. Review the detected authentication settings and continue.

https://brew.new/api/mcp

Authenticate

Choose Sign in now or connect when needed. Finish adding the connector, select Connect, sign in with Brew, and choose one brand or all brands.

Verify

Enable Brew from the conversation’s + → Connectors menu. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

For Team or Enterprise, an owner or authorized admin first uses Organization settings → Connectors → Add → Custom → Web. Members then connect individually. Free accounts are limited to one custom connector.

API-key alternative

Configure

Use the same custom connector flow and server URL. Choose No sign in when using a fixed API key.

https://brew.new/api/mcp

Authenticate

Under Request headers, add Authorization with the value Bearer brew_YOUR_API_KEY, using a key from Brew’s Settings → API. Finish adding the connector.

Verify

Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

On Team or Enterprise, a fixed credential is shared by everyone using the connector. Choose a key limited to the access those members need.

Configure

On chatgpt.com, open Plugins → + → Add custom MCP server.Name it Brew. Under Connection, enter the server URL below and choose OAuth.Review the warning, select I understand and want to continue, then Create as a plugin.

https://brew.new/api/mcp

Authenticate

Install the plugin. Complete the OAuth sign-in with Brew, choose one brand or all brands, and approve the access when prompted.

Verify

In a new chat, type @ and select Brew. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Full MCP support on the web requires Business or Enterprise/Edu. Pro supports read/fetch access. Workspace permissions govern who can create custom MCP plugins; Business requires an admin or owner.

If tools changed after installation, refresh the plugin’s tools or actions using the controls your workspace provides. An administrator may need to review and publish the update.

Web connector

Configure

Open grok.com/connectors → New Connector → Custom and enter the server URL below.

https://brew.new/api/mcp

Authenticate

Start authentication, sign in with Brew, select a brand or all brands, and approve access.

Verify

Start a new chat; Grok can use connected tools when relevant. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

For Business or Enterprise, a team admin provisions the connector first.

Grok Build

Configure

Run the command below.

grok mcp add --transport http brew 'https://brew.new/api/mcp'

Authenticate

If authentication is needed, open /mcps, select Brew, and press i to sign in with Brew and select your brand.

Verify

Run grok mcp doctor brew, then start a session. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Configure

Run the command below with —scope user for every project, or omit it for this project’s local configuration. Adding the server only saves its configuration.

claude mcp add --transport http --scope user brew 'https://brew.new/api/mcp'

Authenticate

Run claude mcp login brew, or open /mcp in a Claude Code session and select Brew to authenticate. Sign in with Brew and choose a brand or all brands.

Verify

Run /mcp to confirm Brew is connected. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Configure

Use Add to Cursor below, or merge the configuration into ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project).Add to Cursor

mcp.json

{
  "mcpServers": {
    "brew": {
      "url": "https://brew.new/api/mcp"
    }
  }
}

Authenticate

Open Customize → MCP, select Brew, and use its sign-in action if prompted. Sign in with Brew and choose a brand or all brands.

Verify

Confirm Brew’s tools appear in Customize. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Older Cursor builds call this settings section Tools & MCP.

Configure

Merge this block into ~/.config/opencode/opencode.json.

opencode.json

{
  "mcp": {
    "brew": {
      "type": "remote",
      "url": "https://brew.new/api/mcp",
      "enabled": true
    }
  }
}

Authenticate

Run opencode mcp auth brew, sign in with Brew, and select a brand or all brands. OpenCode can also prompt on first use.

Verify

Run opencode mcp list to confirm Brew is connected. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Configure

Run MCP: Add Server from the Command Palette and choose HTTP, or create .vscode/mcp.json with the block below.For all workspaces, use MCP: Open User Configuration.

mcp.json

{
  "servers": {
    "brew": {
      "type": "http",
      "url": "https://brew.new/api/mcp"
    }
  }
}

Authenticate

Select Start above Brew’s entry in mcp.json. Complete the browser sign-in with Brew and select a brand or all brands.

Verify

In Chat, select Agent, then Configure Tools and enable Brew’s tools. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Requires GitHub Copilot. On Copilot Business or Enterprise, an administrator must allow MCP servers in Copilot.

ChatGPT desktop

Configure

Open Settings → Plugins → MCPs → Add → Add MCP server. Some builds use Settings → MCP servers → Add server.Name it brew, select Streamable HTTP, and enter the URL below. Leave token and header fields empty for OAuth, then Save. Restart the connection if offered.

https://brew.new/api/mcp

Authenticate

Select Authenticate on the Brew server, sign in with Brew, and choose a brand or all brands.

Verify

Type /mcp to inspect connected servers. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Codex CLI or IDE configuration

Configure

Merge this block into ~/.codex/config.toml. The desktop app, CLI and IDE extension share it on the same Codex host.

config.toml

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

Authenticate

Run codex mcp login brew, sign in with Brew, and select a brand or all brands. The desktop and IDE server lists also offer Authenticate.

Verify

Run codex mcp list or /mcp in a session. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Windows and WSL can use different hosts and home directories. ChatGPT web does not read this file. For an API key, set bearer_token_env_var to the name of an environment variable containing your Brew key.

Configure

Open Connectors → Create → Add MCP by URL. Name the server Brew and enter the URL below. Older builds use Settings → Integrations → Custom MCP Servers → Add Server.

https://brew.new/api/mcp

Authenticate

Create a key in Brew’s Settings → API. Use the key in Manus’s bearer-token field, or set Authorization to Bearer brew_YOUR_API_KEY. Save and test the connection.

Verify

Confirm Brew’s tools are available. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Use API-key authentication for custom servers. Brew OAuth in Manus’s custom-server flow still needs a live compatibility check.

Configure

Merge this block into ~/.config/devin/mcp_config.json on macOS/Linux, or %APPDATA%\devin\mcp_config.json on Windows. For private project settings, use .devin/mcp_config.local.json.

mcp_config.json

{
  "mcpServers": {
    "brew": {
      "url": "https://brew.new/api/mcp"
    }
  }
}

Authenticate

Run devin mcp login brew in Devin CLI, or use the authentication action when Devin Local first uses Brew. Sign in with Brew and select a brand or all brands.

Verify

Run devin mcp list or inspect the session’s MCP servers. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Current Devin Desktop uses Devin Local. Upgrade legacy Windsurf builds before following these steps. Organization policy may restrict available servers.

Remote Servers

Configure

Click the MCP Servers icon and open Remote Servers.Enter Server Name brew and the Server URL below. Choose Streamable HTTP, then Add Server.

https://brew.new/api/mcp

Authenticate

Click Authenticate on the Brew server row. Complete the browser sign-in with Brew and select a brand or all brands.

Verify

Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

JSON alternative

Configure

Open MCP Servers → Configure → Configure MCP Servers and merge the block below into the settings file. Save it.

cline_mcp_settings.json

{
  "mcpServers": {
    "brew": {
      "type": "streamableHttp",
      "url": "https://brew.new/api/mcp",
      "disabled": false
    }
  }
}

Authenticate

Click Authenticate on Brew’s server row, sign in with Brew, and select a brand or all brands.

Verify

Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

The type field is required here: omitting it selects legacy SSE in Cline.

Configure

Run goose configure. Choose Add Extension → Remote Extension (Streamable HTTP), name it brew, and enter the endpoint below.

goose configure
# Add Extension → Remote Extension (Streamable HTTP)
# name: brew
# endpoint: https://brew.new/api/mcp

Authenticate

Complete the OAuth sign-in when Goose requests it. Sign in with Brew and select a brand or all brands.

Verify

Start a session with the Brew extension enabled. Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

Goose Desktop: open Extensions → Add custom extension, choose Streamable HTTP, and enter the same endpoint.

Configure

Use your client’s documented remote-server format. The example below is for clients that accept mcpServers with type http. Merge it into your existing config.

mcp.json

{
  "mcpServers": {
    "brew": {
      "type": "http",
      "url": "https://brew.new/api/mcp"
    }
  }
}

Authenticate

Run the client’s sign-in or authenticate action, then sign in with Brew and choose a brand or all brands. For clients without OAuth, use an API-key bearer header in their supported format.

Verify

Call get_brew_capabilities to confirm the connection and inspect its brand or organization scope.

This example is for clients that accept mcpServers and type: http. VS Code uses servers, OpenCode uses mcp and type: remote, and Cline requires type: streamableHttp. Follow your client’s recipe.

Alternative: Connect with an API Key

Create a key in Settings → API. A brand key covers one brand. An organization key covers your organization; pass a brand_id for brand-scoped tools. For clients using the HTTP JSON format, add a bearer header:

{
  "mcpServers": {
    "brew": {
      "type": "http",
      "url": "https://brew.new/api/mcp",
      "headers": {
        "Authorization": "Bearer brew_YOUR_API_KEY"
      }
    }
  }
}

Use your client’s own wrapper and transport name. Cline requires streamableHttp; VS Code uses servers; OpenCode uses mcp and remote. Claude’s custom connector supports Request headers. Set Authorization to Bearer brew_YOUR_API_KEY and choose No sign in for fixed credentials. On Team or Enterprise, everyone using that connector shares its credential’s access. In ChatGPT desktop or Codex, set bearer_token_env_var to an environment variable name such as BREW_API_KEY. Put the key in that environment variable before launching the client.

Optional Compatibility Bridge

For a client that only supports local stdio servers, use mcp-remote. Install Node.js so npx is available on the client host. Use your client’s local-server wrapper. This example uses mcpServers:

claude_desktop_config.json

{
  "mcpServers": {
    "brew": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://brew.new/api/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer brew_YOUR_API_KEY"
      }
    }
  }
}

The full header value stays in AUTH_HEADER. The argument contains no spaces, which avoids argument-splitting problems in some clients. Restart the local client after changing its process configuration. mcp-remote configuration

Verify Your Connection

Once connected, ask your agent to call get_brew_capabilities. It returns the connection’s scope, the tool catalog, and the guided workflows. Or smoke-test the endpoint directly with a key:

curl -sN https://brew.new/api/mcp \
  -H "Authorization: Bearer brew_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Next: the quickstart create → send → analyze loop, the full tool catalog, and the guided workflows.

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.

Start Here

Public API v1

API Contracts

API Guides

MCP Server

CLI

SDKs

Alternative: Connect with an API Key

Optional Compatibility Bridge

Verify Your Connection

Need Help?

Search Documentation

Ask ChatGPT or Claude

Schedule a Call

Call Us Directly

Slack Channel

Email Support

​Alternative: Connect with an API Key

​Optional Compatibility Bridge

​Verify Your Connection

​Need Help?

Search Documentation

Ask ChatGPT or Claude

Schedule a Call

Call Us Directly

Slack Channel

Email Support

Alternative: Connect with an API Key

Optional Compatibility Bridge

Verify Your Connection

Need Help?