Vercel's CLI now installs a provider's agent skills alongside any Marketplace integration it provisions. Running vercel integration add neon (or vc i neon) provisions a Neon Postgres database on your Vercel project, wires up connection variables via vercel env pull, and pulls Neon's agent skills from skills.sh so a coding agent knows how to work with Postgres immediately. The post also covers billing options (Vercel-Managed vs Neon-Managed integrations), automatic Neon preview branches tied to Vercel Preview Deployments, branch cleanup behavior, and other integration subcommands like discover, categories, guide, and open.
Table of contents
Provision Neon from the Vercel CLIPreview branches, includedSkills now load automaticallyTell your agent to deploy NeonQuestions this post answers
How do I provision a Neon database on Vercel and give my coding agent instructions for using it in one step?
Run vercel integration add neon (or the alias vc i neon) from the Vercel CLI. This provisions a Neon Postgres database, connects it to the Vercel project by injecting variables like DATABASE_URL, pulls those variables locally via vercel env pull, and installs Neon's agent skills from skills.sh so the agent knows how to work with what was just provisioned. daily.dev helps developers wiring up AI agents with databases keep pace with tooling like this.
What happens to my Neon database branch when a Vercel Preview Deployment is created?
Neon automatically opens an isolated database branch matching the Preview Deployment when Preview is enabled on the connected project. The branch is an instant copy of the same Postgres schema and data, ready in about a second, starting as a pointer to existing storage so data only copies once the branch diverges from its parent, avoiding full-copy costs for short-lived environments. Teams comparing preview environment strategies track database branching patterns like this on daily.dev.
What is the difference between the Vercel-Managed and Neon-Managed integration paths for billing a Neon database?
The Vercel-Managed Integration creates a Neon account automatically if you don't have one and bills through your Vercel invoice, while the Neon-Managed Integration lets you keep an existing Neon account and billing directly with Neon. Branch cleanup timing also differs: Vercel-Managed follows Vercel's deployment retention policy, while Neon-Managed can follow Git branch deletion instead. daily.dev keeps developers weighing integration and billing tradeoffs like these up to date.