Full Supabase access: database, auth, storage, and edge functions.
supabase, database, backend, postgres
Vercel (MCP server)
Deploy from files or Git, buy and attach domains, edit DNS, and debug deployments on Vercel — the official remote MCP, over OAuth.
Quick answer
What it does
Wraps the Vercel REST API: deployments (`create_deployment` from `gitSource` or `files`, `upload_file`, `list_deployments`, `list_deployment_events`, `cancel_deployment`), projects (`create_project`, `create_git_project`, `add_project_domain`, `list_project_domains`), domains and DNS (`get_domain_availability`, `get_domain_price`, `list_supported_tlds`, `create_or_transfer_domain`, `update_record`, `replace_domains_by_domain_records`, certificates), billing (`get_purchase_quote`, `buy_domain`, `buy_credits`, `buy_pro`), logs, analytics, sandboxes, firewall, feature flags and more.
Best for
- Deploy investigation and build-log debugging
- Deployments from local files or a Git repository
- Custom domains on a project, with DNS records
- Domain registration with a quote-then-confirm gate
Not for
- Unattended production deploys
- Workflows that need secret values in plaintext
Source: top-mcps.com/mcp/vercel-mcp — verified Sep 2026
Setup recipe
Pick your client, then follow the three steps.
- 1
Install
claude_desktop_config.jsonjson{ "mcpServers": { "vercel-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.vercel.com" ] } } }Claude Desktop launches stdio servers, so mcp-remote bridges to the hosted endpoint and opens the sign-in in your browser. On Pro, Max, Team and Enterprise you can skip the file: Settings → Connectors → Add custom connector → https://mcp.vercel.com. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
CLI or .mcp.jsonshellclaude mcp add --transport http vercel-mcp https://mcp.vercel.comThen run /mcp inside Claude Code to finish the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
.cursor/mcp.jsonjson{ "mcpServers": { "vercel-mcp": { "url": "https://mcp.vercel.com" } } }Global path: ~/.cursor/mcp.json. Cursor shows "Needs login" once it connects — click it to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
.vscode/mcp.jsonjsonc{ "servers": { "vercel-mcp": { "type": "http", "url": "https://mcp.vercel.com" } } }VS Code uses the "servers" key. Run MCP: List Servers → Start Server and allow the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
~/.codeium/windsurf/mcp_config.jsonjson{ "mcpServers": { "vercel-mcp": { "serverUrl": "https://mcp.vercel.com" } } }Windsurf uses "serverUrl" for hosted servers. Open via Cascade → hammer icon → Configure. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
cline_mcp_settings.jsonjson{ "mcpServers": { "vercel-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.vercel.com" ] } } }Bridged through mcp-remote. Open via the Cline sidebar → MCP Servers → Edit. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
~/.continue/config.jsonjson{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "streamable-http", "url": "https://mcp.vercel.com" } } ] } }Continue takes the hosted URL directly in the transport block. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
CLIshellcodex mcp add vercel-mcp --url https://mcp.vercel.comCodex detects OAuth support and opens the browser to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
~/.config/zed/settings.jsonjsonc{ "context_servers": { "vercel-mcp": { "command": { "path": "npx", "args": [ "-y", "mcp-remote", "https://mcp.vercel.com" ] } } } }Bridged through mcp-remote under "context_servers". Settings live-reload on save. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
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.
- 2
Set required secrets
No credentials required — this MCP runs over stdio without authentication.
- 3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.
Tools & permissions
Showing 25 of 213 tools the server reported. The rest are real, just not listed here.
| Tool | Description | Args | Side effects |
|---|---|---|---|
list_teams | List the teams the connection was granted access to. | — | Read |
list_projects | List projects in a team, with repository and setting filters. | — | Read |
get_project | Return one project's configuration. | — | Read |
create_git_project | Create or reuse a project linked to a Git repository; deploys a preview by default. | — | Write |
add_project_domain | Add a domain to a project. | — | Write |
list_project_domains | List a project's domains, with verification and target filters. | — | Read |
create_deployment | Create a deployment from a Git source or from files; `target: "production"` ships to production, otherwise a preview. | — | Write |
upload_file | Upload a file for a deployment (base64 body, SHA1 digest). | — | Write |
list_deployments | List deployments, filterable by project, state, branch and rollback candidacy. | — | Read |
get_deployment | Return one deployment by ID or hostname. | — | Read |
list_deployment_events | Build output and deployment events, live with `follow`. | — | Read |
cancel_deployment | Cancel a deployment. | — | Write |
get_runtime_logs | Read and filter runtime logs for a project or deployment. | — | Read |
get_runtime_errors | Grouped runtime errors and the routes they affect. | — | Read |
get_domain_availability | Check whether a domain is available to register. | — | Read |
get_domain_price | Current registration price for a domain and term. | — | Read |
list_supported_tlds | TLDs Vercel can register. | — | Read |
get_purchase_quote | Read-only quote for a domain, credits, add-on or Pro; the only source of the idempotency key a `buy_*` call needs. | — | Read |
buy_domain | Register a domain with `confirm: true`, the quoted `expectedPrice`, the term and registrant contact. Charges the team's payment method; rejected if the live price moved. | — | Write |
get_domain_order | Status of an asynchronous domain registration order. | — | Read |
create_or_transfer_domain | Add a domain you already own to the Vercel platform. | — | Write |
update_record | Update one DNS record on a Vercel-managed domain. | — | Write |
replace_domains_by_domain_records | Replace a domain's DNS records from a BIND zone file — a full replace. | — | Write |
web_fetch_vercel_url | Fetch a Vercel-hosted URL, including protected deployments you can access. | — | Network |
import-claude-design-from-url | Import a self-contained HTML bundle from Claude Design and deploy it. | — | Write |
Security & scope
- Access scope
- Read + write
- Sandbox
- OAuth per client connection, with explicit consent per team; your existing Vercel permissions still apply. Purchases need a payment method on the team and a role with billing access.
- Gotchas
- Connecting grants the AI client the same access as your Vercel user across the teams you approve — approve one team, not all of them.
- `create_deployment` with `target: "production"` moves live traffic and `replace_domains_by_domain_records` replaces the whole zone. Keep both behind a confirmation.
- Every `buy_*` call needs a fresh `get_purchase_quote` (quotes expire after five minutes) and must echo the quoted price; charges are immediate and non-refundable.
- Env var values are masked, but build logs can still echo secrets the application prints.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. cloud & infrastructure work] in [client: Claude Code]. 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) against a real alternative. Swap the second MCP in [brackets] if you want a different match.
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
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Vercel (MCP server) MCP server for my [client: Claude Code] 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 (no secrets) 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
— 3 updates tracked.Entry re-verified against Vercel's tools reference (updated 2026-09-15): 213 tools in 28 categories, including deployments from files, domain purchase and DNS records. Earlier text described a read-only inspection server.
Deploys from files: Vercel creates the project, detects the framework, installs dependencies and builds; announced as deploy_to_vercel.
Purchases: Pro upgrades, prepaid credits, the SIEM add-on and domain registration through a quote-then-confirm flow.
More Cloud & Infrastructure MCPs
Other tools in the same category worth evaluating.
Official
Manage payments, customers, and subscriptions through Stripe.
stripe, payments, billing, invoicing
Official
Reach the whole Cloudflare API from an agent — DNS records, Workers, R2, and the Registrar beta — through one hosted Code Mode server.
cloudflare, edge, workers, dns
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 →