> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brew.new/llms.txt
> Use this file to discover all available pages before exploring further.

# Brew on Vercel Connect

> Apps and agents on Vercel reach Brew through Vercel Connect, with no Brew key in your environment variables. Connect with OAuth or an API key.

<Note>
  **October 2026**
</Note>

<Note>
  **Historical note · October 2026** · Describes Brew as of October 2026. For
  current behavior, see [Use Brew with Vercel Connect](/integrations/ai-agents/vercel-connect).
</Note>

## What Shipped

Calling Brew from an app on Vercel used to mean a Brew API key in your
environment variables. You copied it into every project and environment, and
changing it meant editing each one. An agent acting for a signed-in user
needed OAuth plumbing on top.

Now Vercel Connect holds the credential. Your deployed code asks it for a
short-lived token whenever it calls Brew. No Brew key or token lives in your
project.

## Two Ways to Connect

* **OAuth, for agents.** An AI agent in your app uses Brew's MCP tools on
  behalf of a signed-in user. Each user approves access once in Brew, for one
  brand, or for all of them if they're an organization admin.
* **API key, for your backend.** Your server calls the Brew API directly, for
  example to fire an automation trigger. The key lives only in Vercel Connect.

## Connect an Agent

<Steps>
  <Step title="Create the connector">
    In Vercel, open **Connect → Browse Connectors**, choose **Brew**, and pick
    **OAuth**. Or run `vercel connect create https://brew.new/api/mcp`. Vercel
    registers itself with Brew, so there's no client secret to copy.
  </Step>

  <Step title="Attach it to your project">
    Run `vercel connect attach brew` to let Production, Preview, and
    Development request tokens.
  </Step>

  <Step title="Hand Brew's tools to your agent">
    In an AI SDK route, `connectAuthProvider` from `@vercel/connect` fetches a
    current token on every MCP request. The first time, the user approves
    access in Brew, then the tools load.
  </Step>
</Steps>

Sends and other actions that reach real people still ask the user to approve
them first.

## Get Started

[Use Brew with Vercel Connect](/integrations/ai-agents/vercel-connect) walks
through both connections, with the full route code.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.