Vercel
Connect Vercel to check deployments and build logs, ship and roll back sites, and manage projects, domains, DNS and environment variables.
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.
- Setup time
- 1 min
- Auth
- API credentials
- API base URL
- https://api.vercel.com
- Rate limits
- Limits are per endpoint and per team or user, for example 500 deployment reads a minute, 120 environment variable writes a minute and 100 deployments a day on Hobby (6,000 on Pro). Over a limit Vercel answers 429 with the time the limit resets.
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
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.
Tokens
Create and manage access tokens for the Vercel REST API and CLI.
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.
Tokens
Create and manage access tokens for the Vercel REST API and CLI.
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.
Tokens
Create and manage access tokens for the Vercel REST API and CLI.
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.
Connect in PopMCP
Open your workspace, choose Vercel in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Access tokensecret | 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.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Vercel immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
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..."
Why: 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..."
Why: 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
Why: 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
Why: 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.