Vercel

At a glance

Set these per environment. See Connect an integration.

Variable	Required	Description
`VERCEL_TOKEN`	Yes	Vercel access token (Account Settings > Tokens) Docs.

Sign in to Vercel: Go to https://vercel.com and sign in (the free Hobby plan is sufficient for testing).
Create an access token: Open Account Settings > Tokens (https://vercel.com/account/settings/tokens), create a token, choose its scope (personal account or a team), and copy it.
Set the environment variable: Add the token to your .env as VERCEL_TOKEN=…
Verify access: Run List Projects. For team resources, pass the team’s ID via the teamId parameter (find it in Team Settings).

Tokens are sent as ‘Authorization: Bearer <token>’
To access resources owned by a team, every call must include teamId (or slug) as a query parameter
Endpoint versions differ per route (v10 projects, v7 deployments list, v13 deployment detail) - this is normal for the Vercel API

Tool	Access	Description
List Projects	Read	List projects of the authenticated user or team
Get Project	Read	Get a project by ID or name
List Deployments	Read	List deployments under the authenticated user or team
Get Deployment	Read	Get a deployment by ID or hostname URL
List Environment Variables	Read	List the environment variables of a project (values stay encrypted unless decrypt is set)

List my most recent Vercel deployments with their state and target environment.
Find my Vercel deployments in ERROR state from the last day and tell me which projects are affected.