Every client connects to the same clean endpoint:
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. The issued token is scoped to that brand and revocable anytime in Settings → API.
Wiring up a headless / CI setup, or a client with no OAuth UI? Send a brand-scoped key as
Authorization: Bearer brew_… instead — see
the API-key alternative below.
Claude Desktop
ChatGPT
Claude Code
Cursor
OpenCode
VS Code
OpenAI Codex
Manus
Windsurf
Cline
Goose
Any client
Add a custom connector
Open Settings → Connectors, click Add custom connector, and paste the connection URL: Connect
Click Connect, sign in with Brew, and pick a brand.
Works with Claude Desktop and claude.ai.
Add a custom connector
Open Settings → Connectors, click Add custom connector, and paste the connection URL: Connect
Connect, sign in with Brew, and pick a brand.
Custom connectors require a ChatGPT plan with connector support.
Add the server
Run this in your terminal:claude mcp add --transport http brew "https://brew.new/api/mcp"
Sign in
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"
}
}
}
Sign in
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
}
}
}
Sign in
OpenCode connects to the remote server; sign in with Brew when prompted.
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"
Sign in
Run codex and sign in with Brew when prompted.
Add a custom MCP server
Open Manus → Settings → MCP / Connectors and add a custom MCP server with the connection URL: Connect
Sign in with Brew and pick a brand.
Open the raw config
Settings → Cascade → MCP Servers → View raw config (~/.codeium/windsurf/mcp_config.json).
Add the brew server
Windsurf uses serverUrl (not url):{
"mcpServers": {
"brew": {
"serverUrl": "https://brew.new/api/mcp"
}
}
}
Refresh & sign in
Click Refresh in the MCP panel and sign in with Brew when prompted.
Remote servers use the serverUrl key (everyone else uses url).
Open MCP settings
Cline → MCP Servers → Configure MCP Servers.
Add the brew server
{
"mcpServers": {
"brew": {
"url": "https://brew.new/api/mcp",
"disabled": false
}
}
}
Sign in
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
Sign in
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"
}
}
}
Sign in
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 a brand-scoped API key instead. Create one at Settings → API and send it as a bearer header. The key carries the org + brand, so the URL stays the same:
{
"mcpServers": {
"brew": {
"url": "https://brew.new/api/mcp",
"headers": { "Authorization": "Bearer brew_YOUR_API_KEY" }
}
}
}
mcp-remote bridge — 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"}'
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:
