Skip to main content
Connect your Vercel account to enable CloudThinker agents to inventory projects, inspect deployments and build events, fetch runtime logs, audit domains and aliases, and run approval-gated controls like canceling stuck deployments or pausing projects. Vercel authenticates with an access token that CloudThinker passes to the official Vercel MCP server (@vercel/sdk). The token’s scope — personal account or a specific team — determines what the agent can reach. No OAuth flow is required.

​
Prerequisites

  • A Vercel account with access to the teams and projects you want to investigate.
  • An access token scoped to the right team.
  • Permission to create tokens for that scope.
Scope the token to only the team CloudThinker needs. The connection’s read operations never mutate Vercel resources — only the three approval-gated controls do.

​
Setup

1

Create an access token

In Vercel, go to Settings → Tokens → Create Token:
  • Name: cloudthinker
  • Scope: pick the team (or personal account) CloudThinker should access
  • Expiration: choose a lifetime and plan to rotate
Copy the token immediately — Vercel shows it only once.
2

Add the connection in CloudThinker

Navigate to Connections → Vercel and enter:
  • Token: the access token you just created
Click Connect. CloudThinker starts the Vercel MCP server and shows a Connected status.
Copy the access token immediately after creation. You’ll need to create a new token if it’s lost.

​
Connection details

FieldDescriptionExample
VERCEL_TOKENVercel access token used as the MCP bearer token—
CloudThinker resolves the team and projects from the token’s scope, so no manual team ID or URL configuration is required.

​
Required permissions

Scope the token to the team whose projects, deployments, domains, and logs CloudThinker should reach. Read operations work with any token that can see those resources; the three control operations additionally require the token’s scope to allow them and explicit approval in CloudThinker.
Follow least privilege: scope the token to a single team and set an expiration. Keep control operations approval-gated rather than removing the guardrail.

​
Agent capabilities

Once connected, agents have read access to your Vercel projects and deployments.
CapabilityDescription
Teams & ProjectsList teams and projects, and inspect project domains
DeploymentsList and inspect deployments, deployment events, and build output
Runtime LogsFetch runtime logs for error triage
Domains & AliasesAudit domains, domain configuration, and aliases
AccountRead the authenticated Vercel user
Deployment ControlCancel deployments, pause and unpause projects — requires approval
Cancel deployment, Pause project, and Unpause project are approval-gated. CloudThinker requests confirmation before running them; read-only operations run without approval.

​
Verify the connection

@alex check the Vercel connection and list accessible teams and projects

​
Example prompts

@alex list all projects across my Vercel teams with their framework and latest deployment status and #report as a table
@alex the latest production deployment failed — pull the build events, find the error, and #recommend a fix
@alex show runtime error logs for my Vercel project over the last 6 hours and #alert on 5xx spikes
For accounts with many projects, scope requests to a single team or project so the agent returns focused results.

​
Troubleshooting

The token is missing, expired, or revoked. Create a fresh Vercel token and reconnect the Vercel connection.
The token’s scope does not include those teams. Create a new token scoped to the correct team and reconnect.
Only one Vercel connection is allowed per workspace. Use the existing connection or remove it before reconnecting.
Cancel, pause, and unpause require both a token scope that permits the action and explicit approval in CloudThinker. Approve the action when prompted, and confirm the token’s scope allows it.

​
Security

  • Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
  • Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
  • Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
  • Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
  • Set token expiration — choose an expiration when creating the token and plan to rotate it; Vercel tokens do not auto-rotate.
  • Approval for controls — keep cancel, pause, and unpause actions approval-gated rather than removing the guardrail.
https://mintcdn.com/cloudthinker/aLd-ttc-SCW-aFky/images/icons/mcp.svg?fit=max&auto=format&n=aLd-ttc-SCW-aFky&q=85&s=c89b6087a9d233901dea5e354452eff6

MCP Connection

Connect custom tools and services with MCP

Approval

How approval-gated actions work