vercel

Deploy, inspect, and troubleshoot Vercel applications using CLI commands and MCP tools.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Domush/ai-agent-web-development-skills --skill vercel-domush
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vercel
Source: https://github.com/Domush/ai-agent-web-development-skills/tree/main/skills/vercel
Command: npx skills add https://github.com/Domush/ai-agent-web-development-skills --skill vercel-domush

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying and operating applications on Vercel involves many moving parts—project linking, environment variables, build logs, protected previews, and rollbacks—and mistakes like deploying the wrong project or misconfiguring CI are common. This Skill provides a task-first operational guide so agents and developers can reach a verified deployment quickly and diagnose failures with evidence. ## Core Features & Use Cases - Deployment Workflows: Step-by-step flows for first-time setup, monorepo linking, CI prebuilt production deploys, and failed-deployment diagnosis. - CLI and MCP Tooling: A command map covering deploy, inspect, logs, env vars, domains, promote, and rollback, plus MCP tool equivalents for isolated agent contexts without terminal access. - Troubleshooting Matrix: Symptom-to-action tables for auth failures, protected preview 403s, build/runtime mismatches, and CI hangs, with explicit anti-patterns to avoid. - Use Case: Your CI pipeline deploys a broken build to production. Use this Skill to inspect build and runtime logs, identify the env mismatch, then promote a known-good deployment or roll back with explicit commands. ## Quick Start Use the vercel skill to deploy my app to production and verify the deployment health endpoint.

Frequently Asked Questions about vercel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy to Vercel production from the CLI?▼

Run vercel --prod to deploy directly to production, or use vercel build --prod followed by vercel deploy --prebuilt --prod for CI pipelines that build once and deploy the artifact. Always verify the linked team and project first with vercel whoami and vercel link.

How do I link a monorepo project on Vercel?▼

Use vercel link --repo to link a monorepo, then run vercel pull to fetch project config and environment values. If the target app is not the repo root, change into that app directory before running vercel or vercel --prod.

When should I use Vercel MCP tools instead of the CLI?▼

Use MCP tools when terminal access is unavailable or you need structured JSON responses for automation, such as listing deployments or fetching build logs. Use the CLI for local build parity, CI shell scripts, and direct command execution.

Why does my Vercel preview URL return a 403 forbidden error?▼

Deployment protection is enabled on the preview environment. Use vercel curl with the deployment URL or the MCP authenticated fetch tools to access protected routes instead of disabling protection.

How do I roll back a bad Vercel production deployment?▼

Run vercel rollback with the deployment URL for immediate recovery, or vercel promote with a known-good deployment URL. Confirm recovery afterward by checking runtime logs and hitting a health endpoint.

Why does my Vercel build succeed locally but fail in the cloud?▼

This usually indicates an environment variable mismatch or differing build context. Compare env vars with vercel env ls, inspect the cloud build logs, and verify the project root and output settings match your local setup.