What problem does it solve?
It solves the problem of deploying and managing Vercel projects when interactive login is unavailable or unreliable by ensuring every Vercel CLI command uses token-based authentication and the correct team/project scope.
Core Features & Use Cases
- Token-first CLI Authentication: Deploy and manage projects without running vercel login by using --token and/or VERCEL_TOKEN, plus optional org and project targeting.
- Team and Project Scoping: Use --scope for a team slug/ID and --project for a project name/ID to avoid accidental deployments to the wrong account.
- Environment Variable Management: Add, list, pull, and remove Vercel environment variables via vercel env commands using token-based scope.
- Use Case: A developer wants to create a preview deployment from a CI system or a shared machine where multiple Vercel accounts may be logged in, and needs deterministic targeting of the intended team and project.
Quick Start
Run a token-based preview deploy by telling the AI to execute vercel deploy with --token set from VERCEL_TOKEN, plus the correct --scope and --project values, defaulting to preview unless production is explicitly requested.