Vercel MCP server for Claude, Codex and Cursor

What your AI apps can do with Vercel

Find projects and deployments
Read deployment and build logs

Vercel MCP tools

28 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does
`search_vercel_documentation`	Searches Vercel documentation
`list_teams`	Lists the teams you can access
`list_projects`	Lists projects or reads one project's configuration
`get_project`	Lists projects or reads one project's configuration
`list_deployments`	Lists deployments or reads one
`get_deployment`	Lists deployments or reads one
`get_deployment_build_logs`	Reads build logs for a failed build
`get_runtime_logs`	Reads runtime logs for a project or deployment
`get_runtime_errors`	Reads grouped runtime errors and affected routes
`web_fetch_vercel_url`	Fetches a deployment URL, including protected deployments you can access
`get_web_analytics`	Queries visitors, page views and custom events
`filter_project_envs`	Lists a project's environment variables
`get_project_env`	Returns the decrypted value of an environment variable
`create_project_env`	Creates or edits environment variables
`edit_project_env`	Creates or edits environment variables
`create_deployment`	Creates a preview or production deployment
`deploy_to_vercel`	Deploys a small project from inline files
`cancel_deployment`	Cancels a deployment
`request_promote`	Points production traffic to a given deployment
`request_rollback`	Points production traffic to a previous deployment
`get_access_to_vercel_url`	Creates a temporary shareable link that bypasses deployment protection
`update_project`	Updates project settings
`update_project_deployment_protection`	Changes password protection, Vercel Authentication and trusted IPs
`pause_project`	Pauses a project
`update_firewall_config`	Changes firewall configuration
`put_firewall_config`	Changes firewall configuration
`replace_domain_dns_records`	Replaces a domain's DNS records
`buy_domain`	Registers (buys) a domain for a team

Suggested starting access

Toolstile read each Vercel tool's description and wrote these starting selections by hand. They are a suggestion reviewed by Toolstile, not a guarantee: Vercel decides what each tool does and can change it, so check that a selection fits each app before you save it.

Inspect deployments and logs

Read teams, projects and deployments, and search the docs. Build logs, runtime logs and errors, which can contain logged values, and fetching a protected deployment URL wait for approval.

Allow: search_vercel_documentation, list_teams, list_projects, get_project, list_deployments, get_deployment
Require approval: web_fetch_vercel_url, get_deployment_build_logs, get_runtime_logs, get_runtime_errors

In the access editor, choosing a suggestion adds the listed tools this server offers to your draft. Existing access stays as it is, blocks and approval requirements stay in force, and the suggestion doesn't grant tool names the server adds later. Nothing is saved until you choose Save changes.

Suggested access for each AI app

The documentation this list comes from doesn't mark Vercel's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Vercel connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add Vercel to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every Vercel tool, give Cursor only the read tools, or keep Vercel away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Vercel MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://toolstile.com/mcp'

Then connect Vercel in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Vercel endpoint to each app separately. In Claude Code:

Shell

claude mcp add --transport http vercel 'https://mcp.vercel.com'

In Cursor's mcp.json:

JSON

{
  "mcpServers": {
    "vercel": {
      "url": "https://mcp.vercel.com"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Vercel MCP documentation for what your client needs.

Before you connect

A Vercel account. Sign-in uses your Vercel permissions.

Server details

Detail	Value
Publisher	Vercel
Endpoint	`https://mcp.vercel.com`
Authentication	Browser sign-in
Categories	Development
Tool list	28 tools, observed 29 October 2026 (docs)

Vercel MCP documentation