Vercel MCP server
Last verified: 2026-09
Projects and deployments on Vercel.
Community Cloud & infra Needs a secret Claude Desktop, Cursor, Windsurf, Claude Code
What it does
Community Vercel MCP: list and inspect deployments and files, plus a create-deployment tool. Needs VERCEL_API_TOKEN.
It sits in Cloud & infra: Most of these are admin APIs.
Good for
- List deployments on a preview project.
- Inspect one deployment and its files.
- Leave vercel-create-deployment unused until you want the model to ship.
- Scope the token to one team/project.
Tools
- vercel-list-all-deployments / vercel-get-deployment / vercel-list-deployment-files — Read deploys.
- vercel-create-deployment — Write — ships a deploy.
Config (Claude Desktop / Cursor / Windsurf)
Paste the JSON below. Same mcpServers shape. Replace placeholder paths and secrets.
Windows paths look like C:\\Users\\you\\project, not /path/to.
Host-side steps →
Claude Desktop
| OS | Config file |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json
(usually C:\Users\<you>\AppData\Roaming\Claude\) |
| Linux | ~/.config/Claude/claude_desktop_config.json |
Cursor
| Scope | macOS / Linux | Windows |
|---|---|---|
| This project | .cursor/mcp.json in the repo root | |
| This user | ~/.cursor/mcp.json |
%USERPROFILE%\.cursor\mcp.json |
Windsurf
| OS | Config file |
|---|---|
| macOS / Linux | ~/.codeium/windsurf/mcp_config.json |
| Windows | %USERPROFILE%\.codeium\windsurf\mcp_config.json |
{
"mcpServers": {
"vercel": {
"command": "npx",
"args": [
"-y",
"vercel-mcp"
],
"env": {
"VERCEL_API_TOKEN": "..."
}
}
}
}
Windsurf remote MCP: use serverUrl instead of url if the block below is HTTP.
One-liner: npx -y vercel-mcp
Secrets it wants: VERCEL_API_TOKEN
How to get started
- Create a Vercel token scoped to one team/project.
- List deployments on a preview project first.
- Leave create-deployment unused until you want the model to ship.
Access risk
create-deployment is production if the project is. Tokens can also read env vars on some scopes.
When to skip it
Skip it for Netlify or Cloudflare Workers, or if git-push is your only deploy path.
Instead: Netlify, Cloudflare, GitHub.
Vs alternatives
| Server | Official? | Needs a secret? | Best for |
|---|---|---|---|
| Vercel | No | Yes | Projects and deployments on Vercel. |
| Netlify | No | Yes | Sites and deploys on Netlify. |
| Cloudflare | No | Yes | Workers, KV, R2, and DNS via Cloudflare. |
| GitHub | Yes | Yes | Repos, issues, PRs, and file contents on GitHub. |
More in Cloud & infra
FAQ
Can it read env vars?
Some token scopes can. Treat a Vercel token as the project, including secrets.
Community or Vercel official?
Community (nganiet/mcp-vercel). Confirm it still matches Vercel's current MCP docs.
Vercel or Netlify?
Match the host. create-deployment is production if the project is.
Git-push is enough — do I need this?
No. Skip it if git-push is your only deploy path.