Skip to Content
ResourcesIntegrationsDeveloper ToolsVercel

Vercel

Vercel icon
Arcade Optimized

Arcade.dev tools for interacting with Vercel

Author:Arcade
Version:0.1.0
Auth:No authentication required
23tools
23require secrets

The Vercel toolkit lets you manage Vercel projects, deployments, domains, and environment variables programmatically via Arcade. It covers the full project lifecycle — from creation and configuration through deployment, promotion, rollback, and teardown.

Capabilities

  • Account & team discovery — resolve the authenticated account, list accessible teams, and inspect team details (including billing plan) to establish the correct scope before making changes.
  • Project management — create, retrieve, list, update settings for, and permanently delete projects; optionally connect a Git repository at creation time.
  • Deployment lifecycle — trigger deployments from inline source files, connected Git repositories, or prior deployment sources; cancel in-progress builds; inspect state and build/runtime logs; promote a deployment to production; and roll production back to a prior build.
  • Custom domain management — attach and detach custom domains, retrieve verification and DNS-configuration status, list all domains on a project, and trigger re-verification against outstanding DNS challenges.
  • Environment variable management — list, create, update, and delete project environment variables across all environments.

Secrets

VERCEL_ACCESS_TOKEN is a Vercel personal access token (or team-scoped OAuth token) used to authenticate every API call. To obtain one:

  1. Log in to your Vercel account and open Account Settings → Tokens (personal token): https://vercel.com/account/tokens. For a team-scoped token, open the team's Settings → Tokens.
  2. Click Create, give it a name, choose an expiry, and optionally restrict it to a specific team scope.
  3. Copy the token immediately — Vercel only shows it once.
  4. The token needs sufficient permissions for all operations you intend to use (full-access tokens work for all tools; read-only tokens will fail write operations).

For details on creating tokens see the Vercel documentation on access tokens.

Store this value as an Arcade secret. See Arcade secret configuration docs and manage your secrets at https://api.arcade.dev/dashboard/auth/secrets.

Available tools(23)

23 of 23 tools
Operations
Behavior
Tool nameDescriptionSecrets
Attach a custom domain to a project; the result reports its verification status.
1
Cancel an in-progress deployment. Canceling a deployment that has already finished is not an error: its current (terminal) state is returned unchanged rather than reporting a cancellation.
1
Trigger a new deployment from inline source files, a git repository, or a prior deployment. The target project must already exist (create it first); an unknown project name or id is rejected rather than silently auto-created. Exactly one source is required: pass files to upload source inline (no Git connection needed, the way to ship a first deployment on an account without a connected repository), git_repo together with git_ref to deploy from a connected repository, or redeploy_of to rebuild a prior deployment's source. Deploying from a repository requires the Vercel account to have a connected Git integration for that provider.
1
Create a new project, optionally connecting a git repository to deploy from.
1
Delete an environment variable from a project.
1
Permanently delete a project and all of its deployments.
1
Return the Vercel account the access token authenticates as. Call this first in a session to confirm which account you are acting on before making any changes.
1
Return a single deployment's state and metadata.
1
Read a deployment's build and runtime log events to diagnose why it failed.
1
Return a single project's settings and latest deployment state.
1
Return a project domain's verification status and DNS-configuration state.
1
Return a team's details, including its billing plan.
1
List deployments in the active scope, optionally filtered by project, target, and state.
1
List a project's environment variables across all environments.
1
List the custom domains attached to a project.
1
List the projects in the active scope, optionally narrowed by a fuzzy name search.
1
List the teams the access token can act on, to discover a valid team scope.
1
Make a deployment the project's current production deployment ("ship this one"). A deployment that already targeted production (a staged or prior production build) is promoted instantly without a rebuild. A preview deployment cannot be aliased to production directly, because preview and production builds can differ (e.g. environment variables), so this rebuilds the preview's source as a new production deployment — the same complete-rebuild path the Vercel dashboard uses to promote a preview. In that case the returned deployment is the new build (still building), not the preview that was passed in.
1
Detach a custom domain from a project.
1
Roll production back to a prior deployment, making it the current production deployment.
1
Create or update a project environment variable. Omit env_id to create (key, value, and target are required); pass env_id to update an existing variable in place, changing only the fields you supply. Saving a variable does not affect already-built deployments: a new deployment must be triggered for the change to take effect.
1
Update a project's build and framework settings; unset fields are left unchanged.
1
Trigger verification of a project domain and return its resulting status. An unmet DNS challenge is the normal polling path, not an error: this returns the domain's still-unverified status (with the outstanding challenge records) rather than failing.
1

Selected tools

No tools selected.

Click "Show all tools" to add tools.

Requirements

Select tools to see requirements

#

Vercel.AddProjectDomain

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Create
MCP behavior
No

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

No

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Attach a custom domain to a project; the result reports its verification status.

Parameters

ParameterTypeReq.Description
projectstringRequiredProject id (prj_...) or name to attach the domain to.
domainstringRequiredFully-qualified domain name to attach (e.g. app.example.com).
redirectstringOptionalDomain to redirect this domain to. Defaults to None (serve the project directly).
git_branchstringOptionalGit branch to bind the domain to. Defaults to None (the production branch).
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.CancelDeployment

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Update
MCP behavior
No

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Cancel an in-progress deployment. Canceling a deployment that has already finished is not an error: its current (terminal) state is returned unchanged rather than reporting a cancellation.

Parameters

ParameterTypeReq.Description
deploymentstringRequiredDeployment id (dpl_...) to cancel.
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.CreateDeployment

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Create
MCP behavior
No

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

No

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Trigger a new deployment from inline source files, a git repository, or a prior deployment. The target project must already exist (create it first); an unknown project name or id is rejected rather than silently auto-created. Exactly one source is required: pass files to upload source inline (no Git connection needed, the way to ship a first deployment on an account without a connected repository), git_repo together with git_ref to deploy from a connected repository, or redeploy_of to rebuild a prior deployment's source. Deploying from a repository requires the Vercel account to have a connected Git integration for that provider.

Parameters

ParameterTypeReq.Description
namestringRequiredProject name the deployment belongs to.
projectstringOptionalProject id (prj_...) or name to deploy. Defaults to None (inferred from name).
targetstringOptionalEnvironment to deploy to. Selecting preview, or leaving this as the default None, creates a preview deployment, with one exception: a project's very first deployment is always promoted to production by Vercel regardless of this value, so an omitted target on a project that has no prior deployment still goes live in production.
productionpreview
filesarray<json>OptionalSource files to deploy inline, without any connected Git repository. Each entry is a file path and its UTF-8 text content. Use this to ship a first deployment for a project that has no Git integration. Defaults to None.
git_repostringOptionalRepository to deploy from, as owner/repo. Defaults to None (use files or redeploy_of instead).
git_refstringOptionalBranch name or commit SHA to deploy from the repository. Required whenever git_repo is set (Vercel does not infer a default branch). Defaults to None.
git_providerstringOptionalGit host the repository lives on. Defaults to github.
githubgitlabbitbucket
redeploy_ofstringOptionalDeployment id to redeploy. Rebuilds that deployment's source while picking up the project's current environment variables and build settings, so use this to roll out config changes (env vars edited after a deployment do not affect the running build until a rebuild). Defaults to None.
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.CreateProject

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Create
MCP behavior
No

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

No

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Create a new project, optionally connecting a git repository to deploy from.

Parameters

ParameterTypeReq.Description
namestringRequiredName for the new project (lowercase letters, digits, and hyphens).
frameworkstringOptionalFramework preset slug (e.g. nextjs, vite, sveltekit). Defaults to None (auto-detect).
git_repositorystringOptionalRepository to connect, as owner/repo (e.g. acme/marketing-site). Connecting a repository is what lets you deploy and scope preview variables to a branch. Defaults to None (no repository connected).
git_providerstringOptionalGit host the connected repository lives on. Defaults to github.
githubgitlabbitbucket
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.DeleteEnvironmentVariable

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Delete
MCP behavior
No

Reads data without modifying any state in the target system.

Yes

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Delete an environment variable from a project.

Parameters

ParameterTypeReq.Description
projectstringRequiredProject id (prj_...) or name the variable belongs to.
env_idstringRequiredId of the environment variable to delete.
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.DeleteProject

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Delete
MCP behavior
No

Reads data without modifying any state in the target system.

Yes

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Permanently delete a project and all of its deployments.

Parameters

ParameterTypeReq.Description
projectstringRequiredProject id (prj_...) or project name to delete.
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.GetCurrentUser

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Read
MCP behavior
Yes

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Return the Vercel account the access token authenticates as. Call this first in a session to confirm which account you are acting on before making any changes.

Parameters

No parameters required.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.GetDeployment

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Read
MCP behavior
Yes

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Return a single deployment's state and metadata.

Parameters

ParameterTypeReq.Description
deploymentstringRequiredDeployment id (dpl_...) or deployment URL to inspect.
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.GetDeploymentLogs

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Read
MCP behavior
Yes

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Read a deployment's build and runtime log events to diagnose why it failed.

Parameters

ParameterTypeReq.Description
deploymentstringRequiredDeployment id (dpl_...) or deployment URL to read logs for.
limitintegerOptionalMaximum number of log events to return (1-1000). Defaults to 100.
directionstringOptionalOrder to read events in. Defaults to forward (oldest first).
forwardbackward
sinceintegerOptionalOnly return events created at or after this epoch-millisecond time. Defaults to None.
untilintegerOptionalOnly return events created at or before this epoch-millisecond time. Defaults to None.
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.GetProject

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Read
MCP behavior
Yes

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Return a single project's settings and latest deployment state.

Parameters

ParameterTypeReq.Description
projectstringRequiredProject id (prj_...) or project name to inspect.
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.GetProjectDomain

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Read
MCP behavior
Yes

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Return a project domain's verification status and DNS-configuration state.

Parameters

ParameterTypeReq.Description
projectstringRequiredProject id (prj_...) or name the domain is attached to.
domainstringRequiredFully-qualified domain name to inspect.
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.GetTeam

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Read
MCP behavior
Yes

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Return a team's details, including its billing plan.

Parameters

ParameterTypeReq.Description
teamstringRequiredTeam id (team_...) or team slug to look up.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.ListDeployments

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Read
MCP behavior
Yes

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

List deployments in the active scope, optionally filtered by project, target, and state.

Parameters

ParameterTypeReq.Description
projectstringOptionalProject id (prj_...) or name to scope to. Defaults to None (all projects in scope).
targetstringOptionalFilter to deployments for this environment. Defaults to None (any environment).
productionpreview
statestringOptionalFilter to deployments in this state. Defaults to None (any state).
QUEUEDINITIALIZINGBUILDINGREADYERRORCANCELEDDELETED
limitintegerOptionalMaximum number of deployments to return (1-100). Defaults to 20.
cursorstringOptionalPagination cursor from a prior call's next_cursor. Defaults to None (first page).
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.ListEnvironmentVariables

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Read
MCP behavior
Yes

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

List a project's environment variables across all environments.

Parameters

ParameterTypeReq.Description
projectstringRequiredProject id (prj_...) or name to list variables for.
decryptbooleanOptionalWhether to include decrypted plaintext values in the result (only effective when the plan supports decryption). Defaults to False.
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.ListProjectDomains

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Read
MCP behavior
Yes

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

List the custom domains attached to a project.

Parameters

ParameterTypeReq.Description
projectstringRequiredProject id (prj_...) or name to list domains for.
limitintegerOptionalMaximum number of domains to return (1-100). Defaults to 20.
cursorstringOptionalPagination cursor from a prior call's next_cursor. Defaults to None (first page).
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.ListProjects

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Read
MCP behavior
Yes

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

List the projects in the active scope, optionally narrowed by a fuzzy name search.

Parameters

ParameterTypeReq.Description
searchstringOptionalCase-insensitive name fragment to filter projects by. Only projects whose name contains this fragment are returned. Defaults to None (no filter).
limitintegerOptionalNumber of projects to return (1-100). Without a search filter, a call returns up to this many. With a search filter, the listing is paged until at least this many matches are gathered (a call may return a few more from the last page scanned); use next_cursor for additional matches. Defaults to 20.
cursorstringOptionalPagination cursor from a prior call's next_cursor. Defaults to None (first page).
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.ListTeams

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Read
MCP behavior
Yes

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

List the teams the access token can act on, to discover a valid team scope.

Parameters

ParameterTypeReq.Description
limitintegerOptionalMaximum number of teams to return (1-100). Defaults to 20.
cursorstringOptionalPagination cursor from a prior call's next_cursor. Defaults to None (first page).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.PromoteDeployment

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Update
MCP behavior
No

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

No

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Make a deployment the project's current production deployment ("ship this one"). A deployment that already targeted production (a staged or prior production build) is promoted instantly without a rebuild. A preview deployment cannot be aliased to production directly, because preview and production builds can differ (e.g. environment variables), so this rebuilds the preview's source as a new production deployment — the same complete-rebuild path the Vercel dashboard uses to promote a preview. In that case the returned deployment is the new build (still building), not the preview that was passed in.

Parameters

ParameterTypeReq.Description
projectstringRequiredProject id (prj_...) or name whose production to repoint.
deploymentstringRequiredDeployment id (dpl_...) to make the current production deployment.
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.RemoveProjectDomain

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Delete
MCP behavior
No

Reads data without modifying any state in the target system.

Yes

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Detach a custom domain from a project.

Parameters

ParameterTypeReq.Description
projectstringRequiredProject id (prj_...) or name the domain is attached to.
domainstringRequiredFully-qualified domain name to detach.
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.RollbackDeployment

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Update
MCP behavior
No

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Roll production back to a prior deployment, making it the current production deployment.

Parameters

ParameterTypeReq.Description
projectstringRequiredProject id (prj_...) or name whose production to repoint.
deploymentstringRequiredPrior deployment id (dpl_...) to roll production back to.
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.SaveEnvironmentVariable

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
CreateUpdate
MCP behavior
No

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

No

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Create or update a project environment variable. Omit env_id to create (key, value, and target are required); pass env_id to update an existing variable in place, changing only the fields you supply. Saving a variable does not affect already-built deployments: a new deployment must be triggered for the change to take effect.

Parameters

ParameterTypeReq.Description
projectstringRequiredProject id (prj_...) or name the variable belongs to.
env_idstringOptionalId of an existing variable to update. Omit to create a new variable.
keystringOptionalVariable name. When creating, this is required and sets the name. When updating, it is ignored (the name is fixed). Defaults to None.
valuestringOptionalVariable value. When creating, this is required. When updating, providing it changes the value; omitting it leaves the value unchanged. Defaults to None.
targetarray<string>OptionalEnvironments the variable applies to. When creating, this is required. When updating, providing it replaces the set; omitting it leaves it unchanged. Defaults to None.
productionpreviewdevelopment
typestringOptionalHow the value is stored, applied only when creating. Defaults to encrypted.
encryptedplainsensitive
git_branchstringOptionalGit branch to scope a preview variable to (requires a project with a connected repository). When updating, providing it changes the scope. Defaults to None (all branches).
commentstringOptionalNote describing the variable. When updating, providing it changes the note. Defaults to None.
overwritebooleanOptionalWhen creating, whether to overwrite an existing variable with the same key and target instead of returning a conflict. Defaults to False.
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.UpdateProjectSettings

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Update
MCP behavior
No

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Update a project's build and framework settings; unset fields are left unchanged.

Parameters

ParameterTypeReq.Description
projectstringRequiredProject id (prj_...) or project name to update.
namestringOptionalNew project name. Defaults to None (unchanged).
frameworkstringOptionalNew framework preset slug (e.g. nextjs, vite). Pass an empty string to clear the preset so the project type reverts to no framework (Other / static). Defaults to None (unchanged).
build_commandstringOptionalOverride the build command. Defaults to None (unchanged).
install_commandstringOptionalOverride the install command. Defaults to None (unchanged).
output_directorystringOptionalOverride the build output directory. Defaults to None (unchanged).
root_directorystringOptionalOverride the project root directory. Defaults to None (unchanged).
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
#

Vercel.VerifyProjectDomain

Execution hints

Signals for MCP clients and agents about how this tool behaves.

Operations
Update
MCP behavior
No

Reads data without modifying any state in the target system.

No

May permanently delete or overwrite data in the target system.

Yes

Repeated calls with the same inputs produce no additional effect.

Yes

Communicates with external APIs, databases, or other services.

Trigger verification of a project domain and return its resulting status. An unmet DNS challenge is the normal polling path, not an error: this returns the domain's still-unverified status (with the outstanding challenge records) rather than failing.

Parameters

ParameterTypeReq.Description
projectstringRequiredProject id (prj_...) or name the domain is attached to.
domainstringRequiredFully-qualified domain name to verify.
teamstringOptionalTeam id (team_...) or team slug to scope the request to. Defaults to None (the token's own personal scope).

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:jsonNo description provided.
Last updated on