Every client connects to the same clean endpoint:
Authenticate with a brand-scoped API key — send it as Authorization: Bearer brew_…. Grab the connection URL and a key from Settings → API in Brew (the Connect AI agents panel copies both). The key carries the org + brand, so there’s nothing else to configure.
OAuth-based connection (for clients like Claude on the web and ChatGPT, whose connector UIs only accept a URL with no header field) is a planned follow-up. Today the server is API-key only — use the config-file clients below, or the Claude Desktop bridge.
Claude Code
Cursor
Claude Desktop
VS Code
Windsurf
Cline
Goose
Any client
Add the server
Run this in your terminal — replace the key with one from Settings → API:claude mcp add --transport http brew "https://brew.new/api/mcp" \
--header "Authorization: Bearer brew_YOUR_API_KEY"
Verify
Open a session and run /mcp — Brew should show connected with its tools.
Open your MCP config
~/.cursor/mcp.json (global) or .cursor/mcp.json (this project).
Add the server
{
"mcpServers": {
"brew": {
"url": "https://brew.new/api/mcp",
"headers": { "Authorization": "Bearer brew_YOUR_API_KEY" }
}
}
}
Confirm
Cursor picks it up automatically — check Settings → MCP for a green dot.
Edit the config
Claude Desktop’s connector UI has no header field, so an API key uses the 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.
Create .vscode/mcp.json
{
"servers": {
"brew": {
"type": "http",
"url": "https://brew.new/api/mcp",
"headers": { "Authorization": "Bearer ${input:brew-api-key}" }
}
},
"inputs": [
{
"type": "promptString",
"id": "brew-api-key",
"description": "Brew API Key",
"password": true
}
]
}
Start it
Click Start in the mcp.json gutter. VS Code prompts once for the key (stored securely); Brew appears in the agent-mode tools picker.
Requires GitHub Copilot agent mode.
Open the raw config
Settings → Cascade → MCP Servers → View raw config (~/.codeium/windsurf/mcp_config.json).
Add the server
Windsurf uses serverUrl (not url):{
"mcpServers": {
"brew": {
"serverUrl": "https://brew.new/api/mcp",
"headers": { "Authorization": "Bearer brew_YOUR_API_KEY" }
}
}
}
Refresh
Click Refresh in the MCP panel.
Open MCP settings
Cline → MCP Servers → Configure MCP Servers.
Add the server
{
"mcpServers": {
"brew": {
"url": "https://brew.new/api/mcp",
"headers": { "Authorization": "Bearer brew_YOUR_API_KEY" },
"disabled": false
}
}
}
Run the configurator
goose configure
# → Add Extension → Remote Extension (Streamable HTTP)
# name: brew
# endpoint: https://brew.new/api/mcp
# header: Authorization: Bearer brew_YOUR_API_KEY
Restart Goose after editing the config.
Most clients accept the canonical mcpServers block:{
"mcpServers": {
"brew": {
"url": "https://brew.new/api/mcp",
"headers": { "Authorization": "Bearer brew_YOUR_API_KEY" }
}
}
}
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:
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:
