Vercel MCP server

Vercel × Claude

Use the Vercel MCP server
in Claude

Manage deployments, projects, and logs across your Vercel account. This guide connects Vercel to Claude (claude.ai and the Claude desktop app) 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 Claude

Claude adds MCP servers via custom connectors in Settings. The gateway route takes about two minutes:

  1. Create a free gate gateway and connect Vercel to it from the verified directory (one click — note: Vercel currently restricts third-party sign-ins, so use the API-key path if the vendor offers one).
  2. Open claude.ai → Settings → Connectors and click 'Add custom connector'.
  3. Name it 'gate' and paste your gateway URL, then approve the authorization.
  4. Ask Claude something Vercel can answer — the call runs through your gateway, with your rules applied and logged.

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 Code, ChatGPT, Cursor, VS Code 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 Claude 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 Code · Vercel in ChatGPT · Vercel in Cursor · Vercel in VS Code