---
title: "Vercel MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/vercel/
description: "Search Vercel docs, inspect projects and runtime failures, and deploy a supplied file tree through the hosted endpoint."
---

# Vercel MCP: review, setup & limitations · Undominated.ai

> Search Vercel docs, inspect projects and runtime failures, and deploy a supplied file tree through the hosted endpoint.

[← Explore all mcp servers](/mcp-servers/)

CLOUD OPERATIONS / Vercel

# Vercel MCP

Search Vercel docs, inspect projects and runtime failures, and deploy a supplied file tree through the hosted endpoint.

 [See setup guidance ↓](#setup)[Original source ↗](https://vercel.com/docs/agent-resources/vercel-mcp)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 2 linked sources
 Publisher Vercel
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“Vercel MCP is Vercel's official MCP server. It's a remote MCP with OAuth that gives AI tools secure access to your Vercel projects”

 [Vercel · upstream description ↗](https://vercel.com/docs/agent-resources/vercel-mcp) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - First-party project, deployment and runtime-log tools connect application context with platform diagnostics.
- Direct file-tree deployment supports creating a preview without first configuring a Git repository.
- Vercel’s tools page says the MCP catalog lets an assistant work with projects, deployments, and related account resources, still gated by the OAuth grant and team permissions.
- The same page says a tool that is listed does not inherit the Vercel CLI’s access, and it names operations the server does not perform.

### A good fit for

 - Investigate a failed build or production runtime error.
- Create an explicitly approved preview deployment.
- Inspecting or managing Vercel projects and deployments from a client that has completed the team OAuth grant
- Checking whether a documented tool is actually available to this connection before relying on a CLI result

### Weigh up before choosing

 - The server is in beta and Vercel supports a reviewed set of compatible clients.
- deploy_to_vercel can target production; connecting the server is not limited to reading logs.
- Project logs and uploaded source may reach both Vercel and the connected AI client.
- A successful CLI request does not prove the MCP OAuth connection has the same access.
- The documented tool does not create AI Gateway API keys, exchange SSO tokens, import KMS private keys, or sign KMS messages or tokens.
- No licence was stated on these pages, and none was inferred.
- This review did not execute the resource.
- The server was not called.
- Only Vercel-reviewed clients are supported; a generic remote-MCP client is not automatically compatible.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - Current Vercel MCP setup page and per-tool reference, including deploy_to_vercel and log access.
- https://vercel.com/docs/agent-resources/vercel-mcp
- https://vercel.com/docs/agent-resources/vercel-mcp/tools
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### Our findings

 - The documented hosted endpoint uses OAuth and Streamable HTTP.
- The deployment tool accepts a file tree and a preview or production target. This differs from a local Vercel CLI configuration helper.
- Vercel MCP is documented with tools for docs search, teams, projects, deployments, and Web Analytics, and the setup page says it only operates within the Vercel account.
- Server configuration, the client’s OAuth grant, and team permissions affect access. A listed tool still needs that grant; a successful CLI call does not prove the MCP connection has the same access.
- The tools page says the referenced capability does not create AI Gateway API keys, exchange SSO tokens, import KMS private keys, or sign KMS messages or tokens.
- The available catalog depends on server configuration, OAuth grant and team permissions; the live tool list is the authoritative connection-specific surface.

### Not established by this review

 - Server launch, authenticated tool calls, and release-to-source parity were not tested.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://vercel.com/docs/agent-resources/vercel-mcp)

DOCUMENTED COMMAND

 codex mcp add vercel --url https://mcp.vercel.com Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - For Codex, add the official remote endpoint with the shown command. The page’s quick set-up, npx -y add-mcp https://mcp.vercel.com -g, configures every detected client instead.
- Finish OAuth in the client and grant access to the intended Vercel teams.
- The JSON example uses Cursor’s mcpServers format; follow the official guide for other clients and review production deployment and purchase requests.

### Before you start

 - A compatible client from Vercel’s documented list.
- Vercel account access for account/project tools.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "vercel": {
 "url": "https://mcp.vercel.com"
 }
 }
} Copy configuration ↗

### Compatibility

Codex · Claude Code · Claude.ai · Claude Desktop · ChatGPT · Cursor · VS Code · Windsurf · Gemini Code Assist · Gemini CLI · OpenCode

### Transports

Streamable HTTP

### Remote OAuth

 - Reads documentation, project/deployment metadata, logs and available analytics.
- Can submit files for preview or production deployment.

### Cost model

Vercel account, deployment usage and connected AI-client terms apply.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Vercel MCP setup and scope ↗](https://vercel.com/docs/agent-resources/vercel-mcp/tools) Checked 2026-10-14 https://vercel.com/docs/agent-resources/vercel-mcp/tools Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review
- [Vercel MCP endpoint, clients and beta terms ↗](https://vercel.com/docs/agent-resources/vercel-mcp) Checked 2026-10-14 https://vercel.com/docs/agent-resources/vercel-mcp Supports: install, compatibility, limitations, transports, access

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Fly.io flyctl MCP ↗ Manage Fly apps, Machines, volumes, secrets and operational status through the MCP server built into flyctl.](/mcp-servers/fly/)[### Netlify MCP ↗ Connect an agent to Netlify project, deployment and environment-variable operations through the hosted server.](/mcp-servers/netlify/)[### Render MCP ↗ Inspect Render services, logs and metrics, query Postgres, and perform supported deployment operations.](/mcp-servers/render/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
