Vercel

​

At a glance

• Availability: Experimental (how to enable).
• Authentication: API key.
• Connection: The key comes from VERCEL_TOKEN.
• Provider documentation: Authentication reference.

​

Credentials

Set these per environment. See Connect an integration.

​

Setup

1. Sign in to Vercel: Go to https://vercel.com and sign in (the free Hobby plan is sufficient for testing).
2. 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.
3. Set the environment variable: Add the token to your .env as VERCEL_TOKEN=…
4. Verify access: Run List Projects. For team resources, pass the team’s ID via the teamId parameter (find it in Team Settings).

​

Provider notes

• 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

Provider API reference.

​

Tools

​

Verify the connection

Call a read tool such as vercel__list_projects with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.