Last Verified: September 2026 — commands checked against Vercel’s official MCP docs
A preview deploy fails, and Claude Code can’t see why. So you open the Vercel dashboard, find the deployment, scroll the build log, copy the error, and paste it back. Then you do the same for the runtime logs.
Vercel MCP is Vercel’s official hosted server (in public beta). It lets Claude Code list your projects and deployments, read build and runtime logs, group runtime errors, and fetch protected preview URLs. Setup is one command plus an OAuth sign-in, and you choose which teams it can see.
Errors come from Sentry instead? See our Sentry MCP setup.
How it works
Quick Start
Run this in your project folder:
claude mcp add --scope project --transport http vercel https://mcp.vercel.comStart Claude Code, run /mcp, pick vercel, and approve access in the browser. Total time: about 1 minute. No token to paste.
⚡ Copy This Prompt: Let Claude Code Install and Verify It For You
Skip the manual steps below and hand the whole job to the agent instead:
You have shell access and the `claude mcp` CLI on this machine. Connect Vercel's official MCP server to Claude Code for this project and report back. Do not tell me it's done unless step 4 actually confirms it:
1. Run `claude mcp list`. If a vercel entry already exists, show me its URL and stop instead of adding a second one.
2. Run:
`claude mcp add --scope project --transport http vercel https://mcp.vercel.com`
3. Tell me to run `/mcp` in Claude Code, pick vercel, and finish the Vercel sign-in in my browser, granting access only to the team this project belongs to. Wait until I say it's done, then run `claude mcp list` and confirm vercel shows Connected.
4. List the teams and projects you can see. For this project, show the 3 most recent deployments with their state, and if the latest one failed or has runtime errors, summarize the top error. Don't deploy, change env vars, domains, or settings, and don't buy anything.
Never ask me to paste a Vercel token into this chat. If any step fails, give me the exact error and the command that produced it. Do not skip ahead.The last step only reads, so you see what Claude can reach before it can change anything.
On this page (7 sections)
What You’ll Need
| Requirement | Why You Need It | Time |
|---|---|---|
| Claude Code installed | It’s on Vercel’s list of approved MCP clients | 0 min |
| A Vercel account with at least one project | The server acts as you, with your permissions | 0 min |
| A browser on the same machine | For the one-time OAuth sign-in and team selection | 0 min |
Step-by-Step Setup
Prefer to do it by hand instead of delegating to the agent? Here’s the manual version.
Step 1 — Add the server
~10 sec
--scope project writes the entry to .mcp.json in your repo, so teammates get the same server and each signs in as themselves. Use --scope user instead if you want it in every project:
claude mcp add --scope project --transport http vercel https://mcp.vercel.com
claude, approve it, then sign in with /mcp.Step 2 — Sign in and pick teams
~30 sec
Inside Claude Code, run /mcp, select vercel, and authenticate. Adding the server alone doesn’t authorize anything: on the consent page, grant access only to the team that owns the project you’re working on. Your existing Vercel role still applies.
Step 3 — Check what it can see
~20 sec
Ask Claude Code to list your teams and projects. If a team is missing, you either signed in with a different Vercel account or didn’t grant that team during sign-in. Run /mcp again to redo it.
What It Can Do
| Job | Example Ask | Changes Anything? |
|---|---|---|
| Debug a failed deploy | “Why did the latest preview deployment of web fail? Show the build error.” | No |
| Read runtime logs | “Show 500s from the api route in the last hour, grouped by error.” | No |
| Check a protected preview | “Fetch the preview URL for this branch and check the pricing page renders.” | No |
| Inspect config | “Which environment variables exist for production vs preview?” | No |
| Deploy, change settings, buy things | “Add the domain and redeploy” | Yes |
Verify It’s Actually Working
claude mcp list! vercel Needs authentication → run
/mcp and sign in (Step 2)✘ vercel Failed to connect → check the URL is exactly
https://mcp.vercel.com and the transport is http
Then ask for something only your account knows:
Find my project's latest deployment and check its runtime errors.If the deployment and errors match your Vercel dashboard, it’s working.
Common Mistakes to Avoid
- Assuming it’s read-only. It isn’t. The connection gets the same access as your Vercel user, and it can deploy code and even make purchases. Keep manual approval on for anything that changes state; a Claude Code hook can enforce it.
- Granting every team. If you’re in a work team and a personal one, grant only the team you need. Fewer teams also means fewer wrong-project guesses.
- Leaving out the team and project name. Vercel’s docs suggest naming both in your ask, so the agent finds the right resources on the first try.
- Using a lookalike URL from a marketplace. The only official endpoint is
https://mcp.vercel.com. Check the domain on any one-click install. - Pairing it with untrusted servers. A malicious page or tool could tell the agent to send your deployment logs somewhere else. Don’t run it next to a scraping server with approvals turned off.
Q&A
Is it free?
The MCP server comes with your Vercel account and is in public beta. Anything it does, like a deployment or a purchase, is billed the same as if you did it in the dashboard.
Can I use a Vercel access token instead of OAuth?
The hosted server at mcp.vercel.com uses OAuth, and only approved clients can connect. Claude Code is one of them, so OAuth through /mcp is the way to go.
Can I scope it to a single project?
Grant only the project’s team at sign-in and name the project in your asks. The Vercel CLI also has vercel mcp --project, which sets up project-specific access for the project linked in your folder.
Does it replace the Vercel CLI?
No. The CLI is still the fastest way to deploy from a script. The MCP server is for letting the agent look things up and investigate while you work.
Does it work in Claude Desktop or claude.ai too?
Yes, as a custom connector with the same URL on paid Claude plans. That connection is separate from the one in Claude Code.
Official Resources
- Vercel MCP docs — setup per client, security best practices
- Vercel MCP tools reference — every tool, by category
- Claude Code MCP docs —
claude mcp add, scopes, and OAuth with/mcp
If this guide got Claude Code reading your Vercel build logs instead of you copying them out of the dashboard, follow us on X for more setup guides and prompt tips.