Connect Your Client

Every client connects to the same clean endpoint:

https://brew.new/api/mcp

Brew is its own OAuth 2.1 connector, so the first-party flow needs no key to copy: add the URL, sign in with Brew, and pick a brand (or your whole organization). The issued token is scoped to that choice and revocable anytime in Settings → MCP. 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.

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:

Add a custom connector

Open Settings → Connectors, click Add custom connector, and paste the connection URL:

https://brew.new/api/mcp

Connect

Click Connect, sign in with Brew, and pick a brand.

Works with Claude Desktop and claude.ai.

Enable Developer mode

Open Settings → Security and login and enable Developer mode.

Create the Brew plugin

Open Settings → Plugins, select +, and create a plugin named Brew. Choose Server URL, paste the URL below, and select OAuth authentication:

https://brew.new/api/mcp

Approve brand access

Enable Brew in a new chat

Start a new chat and enable @Brew from the Plugins menu.

Verify the catalog

Ask Brew to call get_brew_capabilities. A successful response confirms that ChatGPT loaded the current action catalog.

If an older cached plugin reports an invalid action schema, refresh its actions first. Remove and re-add Brew only after the corrected endpoint is deployed and only if refresh does not work. Your existing OAuth grant remains valid.

Create a custom connector

Open grok.com/connectors, select New Connector → Custom, name it Brew, and paste:

https://brew.new/api/mcp

Authenticate

Start authentication, sign in with Brew, select a brand, review the full-brand access, and approve it.

Verify in a new chat

Start a new Grok chat, enable Brew, and ask it to call get_brew_capabilities.

Grok CLI: run grok mcp add --transport http brew https://brew.new/api/mcp, authenticate from /mcps if needed, then run grok mcp doctor brew.

Add the server

Run this in your terminal:

claude mcp add --transport http brew "https://brew.new/api/mcp"

Claude opens your browser to sign in with Brew and pick a brand.

Verify

Start a session and run /mcp to confirm Brew is connected.

Open your MCP config

~/.cursor/mcp.json (global) or .cursor/mcp.json (this project).

Add the brew server

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

Cursor opens your browser to sign in with Brew, then check Settings → MCP for a green dot.

Open your config

~/.config/opencode/opencode.json.

Add the brew server

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

Run opencode mcp auth brew, sign in with Brew, and pick a brand. Run opencode mcp list to confirm Brew is connected.

Create .vscode/mcp.json

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

Start & sign in

Click Start in the mcp.json gutter and sign in with Brew when prompted. Brew appears in the agent-mode tools picker.

Requires GitHub Copilot agent mode.

Add the brew server

Open ~/.codex/config.toml and add:

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

Run codex mcp login brew, sign in with Brew, and pick a brand. Start Codex and use /mcp to confirm Brew is connected.

Add a custom MCP server

Open Manus → Settings → MCP / Connectors and add a custom MCP server with the connection URL:

https://brew.new/api/mcp

Connect

Open the raw config

Settings → Cascade → MCP Servers → View raw config (~/.codeium/windsurf/mcp_config.json).

Add the brew server

Add Brew as a remote Streamable HTTP server. Current Windsurf builds accept serverUrl or url; this example uses serverUrl:

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

Refresh & sign in

Click Refresh in the MCP panel and sign in with Brew when prompted.

Windsurf limits the total enabled MCP tool count to 100. Brew currently exposes 72 tools.

Open MCP settings

Cline → MCP Servers → Configure MCP Servers.

Add the brew server

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

Save; Cline connects to the remote server and signs in with Brew.

Run the configurator

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

Name it brew, paste the connection URL, then sign in with Brew.

Restart Goose after editing the config.

Add the canonical block

Add Brew to your client’s mcpServers map with the bare URL:

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

Reload or restart the client, then sign in with Brew (OAuth) on first connect and pick your brand. If your client can’t do the OAuth handshake, add an Authorization: Bearer <brew key> header instead (see below).

Alternative: Connect with an API Key

If your client has no OAuth connector UI (or you’re wiring up a headless / CI setup) authenticate with an API key instead. Create one at Settings → API and send it as a bearer header. A brand key connects to its one brand. An organization key connects to the whole organization, and tools then take a brand_id. The URL stays the same either way:

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

Claude Desktop’s connector UI has no header field, so a key uses the mcp-remote bridge: open Settings → Developer → Edit Config, paste this, then fully quit and reopen Claude:

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

Write Authorization:Bearer … with no space after the colon (an mcp-remote arg quirk); it sends the correct header on the wire.

Verify Your Connection

Once connected, ask your agent to call get_brew_capabilities. It returns the tool catalog, credit costs, 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.

ChatGPT/Claude Integration

Click “Open in ChatGPT” at the top right of any page to explore it further with ChatGPT or Claude.

Overview

Core concepts

Guides

MCP server

CLI

Public API v1

Alternative: Connect with an API Key

Verify Your Connection

Need Help?

Search Documentation

ChatGPT/Claude Integration

Schedule a Call

Call Us Directly

Slack Channel

Email Support

​Alternative: Connect with an API Key

​Verify Your Connection

​Need Help?

Search Documentation

ChatGPT/Claude Integration

Schedule a Call

Call Us Directly

Slack Channel

Email Support

Alternative: Connect with an API Key

Verify Your Connection

Need Help?