Project + deployment + domain inspection. Read-only by design (no triggering deploys).
#Vercel
Project + deployment + domain inspection. Read-only by design (no triggering deploys).
This wrapper is read-only by design. No writes, no destructive operations.
#Get a token
Generate a Vercel Token at https://vercel.com/account/tokens.
#Recommended scopes
- Generate a token scoped to a single team if you want least-privilege per account.
- Set an expiration — Vercel allows 1 day, 1 week, 1 month, no expiry.
#Add it to the vault
bashmcpvault add vercel
Example session:
text$ mcpvault add vercel Label: work Description: Acme team on vercel.com Vercel Token: •••••••••••••••••••• Team slug (optional): acme ✓ Validated against api.vercel.com (team: acme, 12 projects) ✓ Saved.
#Tools exposed
vercel_list_projectsvercel_list_deploymentsvercel_get_deploymentvercel_list_domains
#Notes
- Vercel tokens grant write access to the team. mcpvault's wrapper exposes only read endpoints, but rotate the token if you suspect compromise.
#Switch to this account
In any chat client wired to mcpvault, ask:
Switch to my <label> Vercel account.
The vault server's activate_account tool flips the active label. Wrappers re-read it on the next call — no restart.