Full Supabase access: database, auth, storage, and edge functions.
- Home
- Top MCPs for Cloud & Infrastructure
- Vercel (MCP server)
Vercel (MCP server)
Inspect deployments, logs, and project state on Vercel from an AI agent.
Quick answer
What it does
Wraps the Vercel REST API for project, deployment, log, env var (metadata only), and domain operations. Read-only by default for sensitive surfaces.
Best for
- Deploy investigation
- Build-log debugging
- Env var audits
- Domain status checks
Not for
- Unattended deploys
- Workflows that need secret values in plaintext
Setup recipe
Pick your client, then follow the three steps.
- 1
Install
claude_desktop_config.jsonjson{ "mcpServers": { "vercel-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "VERCEL_TOKEN", "-e", "VERCEL_TEAM_ID", "vercel/mcp-server:latest" ], "env": { "VERCEL_TOKEN": "${VERCEL_TOKEN}", "VERCEL_TEAM_ID": "${VERCEL_TEAM_ID}" } } } }Paste under mcpServers. Fully quit and reopen Claude after editing.
CLI or .mcp.jsonshell# export VERCEL_TOKEN=changeme # export VERCEL_TEAM_ID=optional-team-scope claude mcp add vercel-mcp -- docker run --rm -i -e VERCEL_TOKEN -e VERCEL_TEAM_ID vercel/mcp-server:latestRun from your repo. Commit .mcp.json to share with your team.
.cursor/mcp.jsonjson{ "mcpServers": { "vercel-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "VERCEL_TOKEN", "-e", "VERCEL_TEAM_ID", "vercel/mcp-server:latest" ], "env": { "VERCEL_TOKEN": "${VERCEL_TOKEN}", "VERCEL_TEAM_ID": "${VERCEL_TEAM_ID}" } } } }Global path: ~/.cursor/mcp.json. Reload window after editing.
.vscode/mcp.jsonjsonc{ "servers": { "vercel-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "VERCEL_TOKEN", "-e", "VERCEL_TEAM_ID", "vercel/mcp-server:latest" ], "env": { "VERCEL_TOKEN": "${VERCEL_TOKEN}", "VERCEL_TEAM_ID": "${VERCEL_TEAM_ID}" } } } }VS Code uses the "servers" key (not "mcpServers").
~/.codeium/windsurf/mcp_config.jsonjson{ "mcpServers": { "vercel-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "VERCEL_TOKEN", "-e", "VERCEL_TEAM_ID", "vercel/mcp-server:latest" ], "env": { "VERCEL_TOKEN": "${VERCEL_TOKEN}", "VERCEL_TEAM_ID": "${VERCEL_TEAM_ID}" } } } }Open via Cascade → hammer icon → Configure.
cline_mcp_settings.jsonjson{ "mcpServers": { "vercel-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "VERCEL_TOKEN", "-e", "VERCEL_TEAM_ID", "vercel/mcp-server:latest" ], "env": { "VERCEL_TOKEN": "${VERCEL_TOKEN}", "VERCEL_TEAM_ID": "${VERCEL_TEAM_ID}" } } } }Open via the Cline sidebar → MCP Servers → Edit.
~/.continue/config.jsonjson{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "stdio", "command": "docker", "args": [ "run", "--rm", "-i", "-e", "VERCEL_TOKEN", "-e", "VERCEL_TEAM_ID", "vercel/mcp-server:latest" ], "env": { "VERCEL_TOKEN": "${VERCEL_TOKEN}", "VERCEL_TEAM_ID": "${VERCEL_TEAM_ID}" } } } ] } }Continue uses modelContextProtocolServers with a transport block.
~/.codex/config.tomlshell# ~/.codex/config.toml [mcp_servers.vercel-mcp] command = "docker" args = [ "run", "--rm", "-i", "-e", "VERCEL_TOKEN", "-e", "VERCEL_TEAM_ID", "vercel/mcp-server:latest", ] env = { VERCEL_TOKEN = "${VERCEL_TOKEN}", VERCEL_TEAM_ID = "${VERCEL_TEAM_ID}" }Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.
~/.config/zed/settings.jsonjsonc{ "context_servers": { "vercel-mcp": { "command": { "path": "docker", "args": [ "run", "--rm", "-i", "-e", "VERCEL_TOKEN", "-e", "VERCEL_TEAM_ID", "vercel/mcp-server:latest" ] }, "env": { "VERCEL_TOKEN": "${VERCEL_TOKEN}", "VERCEL_TEAM_ID": "${VERCEL_TEAM_ID}" } } } }Zed calls them "context_servers". Settings live-reload on save.
ChatGPT → Settings → Connectors (remote URL)json{ "name": "Vercel (MCP server)", "transport": "http", "url": "https://mcp.vercel.com" }Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled. ChatGPT supports remote HTTPS MCP servers only — stdio servers must be hosted on a public HTTPS endpoint first.
- 2
Set required secrets
Set
VERCEL_TOKEN,VERCEL_TEAM_IDin your shell environment before launching your MCP client. - 3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.
Tools & permissions
| Tool | Description | Args | Side effects |
|---|---|---|---|
list_projects | List Vercel projects in the configured team or account. | — | Read |
list_deployments | List recent deployments for a project. | project: string | Read |
get_build_logs | Fetch build logs for a deployment. | deployment_id: string | Read |
list_env_vars | List env var names and scopes for a project (values masked). | project: string | Read |
list_domains | List domains attached to a project. | project: string | Read |
Security & scope
- Access scope
- Read-only
- Sandbox
- Authenticates with a Vercel access token, ideally scoped to one team. Most tools are read-only; the redeploy tool can be disabled via VERCEL_DISABLE_WRITES=true for read-only stacks.
- Gotchas
- Tokens granted personal-account scope can see every project the human can see — scope by team.
- The MCP masks env var values, but build logs themselves can leak secrets if the application echoes them; sanitize on the build side.
- Redeploy tool can trigger a production deploy — leave VERCEL_DISABLE_WRITES=true unless you actively need it.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Recommend the best MCP servers for [task: e.g. cloud & infrastructure work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-cloud-infrastructure
Compare Vercel (MCP server) MCP vs [Cloudflare MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/vercel-mcp - top-mcps.com listing for Cloudflare
Install the Vercel (MCP server) MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/vercel-mcp (fetch https://top-mcps.com/mcp/vercel-mcp.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (VERCEL_TOKEN, VERCEL_TEAM_ID) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 2 updates tracked.Refreshed install snippets and fact sheet; verified for 2026.
Initial directory listing.
More Cloud & Infrastructure MCPs
Other tools in the same category worth evaluating.
Manage payments, customers, and subscriptions through Stripe.
Manage Workers, R2 buckets, DNS, and edge policies on Cloudflare.
Compared with Vercel (MCP server)
Side-by-side breakdowns for the choices people most often weigh against this MCP.
Exploring Top MCPs for Cloud & Infrastructure? See all Cloud & Infrastructure MCPs →

