Vercel MCP Server

How to install the Vercel MCP server

Add this to your Claude Desktop MCP configuration:

{
  "mcpServers": {
    "vercel": {
      "command": "npx",
      "args": [
        "-y",
        "vercel-mcp"
      ]
    }
  }
}

Add this to your Claude Code MCP configuration:

npx -y vercel-mcp

Add this to your Cursor MCP configuration:

{
  "mcpServers": {
    "vercel": {
      "command": "npx",
      "args": [
        "-y",
        "vercel-mcp"
      ]
    }
  }
}

The Vercel MCP server gives Claude full access to your Vercel projects. List deployments, manage environment variables, inspect build logs, trigger redeploys. For anyone using Vercel as their hosting, this is the missing link between Claude and your live infrastructure.

The community servers are the only option as of May 2026, but they’re solid. Pick the one that’s been updated most recently and has clear repo activity.

Why use it

Vercel’s dashboard is great for deep config work but most day-to-day ops are simple lookups: “is the latest deployment healthy?” “What’s the production env var for STRIPE_KEY?” “Did the redeploy from this morning succeed?” The MCP server turns these into prompts.

For solo founders running multiple Vercel projects, the install pays for itself the first time you ask “show me build errors across all my projects this week” and get an answer in five seconds.

What it actually does

Project ops: list, inspect, create. Deployment ops: list with filters (project, environment, state), fetch detail, fetch logs, redeploy. Environment variables: list, create, update, delete (scoped per project). Domain ops: list and inspect domains attached to a project.

Practical patterns:

“Show me all failed deployments across my projects this week.”
“Add SENTRY_DSN as a production env var to the api project.”
“Redeploy the contextbolt-landing project’s main branch.”

Gotchas

Token scope matters. A team-wide token can edit env vars across every project. For sensitive workflows, generate a project-scoped token if your Vercel plan supports it.

Build logs can be huge. Fetching the full log of a verbose build will fill Claude’s context fast. Most servers support tail and grep operations on logs; use them.

Pair with GitHub for an end-to-end deploy flow: open a PR, Vercel builds the preview, Claude inspects both the PR diff and the preview deployment, suggests changes if needed.

For the underlying app code, run Filesystem too. The combination (Filesystem + GitHub + Vercel) is the canonical stack for Claude-driven deployments on Next.js or Astro projects.

MCP servers related to Vercel

All in Cloud & Infra →

Vercel MCP server: FAQs

Is the Vercel server official?

Not yet. The community implementations wrap the Vercel REST API and cover most read and write operations. Vercel has hinted at first-party MCP support but hasn't shipped it as of May 2026.

What does it need to authenticate?

A Vercel access token from vercel.com/account/tokens. Scope it to a specific team if you want to avoid accidentally touching projects on your personal account.

Can it trigger deployments?

Yes. Most servers expose project list, deployment list and detail, env var read and write, and deployment trigger via the deploy hook URL. Some also support direct deployments via the Vercel CLI bridge.

Does it work with Vercel preview deployments?

Yes. You can list and inspect any deployment, including previews. This is useful for verifying that a PR's preview deployment is healthy without leaving the chat.

How is this different from running vercel CLI in Claude Code?

The CLI works fine when Claude is running shell commands. The MCP server returns structured JSON, which Claude reasons about more reliably. For complex queries (like 'compare env vars across these three projects'), the MCP server wins.

Back to all MCP servers

Vercel