Vercel MCP server

Vercel × VS Code

Use the Vercel MCP server
in VS Code

Manage deployments, projects, and logs across your Vercel account. This guide connects Vercel to VS Code (GitHub Copilot's agent mode) through a governed gateway — one URL that also works in every other MCP client you use, with your rules and a full log attached.

Live-probed · Security-scanned · Note: Vercel currently restricts third-party sign-ins — API-key path recommended

Setup: Vercel in VS Code

VS Code adds MCP servers via MCP server configuration. The gateway route takes about two minutes:

  1. Connect Vercel to your free gate gateway from the verified directory.
  2. On your gate overview, click 'Add to VS Code' — VS Code prompts to add the gateway as an HTTP MCP server.
  3. Confirm and approve the sign-in.
  4. Copilot's agent mode can now use Vercel — logged and governed through your gateway.

What to ask once it’s connected

Why did the last deployment fail?
List the preview deployments for this pull request.
Summarize the function logs for errors since midnight.
Which projects are still on the old Node runtime?

Why route it through a gateway

One URL, every client

The same Vercel connection works in Claude, Claude Code, ChatGPT, Cursor too — no per-client re-wiring.

Rules before regret

Allow, ask, or block every tool Vercel exposes — reads can flow freely while writes require your approval.

Every call logged

A plain-language activity log of everything VS Code did with Vercel — searchable, exportable, auditable.

Scanned and probed

Vercel passed a live handshake probe and a security scan before listing — and drift detection watches it after you connect.

Also available: Vercel in Claude · Vercel in Claude Code · Vercel in ChatGPT · Vercel in Cursor