What problem does it solve? Deploying to Vercel from automated or agent-driven environments is difficult when interactive vercel login is unavailable, and passing tokens as CLI flags exposes secrets in shell history and process listings. ## Core Features & Use Cases - Token-Based Authentication: Locates VERCEL_TOKEN from the environment or .env files and exports it so the Vercel CLI reads it natively without --token flags. - Deployment Workflows: Supports quick deploys with VERCEL_PROJECT_ID/VERCEL_ORG_ID, full link-and-deploy flows with vercel link --repo, and git-push triggered deployments. - Project Management: Covers environment variable management, deployment inspection with logs, domain configuration, and Stripe Projects plan upgrades or downgrades. - Use Case: An AI agent in a CI-like environment needs to deploy a Next.js app to a Vercel team as a preview deployment using only a stored access token, without any interactive prompts. ## Quick Start Deploy my project to Vercel as a preview using the token in my environment.