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

# Let AI Agents Deploy and Manage Vercel Projects

> Let agents check Vercel deployments, manage environment variables and domains, and ship new deploys with an access token the gateway keeps hidden.

## Overview

OneCLI connects AI agents to [Vercel](https://vercel.com) with an access token. Agents can check deployments, manage environment variables and domains, and start new deployments. The gateway injects the token into every request, so your agent never sees it.

Connecting takes about a minute.

## What you will set up

* A Vercel access token scoped to your account or one team
* Automatic token injection on every Vercel request
* Per-agent, per-tool access, with approval for production changes

## Connect Vercel

**1. Create an access token in Vercel**

Open [vercel.com/account/tokens](https://vercel.com/account/tokens) and click **Create**. Name it `OneCLI`, choose the **scope** (your personal account or a team), set an expiration, and click **Create Token**. Copy the token right away, Vercel only shows it once.

**2. Paste it in OneCLI**

In the OneCLI dashboard, open **Connections** > **Vercel**, paste the token into **Access Token**, and click **Connect Vercel**.

![OneCLI connect window for Vercel, showing the setup guide link, the Access Token field, and the Connect Vercel button.](https://mintcdn.com/chartdbinc/yFw2bbdvTPdZgMOT/images/integrations/vercel/onecli-connect-vercel.png?fit=max\&auto=format\&n=yFw2bbdvTPdZgMOT\&q=85\&s=7c90e7d415f97bfbdf5d5bb4ee47319e)

The Vercel connect window in OneCLI.

> [!NOTE]
>
> The token can reach everything its scope can reach. Scope it to one team when you can, and treat it like a password.

## What agents can do

| Area | What agents can do |
| - | - |
| **Projects** | List projects and read project details |
| **Deployments** | List and read deployments, create new deployments |
| **Environment variables** | List, create, update, and delete env vars |
| **Domains** | List, add, and remove domains |
| **Account** | Read the current user and list teams |

## Controlling access

[Grant](https://onecli.sh/docs/guides/agent-access.md) the connection to each agent that needs it, and choose per tool what runs freely, what needs approval, and what's blocked. **Create deployment**, env var changes, and domain changes affect production, so put them behind approval. Organization [rules](https://onecli.sh/docs/guides/rules.md) add guardrails on top. A blocked request never reaches Vercel.

To disconnect, remove the connection in **Connections** > **Vercel**, then delete the token at [vercel.com/account/tokens](https://vercel.com/account/tokens).

## FAQ

> [accordion] How do I rotate my Vercel token?
>
> Create a new token at [vercel.com/account/tokens](https://vercel.com/account/tokens), then paste it into **Connections** > **Vercel**. Agents pick it up automatically. Then delete the old token.

> [accordion] How do I keep the token out of the agent's context?
>
> Don't set `VERCEL_TOKEN` in the agent's environment. Store it in OneCLI, and the gateway injects it at the proxy. See [How it works](https://onecli.sh/docs/how-it-works.md).

> [accordion] Can I require approval before deploys or env var changes?
>
> Yes. Put **Create deployment**, env var, and domain changes behind approval when you [grant](https://onecli.sh/docs/guides/agent-access.md) the connection.


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