# Vercel setup for PopMCP

You paste one value into PopMCP: an access token from the Tokens page of your Vercel account settings. If the token reaches several teams, you then choose which team the connection is for.

- Auth: API credentials
- Setup time: 1 min
- API base URL: https://api.vercel.com
- Credentials screen: https://vercel.com/account/tokens
- Provider docs: https://vercel.com/docs/rest-api

## Before you begin

- A Vercel account. Access tokens are free on every Vercel plan, including Hobby
- To change projects, deployments, environment variables or domains, a team role that allows it (Owner or Member can do almost everything)
- If your team requires SAML single sign-on or two-factor authentication, sign in that way before you create the token

## Get your credentials

### 1. Open the Tokens page of your account settings

Sign in at vercel.com. Open your Account Settings (from your avatar), then Tokens. You can also go straight to vercel.com/account/tokens.

Screen: https://vercel.com/account/tokens

### 2. Name the token, pick its scope and expiration

Enter a name that tells you what it is for, such as PopMCP. Open Scope and choose Full Account to be able to connect any of your teams, or pick one team and then All Projects. Choose an Expiration (a longer one means fewer reconnects) and click Create.

Screen: https://vercel.com/account/tokens

### 3. Copy the token

Vercel shows the new token once; new tokens start with vcp_. Copy it now: once you close the dialog you cannot see it again.

Screen: https://vercel.com/account/tokens

### 4. Paste the token into PopMCP and choose the team

In PopMCP, paste the token into Access token and connect. PopMCP checks it and lists the Vercel teams it can reach; choose the team this connection is for (each team goes into its own workspace). The connection is then locked to that team. A token limited to one project connects as that project's team and only reaches that project.

## Fields PopMCP asks for

- Access token (apiToken) [required]: In Vercel, open Account Settings, then Tokens. Enter a name, set Scope to Full Account (or one team), choose an expiration and select Create. Copy the token right away, it is shown only once. Stored encrypted and used only on our servers.

## Verify

PopMCP marks the Vercel connection Verified with your team's name and records your role, the team's plan, your email and when the token expires. Asking the AI for an overview of a project returns its production URL, recent deployments and domains.

## Troubleshooting

### "Vercel did not accept this access token..."

Cause: The token was copied incompletely, it expired on the date chosen when it was made, or it was deleted.

Fix: Create a new token on the **Tokens** page of your account settings and connect again.

### "This token cannot reach any of your Vercel teams..." or "cannot reach the Vercel team..."

Cause: The team requires SAML single sign-on or two-factor authentication and the token was made without it, or the token's scope is a different team.

Fix: Sign in to the team with SSO or two-factor authentication, then create a new token with **Scope** set to **Full Account** or that team.

### A tool answers that the connection is bound to a different team

Cause: The AI named another team than the one this connection was made for.

Fix: Ask about the connected team, or connect Vercel again and choose the other team for its own workspace.

### Webhook triggers stay quiet

Cause: Account webhooks are available on Vercel Pro and Enterprise teams only.

Fix: On a Hobby team, use the deployment triggers that check on a short cycle instead.

---

Source: https://www.docs.popmcp.com/docs/integrations/vercel/