Guide · Vercel MCP Setup + Use Cases

Vercel MCP: Setup + Use Cases (2026)

Vercel MCP is Vercel’s official server for letting an AI client read your projects, deployments, logs and docs, so you stop copying build errors from the dashboard into a chat. It’s hosted at mcp.vercel.com, signs in with OAuth, and works with Claude, Cursor and VS Code.

One thing to sort out first. “Vercel MCP” can also mean hosting your own MCP server on Vercel’s platform, which is a build task covered in the deploy MCP servers docs. If you want your AI client to read your own Vercel account, you’re in the right place.

Quick answer
  • What it is: Vercel’s official MCP server at mcp.vercel.com. It lets Claude, Cursor, and VS Code read your projects, deployments, logs, and docs in plain language, and act on them.
  • Setup: one command for Claude Code (claude mcp add --transport http vercel https://mcp.vercel.com), or add the URL as a custom connector, then sign in with OAuth.
  • It is not read-only any more. It launched read-only, and since July 2026 it can deploy code. Its tools reference also lists tools that cancel deployments and edit environment variables, so keep confirmations on.
  • Best for: debugging failed builds, reading runtime logs, and searching Vercel docs without leaving your AI tool.

How to connect Vercel MCP to your AI client

The connection is the same underneath for every client: the hosted server at mcp.vercel.com, authenticated with OAuth, so no access token lands in a config file. Only the front door changes.

ClientHow to addAuth
Claude Codeclaude mcp add --transport http vercel https://mcp.vercel.comOAuth via /mcp
Claude Desktop / Claude.aiCustomize, then Connectors, then the + button, then Add custom connector, and paste the URLOAuth consent screen
CursorAdd to .cursor/mcp.json, or the one-click add button”Needs login” prompt, OAuth
VS Code (Copilot)The vercel mcp CLI configures it for youOAuth

Claude Code: Open a terminal in your project and run claude mcp add --transport http vercel https://mcp.vercel.com. Start Claude Code with claude, type /mcp, and finish the OAuth sign-in in the browser window it opens. Ask “list my Vercel projects” to confirm the tools loaded.

Claude Desktop: Go to Customize, then Connectors, then click the + button and choose Add custom connector. On a Team or Enterprise plan, an Owner adds it under Organization settings, then Connectors. Paste https://mcp.vercel.com, name it “Vercel,” and save. Claude sends you to Vercel to sign in and approve access. Then fully quit and reopen Claude Desktop. A window reload does not pick up a new connector, and that step is behind most “my server is not working” complaints.

Cursor and VS Code: In Cursor, add the server to .cursor/mcp.json with the same URL, then click the “Needs login” prompt to authorize. Vercel added official Cursor support after the initial launch. For any client, the simplest route is the vercel mcp CLI command, which runs an interactive picker, detects your installed clients, and wires each one up for the currently linked project.

Every connection ends at the same OAuth consent screen. Vercel keeps an allowlist of approved clients and shows that screen each time.

What does Vercel MCP do?

The Model Context Protocol is an open standard Anthropic released in late 2024. A server exposes tools, the client calls them mid-conversation, and the results flow straight back into the model’s reasoning. Vercel described its server, when it launched in public beta, as a secure, OAuth-compliant interface for AI clients to interact with your projects. The setup reference is in the Vercel MCP docs.

The tool set is broad and keeps growing:

  • Documentation search
  • Team and project listing, and project detail lookup
  • Deployment listing and build log retrieval
  • Runtime log retrieval, with filters for environment and log level
  • Web analytics queries
  • Temporary shareable access links for protected deployments
  • Vercel Toolbar comment thread management
  • Write tools for deployments and environment variables, including deploy_to_vercel, which Vercel added on July 23, 2026

The tools reference lists the current set. You don’t memorize it. You ask a question and the agent picks the tool.

What can you do with it once it’s connected?

Debug a failed deployment without opening the dashboard. “Why did my last deployment fail?” The agent lists recent deployments, finds the failed one, pulls its build logs, and reads the error back with a fix.

Read runtime logs to chase a live bug. Runtime logs include your console.log output and errors, filterable by environment, log level and time range. “Show me the errors from production in the last hour” gives you the relevant lines without building a log query by hand.

Search the docs mid-task. “How do I configure a custom domain, and does my current project already have one?” The agent searches Vercel’s documentation and reads your project metadata in the same answer.

Audit projects and domains. “List all my projects and tell me which ones have not deployed in 30 days,” or “is this domain available and what does it cost?”

“Pull the build logs for my last failed deployment on the marketing site and tell me what broke.”

That one prompt replaces four clicks, a scroll and a paste into a chat window. What is MCP covers the protocol if you want the background.

Where does Vercel MCP still need a human?

It can act, so you’re the safety. The server launched read-only and no longer is. It can deploy code, and its tools reference lists tools that cancel deployments and create and edit environment variables. Your Vercel permissions still apply, but inside them the agent can change real things. Keep human confirmation switched on in your client, read each tool call before approving it, and start with prompts that only read. Before you approve a deploy, check which project and which target, preview or production.

It reads what your account can read. The agent inherits your OAuth grant and can’t see a project or team you lack access to. If your projects are missing, you probably authorized the wrong scope. Redo the connection and pick the right team.

Big log pulls get token-heavy. Reasoning over thousands of log lines at once is slow and can hit context limits. “Production errors in the last hour” beats “show me all my logs.”

It answers, it doesn’t watch. MCP is request and response. It won’t ping you when a deployment fails or traffic spikes, which is what Vercel’s own alerting is for.

Too many servers slow things down. Each MCP server is a subprocess with startup and memory cost. Past ten you feel it, and three to six is the sweet spot. The best MCP servers for knowledge workers has more picks.

Keeping the fixes you’ve saved next to your deploys

Vercel MCP gives Claude your structured deployment data. It doesn’t give Claude the scattered fixes you collected along the way: the X thread on the Next.js caching bug you hit last month, the Reddit post with a build workaround in the comments, the LinkedIn post about edge function cold starts. The assistant can read the error but hasn’t seen the thread that solved it last time.

ContextBolt is a Chrome extension that saves any web page with its text and captures what you save on X, Reddit and LinkedIn, tagging each save by topic automatically. It exposes the whole collection through a personal MCP endpoint. Basic is free and capped at 150 bookmarks. Pro at $6 a month removes the cap, adds cloud sync, and adds the MCP endpoint any client can call.

Wire it in the way you wired Vercel: add the custom connector, paste your endpoint, restart. Then “My build failed with this error, and pull anything I have saved about Next.js caching” returns the build log and the threads you bookmarked about that problem. The walk-through for Claude Desktop is in ContextBolt in Claude Desktop, and the personal AI context stack covers feeding an agent your own context more broadly.

Where next

Frequently asked questions

Something else on your mind? Get in touch.

What is the Vercel MCP server?

It is Vercel's official connector that lets an AI client like Claude work with your projects, deployments, logs, and docs in plain language. Vercel hosts it at mcp.vercel.com, authenticated with OAuth. Any approved MCP client can call it once connected. It launched in public beta as a read-only server, and it can now act as well as read, including deploying code.

How do I connect Vercel MCP to Claude Code?

Run claude mcp add --transport http vercel https://mcp.vercel.com in your project. Then start Claude Code, type /mcp, and complete the OAuth sign-in. No config file to hand-edit and no API token to paste. The vercel mcp CLI command can also auto-detect and set up every client you have installed.

Is Vercel MCP read-only?

No, not any more. It launched read-only, but Vercel added a deploy_to_vercel tool on July 23, 2026, and its tools reference now lists tools that create and cancel deployments and create and edit environment variables. Your existing Vercel permissions still apply, so treat it as a server that can change things and keep human confirmation switched on in your client.

Does Vercel MCP work with Cursor and VS Code?

Yes. MCP is client-agnostic, so the same server works across clients. Vercel's list of supported clients includes Claude Code, Claude Desktop, Claude.ai, Cursor, and VS Code with Copilot, plus others such as ChatGPT and Codex CLI. You add the URL once per client, sign in with OAuth, and the tools appear. More on which tools support MCP.

What is the difference between using Vercel MCP and deploying an MCP server to Vercel?

Two different things people confuse. Using Vercel MCP means connecting an AI client to your Vercel account to inspect projects and logs. Deploying an MCP server to Vercel means hosting your own MCP server on Vercel's platform for others to call. This guide covers the first one.