Skip to Content

Vercel API

Vercel API icon
Arcade Starter

Tools that enable LLMs to interact directly with the vercel API.

Author:Arcade
Version:1.0.0
Auth:No authentication required
194tools
194require secrets
PyPI VersionPython VersionsWheel StatusDownloadsLicense

VercelApi is a comprehensive toolkit enabling developers to integrate with the Vercel API for efficient project and deployment management. It provides seamless access to various functionalities related to domain management, deployment operations, team collaboration, and environmental configurations.

Capabilities

  • Manage project domains, environments, and associated configurations.
  • Facilitate user and team management within Vercel projects.
  • Accept project transfer requests and add members to projects.
  • Handle deployment operations, including creating, deleting, and promoting deployments.
  • Automate SSL certificate management and domain purchases.

Secrets

  • The toolkit utilizes authentication tokens, such as the VERCEL_ACCESS_TOKEN, for secure API access.

Available tools(194)

194 of 194
Tool nameDescriptionSecrets
Accept a project transfer request on Vercel. Use this tool to accept a project transfer request that has been initiated by another team on Vercel. This process requires a transfer code, which is generated by the initiating team. Call this tool when you need to finalize the transfer of a project to your team. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
1
Adds a token to an existing Edge Config. This tool is used to add a new token to an existing Edge Config in Vercel. It should be called when you need to update the configuration with additional access or permissions via token.
1
Add a new apex domain with Vercel for the user. Use this tool to add a new apex domain name with Vercel for the authenticating user. This tool is not meant for transferring domains from external registrars to Vercel. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
1
Add a domain to a specified Vercel project. This tool adds a domain to a Vercel project by specifying the domain name and project identifier (id or name). If the domain is unverified, the response will indicate it needs verification. If the domain already exists, a 400 error will occur.
1
Add a new member to a Vercel project. Use this tool to add a new member to a Vercel project using the project's ID or name. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
1
Advance a rollout to the next stage when manual approval is required. Use this tool to advance a release rollout to the next stage when manual approval is enabled in Vercel's rolling releases configuration. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
1
Cancel a currently building deployment. Use this tool to cancel a deployment that is currently in progress by providing its ID.
1
Check if a domain name is available for purchase. This tool checks the availability of a domain name for purchase, using the deprecated 'checkDomainStatus' endpoint from Vercel. Note that this endpoint has been replaced with 'Get availability for a domain.'
1
Check availability for multiple domains. Use this tool to check if multiple domains are available for purchase. This can help in planning before acquiring domains via the buying endpoints.
1
Retrieve the transfer status of a domain. Use this tool to check the current transfer status of a specific domain, providing insights into progress or any issues.
1
Check the status of Remote Caching. This tool is used to determine if Remote Caching is currently enabled, disabled, or disabled due to usage limits. It provides a quick way to verify the status of caching in Vercel.
1
Check the status of a team access request. Use this tool to check the status of a user's request to join a team on Vercel. The tool will return the status of the request or a 404 error if the request was declined. If no user ID is provided, it returns the status for the authenticated user.
1
Connect an integration resource to a Vercel project. This tool connects a provisioned integration resource to a specific Vercel project. It should be used when you need to establish a link between a resource and a project in Vercel. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
1
Create a new access group on Vercel. This tool should be called when there is a need to create a new access group in Vercel. It facilitates setting up user permissions and organization in projects. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
1
Create a project within a specific access group.
1
Create a new authentication token for the user. Use this tool to generate and retrieve a new authentication token for the currently authenticated user. Ensure to save the token for subsequent API requests, as it is only provided once.
1
Create a custom environment for your Vercel project. This tool creates a custom environment in a specified Vercel project, excluding 'Production' or 'Preview' as names. Use it to set up tailored project environments.
1
Creates a DNS record for a domain. Use this tool to create a DNS record for a specified domain. It helps manage DNS configurations by adding new records as needed. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
1
Create a new Edge Configuration. This tool is used to create a new Edge Config on Vercel. It should be called when there's a need to set up or initialize a configuration for edge functions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
1
Create one or multiple experimentation items. This tool is used to create one or multiple experimentation items for a specific installation. It should be called when you need to add experimentation data to a resource tied to an integration configuration. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
1
Create a new firewall bypass rule. This tool should be called to create new system bypass rules in the firewall. Useful for configuring security exceptions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
1
Sets up an Integration log drain for Vercel. This tool creates an Integration log drain in Vercel, accessible via an OAuth2 client. It should be used when you need to tie log drains to specific integrations within Vercel. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
1
Create integration stores for FREE and PAID billing plans. This tool creates integration stores on Vercel for both free and paid plans, handling billing automatically. It validates configurations, discovers free plans, and creates billing authorizations for paid resources. It should be called when you need to provision integration storage resources while managing billing. Requires admin access and, for paid plans, a valid payment method. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
1
Create a new deployment check using Vercel API. Use this tool to initiate a new check for a specific deployment in Vercel. This requires providing a deployment ID and must be authorized with OAuth2 to avoid errors.
1
Create a new project with specified configurations. This tool creates a new project using the provided configurations. You can specify only the project name or add additional configurations to customize the project further. Call this tool when you need to initialize a new project. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.
1
Page 1 of 8(25 of 194)

Selected tools

No tools selected.

Click "Show all tools" to add tools.

Requirements

Select tools to see requirements

#

VercelApi.AcceptProjectTransfer

Accept a project transfer request on Vercel. Use this tool to accept a project transfer request that has been initiated by another team on Vercel. This process requires a transfer code, which is generated by the initiating team. Call this tool when you need to finalize the transfer of a project to your team. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_transfer_codestringOptionalThe unique code of the project transfer request, required to accept the transfer. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier of the team to perform the request on behalf of. Only used when mode is 'execute'.
team_slugstringOptionalThe team slug used to perform the project transfer request on behalf of a specific team. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'acceptProjectTransferRequest'.
#

VercelApi.AddEdgeConfigToken

Adds a token to an existing Edge Config. This tool is used to add a new token to an existing Edge Config in Vercel. It should be called when you need to update the configuration with additional access or permissions via token.

Parameters

ParameterTypeReq.Description
edge_config_idstringRequiredThe unique identifier for the Edge Config to which the token will be added.
token_labelstringRequiredA descriptive label for the token being added to the Edge Config.
team_identifierstringOptionalThe identifier for the team on whose behalf the request is performed.
team_slugstringOptionalThe slug identifying the Team on whose behalf the request is made. This is used for specifying the target team within Vercel.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createEdgeConfigToken'.
#

VercelApi.AddNewDomainVercel

Add a new apex domain with Vercel for the user. Use this tool to add a new apex domain name with Vercel for the authenticating user. This tool is not meant for transferring domains from external registrars to Vercel. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
team_identifierstringOptionalThe identifier of the Team on whose behalf the request is made. Only used when mode is 'execute'.
team_slugstringOptionalThe identifier for the team to execute the request on behalf of. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createOrTransferDomain'.
#

VercelApi.AddProjectDomain

Add a domain to a specified Vercel project. This tool adds a domain to a Vercel project by specifying the domain name and project identifier (id or name). If the domain is unverified, the response will indicate it needs verification. If the domain already exists, a 400 error will occur.

Parameters

ParameterTypeReq.Description
project_domain_namestringRequiredThe domain name to be added to the specified Vercel project.
project_identifier_or_namestringRequiredThe unique identifier or name of the project to which the domain will be added.
custom_environment_idstringOptionalThe unique custom environment identifier within the project.
git_branch_to_link_domainstringOptionalThe Git branch to associate with the project domain when adding it to a Vercel project. This allows the domain to be tied to a specific branch in the repository.
redirect_status_codeintegerOptionalHTTP status code for redirecting the domain. Options are: 301, 302, 307, 308, or None.
redirect_target_domainstringOptionalSpecify the target destination domain to redirect to.
team_identifierstringOptionalThe identifier of the team for which the request is made. This ensures the request is executed on behalf of the specified team.
team_slugstringOptionalThe slug of the team to perform the request on behalf of. This identifies the team context for the domain addition.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'addProjectDomain'.
#

VercelApi.AddProjectMember

Add a new member to a Vercel project. Use this tool to add a new member to a Vercel project using the project's ID or name. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_id_or_namestringOptionalThe ID or name of the Vercel project to which a new member will be added. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier of the Team to perform the request on behalf of. Only used when mode is 'execute'.
team_slugstringOptionalThe slug identifying the team for performing the request. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'addProjectMember'.
#

VercelApi.AdvanceRolloutStage

Advance a rollout to the next stage when manual approval is required. Use this tool to advance a release rollout to the next stage when manual approval is enabled in Vercel's rolling releases configuration. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_identifierstringOptionalProject ID or URL-encoded project name to identify the project. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe Team identifier used for performing the request on behalf of the specified team. Only used when mode is 'execute'.
team_slugstringOptionalThe slug representing the team for which the rollout action will be performed. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'approveRollingReleaseStage'.
#

VercelApi.CancelDeployment

Cancel a currently building deployment. Use this tool to cancel a deployment that is currently in progress by providing its ID.

Parameters

ParameterTypeReq.Description
deployment_idstringRequiredThe unique identifier of the deployment to cancel.
team_identifierstringOptionalThe Team identifier to perform the request on behalf of when canceling a deployment.
team_slugstringOptionalThe Team slug for which the deployment cancellation should be performed.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'cancelDeployment'.
#

VercelApi.CheckDomainAvailability

Check if a domain name is available for purchase. This tool checks the availability of a domain name for purchase, using the deprecated 'checkDomainStatus' endpoint from Vercel. Note that this endpoint has been replaced with 'Get availability for a domain.'

Parameters

ParameterTypeReq.Description
domain_namestringRequiredThe domain name you want to check for purchase availability.
team_identifierstringOptionalThe identifier of the Team on whose behalf the request is performed.
team_slugstringOptionalThe slug for the team or organization on whose behalf the request is performed.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'checkDomainStatus'.
#

VercelApi.CheckDomainAvailabilityBulk

Check availability for multiple domains. Use this tool to check if multiple domains are available for purchase. This can help in planning before acquiring domains via the buying endpoints.

Parameters

ParameterTypeReq.Description
domain_namesarray<string>RequiredA list of domain names to check, with a maximum of 50 domains.
team_identifierstringOptionalUnique identifier for the team or organization associated with the request. It may be required to access specific domain availability data.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getBulkAvailability'.
#

VercelApi.CheckDomainTransferStatus

Retrieve the transfer status of a domain. Use this tool to check the current transfer status of a specific domain, providing insights into progress or any issues.

Parameters

ParameterTypeReq.Description
domain_namestringRequiredSpecifies the domain name to check the transfer status for. It should be a valid domain string.
team_idstringOptionalThe unique identifier of the team requesting the domain transfer status.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getDomainTransferIn'.
#

VercelApi.CheckRemoteCachingStatus

Check the status of Remote Caching. This tool is used to determine if Remote Caching is currently enabled, disabled, or disabled due to usage limits. It provides a quick way to verify the status of caching in Vercel.

Parameters

ParameterTypeReq.Description
team_identifierstringOptionalThe unique identifier for the team to perform the request on behalf of.
team_slugstringOptionalThe unique slug identifier for the team on whose behalf the request is made.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'status'.
#

VercelApi.CheckTeamAccessStatus

Check the status of a team access request. Use this tool to check the status of a user's request to join a team on Vercel. The tool will return the status of the request or a 404 error if the request was declined. If no user ID is provided, it returns the status for the authenticated user.

Parameters

ParameterTypeReq.Description
team_idstringRequiredThe unique identifier for the team whose access request status is being checked.
user_idstringRequiredThe ID of the user whose team access request status is being checked. Leave empty to use the authenticated user.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getTeamAccessRequest'.
#

VercelApi.ConnectIntegrationResourceToProject

Connect an integration resource to a Vercel project. This tool connects a provisioned integration resource to a specific Vercel project. It should be used when you need to establish a link between a resource and a project in Vercel. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
integration_configuration_idstringOptionalThe identifier for the integration configuration to be connected to the Vercel project. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
resource_idstringOptionalThe ID of the integration resource to connect to the Vercel project. This is required to establish the link. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe identifier of the team to perform the request on behalf of. Only used when mode is 'execute'.
team_slugstringOptionalThe unique team slug used to perform the request on behalf of a specific team in Vercel. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'connectIntegrationResourceToProject'.
#

VercelApi.CreateAccessGroup

Create a new access group on Vercel. This tool should be called when there is a need to create a new access group in Vercel. It facilitates setting up user permissions and organization in projects. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
team_identifierstringOptionalThe identifier of the team on whose behalf the access group is being created. Only used when mode is 'execute'.
team_slugstringOptionalThe unique slug identifier for the team to create the access group for. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createAccessGroup'.
#

VercelApi.CreateAccessGroupProject

Create a project within a specific access group.

Parameters

ParameterTypeReq.Description
access_group_id_or_namestringRequiredIdentifier or name of the access group to associate with the project. It helps specify which access group the new project will be part of.
project_idstringRequiredThe unique ID of the project to be added to the access group.
project_rolestringRequiredThe role to be assigned to the project within the access group. Options: 'ADMIN', 'PROJECT_VIEWER', 'PROJECT_DEVELOPER'.
team_identifierstringOptionalThe unique identifier for the team to perform the request on behalf of.
team_slugstringOptionalThe unique identifier slug for the team on whose behalf the request is made.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createAccessGroupProject'.
#

VercelApi.CreateAuthToken

Create a new authentication token for the user. Use this tool to generate and retrieve a new authentication token for the currently authenticated user. Ensure to save the token for subsequent API requests, as it is only provided once.

Parameters

ParameterTypeReq.Description
token_namestringRequiredA descriptive name for the authentication token. This helps in identifying the token's purpose or context.
expiration_timestampnumberOptionalThe expiration time for the token, specified as a Unix timestamp. This defines when the token will no longer be valid.
team_identifierstringOptionalThe unique identifier for the Team to perform the request on behalf of.
team_slugstringOptionalThe slug of the Team to perform the request on behalf of. This identifies the specific team within your Vercel account.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createAuthToken'.
#

VercelApi.CreateCustomEnvironment

Create a custom environment for your Vercel project. This tool creates a custom environment in a specified Vercel project, excluding 'Production' or 'Preview' as names. Use it to set up tailored project environments.

Parameters

ParameterTypeReq.Description
project_unique_identifier_or_namestringRequiredThe unique project identifier or project name for which the custom environment is being created.
branch_matcher_typestringOptionalSpecifies the type of branch matcher: 'equals', 'startsWith', or 'endsWith'.
copy_environment_variables_fromstringOptionalSpecify the source environment to copy variables from. This is optional.
custom_environment_slugstringOptionalSpecify the slug for the new custom environment. It cannot be 'Production' or 'Preview'.
environment_descriptionstringOptionalOptional description for the custom environment being created.
git_branch_name_patternstringOptionalGit branch name or part of it to match with the custom environment.
team_identifierstringOptionalThe identifier of the team to perform the request on behalf of.
team_slugstringOptionalThe slug of the team to perform the request on behalf of. It is required to specify the unique team for the custom environment.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createCustomEnvironment'.
#

VercelApi.CreateDnsRecord

Creates a DNS record for a domain. Use this tool to create a DNS record for a specified domain. It helps manage DNS configurations by adding new records as needed. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
domain_name_for_dns_recordstringOptionalThe domain for which the DNS record will be created. Must be a valid and registered domain name. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe Team identifier for performing the request. Only used when mode is 'execute'.
team_slugstringOptionalThe slug identifier for the team performing the DNS record creation. It should be a string that represents the team's unique slug. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createRecord'.
#

VercelApi.CreateEdgeConfig

Create a new Edge Configuration. This tool is used to create a new Edge Config on Vercel. It should be called when there's a need to set up or initialize a configuration for edge functions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
team_identifierstringOptionalThe identifier of the team to perform the request for. This is required to specify on whose behalf the request is made. Only used when mode is 'execute'.
team_slugstringOptionalThe Team slug that specifies the team to perform the request on behalf of. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createEdgeConfig'.
#

VercelApi.CreateExperimentationItems

Create one or multiple experimentation items. This tool is used to create one or multiple experimentation items for a specific installation. It should be called when you need to add experimentation data to a resource tied to an integration configuration. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
integration_configuration_idstringOptionalThe ID of the integration configuration for which to create experimentation items. This ties the items to a specific setup or environment. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
resource_identifierstringOptionalThe unique identifier of the resource to associate with the experimentation items. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint ''.
#

VercelApi.CreateFirewallBypassRule

Create a new firewall bypass rule. This tool should be called to create new system bypass rules in the firewall. Useful for configuring security exceptions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_idstringOptionalThe identifier for the project to create a bypass rule for. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe identifier for the team on whose behalf the request is made. Only used when mode is 'execute'.
team_slugstringOptionalThe slug identifier of the team for which the bypass rule is created. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'addBypassIp'.
#

VercelApi.CreateIntegrationLogDrain

Sets up an Integration log drain for Vercel. This tool creates an Integration log drain in Vercel, accessible via an OAuth2 client. It should be used when you need to tie log drains to specific integrations within Vercel. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
team_identifierstringOptionalThe Team identifier for performing the request on behalf of a specific team in Vercel. Only used when mode is 'execute'.
team_slugstringOptionalThe slug representing the team to perform the request on behalf of. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createLogDrain'.
#

VercelApi.CreateIntegrationStore

Create integration stores for FREE and PAID billing plans. This tool creates integration stores on Vercel for both free and paid plans, handling billing automatically. It validates configurations, discovers free plans, and creates billing authorizations for paid resources. It should be called when you need to provision integration storage resources while managing billing. Requires admin access and, for paid plans, a valid payment method. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
team_identifierstringOptionalThe unique identifier of the team on whose behalf the request is being made. Only used when mode is 'execute'.
team_slugstringOptionalThe unique slug of the team for which the integration store is being created. This identifies the team on behalf of which the request is made. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createIntegrationStoreDirect'.
#

VercelApi.CreateNewDeploymentCheck

Create a new deployment check using Vercel API. Use this tool to initiate a new check for a specific deployment in Vercel. This requires providing a deployment ID and must be authorized with OAuth2 to avoid errors.

Parameters

ParameterTypeReq.Description
block_deployment_on_failurebooleanRequiredIndicates if the check should block a deployment from succeeding.
check_namestringRequiredThe name of the check being created. This is required to identify the check purpose.
deployment_idstringRequiredThe unique identifier of the deployment to create the check for.
allow_rerun_requestbooleanOptionalAllow users to request a rerun of the check if it fails. Use a boolean value.
details_urlstringOptionalA URL that provides further details about the check. Expected format is a valid URL string.
external_identifierstringOptionalA unique identifier used as an external reference for the check.
page_path_to_checkstringOptionalSpecify the path of the page that is being checked. This should be a string value representing the specific page path for the deployment check.
team_identifierstringOptionalThe unique identifier used to perform the request on behalf of a team.
team_slugstringOptionalThe slug (unique identifier) of the team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createCheck'.
#

VercelApi.CreateNewProject

Create a new project with specified configurations. This tool creates a new project using the provided configurations. You can specify only the project name or add additional configurations to customize the project further. Call this tool when you need to initialize a new project. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
team_identifierstringOptionalThe identifier of the team on whose behalf the project will be created. Only used when mode is 'execute'.
team_slugstringOptionalThe slug representing the Team to perform the request on behalf of. It should be a string identifier. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createProject'.
#

VercelApi.CreateProjectEnvironmentVariables

Create or update environment variables for a Vercel project. This tool creates or updates one or more environment variables for a specified Vercel project. The project can be identified by its `id` or `name`. The tool allows specifying the `key`, `value`, `type`, and `target` of the environment variables. If `upsert=true` is included, existing variables will be updated instead of creating new ones. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_identifier_or_namestringOptionalThe unique identifier or name of the Vercel project to create or update environment variables for. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
allow_override_existing_variablestringOptionalAllows updating the value of an existing environment variable if set to true. Only used when mode is 'execute'.
team_identifierstringOptionalThe Team identifier to perform the request on behalf of, specified as a string. Only used when mode is 'execute'.
team_slugstringOptionalThe Team slug for the project. Used to perform the request on behalf of a specific team. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createProjectEnv'.
#

VercelApi.CreateVercelDeployment

Create a new deployment on Vercel. This tool helps create a new deployment on Vercel, ideal for deploying projects that aren't directly linked to a git repository. Use it to initiate a deployment by providing necessary files either as references or inlined content. It also allows redeployment of previous deployments by specifying a deployment ID. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
force_new_deploymentstringOptionalSet to 'true' to force a new deployment even if a similar one exists. Only used when mode is 'execute'.
skip_framework_detection_confirmationstringOptionalSet to 'true' to skip framework detection and avoid confirmation request failures. Only used when mode is 'execute'.
team_identifierstringOptionalThe Team identifier to perform the request on behalf of for creating a deployment on Vercel. Only used when mode is 'execute'.
team_slugstringOptionalThe slug identifying the team to perform the deployment on behalf of. This is essential for specifying the target team for the deployment request. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createDeployment'.
#

VercelApi.CreateVercelTeam

Create a new team in your Vercel account. Use this tool to create a new team under your Vercel account by specifying a team slug, and optionally a team name. This is useful for organizing projects and members under a unified group.

Parameters

ParameterTypeReq.Description
team_slugstringRequiredThe desired slug for the new team, used as a team identifier.
session_landing_pagestringOptionalThe URL of the landing page where the session started. This is used for session attribution on Vercel.
session_referrerstringOptionalReferrer URL for the session initiating the team creation process.
signup_referrer_pagestringOptionalThe referrer URL of the page before the signup page, used for tracking attribution.
team_namestringOptionalThe desired name for the Team. If not provided, it will be generated from the slug.
utm_campaign_namestringOptionalSpecifies the UTM campaign name for tracking purposes when creating a team.
utm_mediumstringOptionalThe medium through which the user arrived, such as email, social, or cpc.
utm_sourcestringOptionalThe UTM source identifier, indicating where the traffic originates from, such as a search engine or newsletter.
utm_termstringOptionalThe UTM term used for tracking specific keywords in marketing campaigns.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createTeam'.
#

VercelApi.CreateVercelWebhook

Create a new webhook in Vercel projects. This tool is used to create a new webhook in Vercel. It should be called when you need to set up automated notifications or integrations by creating a webhook within your Vercel projects.

Parameters

ParameterTypeReq.Description
events_listarray<string>RequiredA list of event types that trigger the webhook. Must be an array of strings, each representing an event.
webhook_urlstringRequiredThe target URL where the webhook will send POST requests. It should be a valid and publicly accessible URL.
project_idsarray<string>OptionalList of project IDs for which the webhook is being created. Each ID should be a string.
team_identifierstringOptionalThe identifier for the team on whose behalf the request is performed.
team_slugstringOptionalThe slug representing the Vercel team to target the request for. It identifies the team on whose behalf the webhook is created.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createWebhook'.
#

VercelApi.DeleteAccessGroup

Deletes an access group by ID or name. Use this tool to delete an access group on Vercel by specifying the group's ID or name. It is useful for managing and updating your access control configurations.

Parameters

ParameterTypeReq.Description
group_id_or_namestringRequiredThe ID or name of the access group to be deleted.
team_identifierstringOptionalThe identifier for the team on whose behalf the request is made.
team_slugstringOptionalThe slug for the team on whose behalf the request will be made. This identifies the team uniquely.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteAccessGroup'.
#

VercelApi.DeleteAccessGroupProject

Delete a specified access group project on Vercel. Use this tool to delete a specific access group project on Vercel by providing the access group ID or name and project ID.

Parameters

ParameterTypeReq.Description
access_group_id_or_namestringRequiredEnter the access group ID or name to identify the specific group for project deletion.
project_idstringRequiredThe ID of the project you want to delete from the access group.
team_identifierstringOptionalThe ID of the team to perform the request on behalf of.
team_slugstringOptionalThe slug of the team to perform the deletion on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteAccessGroupProject'.
#

VercelApi.DeleteAliasById

Delete a specific alias by its ID. Use this tool to delete an alias from Vercel using its unique ID.

Parameters

ParameterTypeReq.Description
alias_id_to_removestringRequiredThe unique ID or alias of the item to be removed from Vercel.
team_identifierstringOptionalThe unique identifier for the team to execute the request.
team_slugstringOptionalThe unique slug of the team for which the alias will be deleted.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteAlias'.
#

VercelApi.DeleteCacheByTags

Marks cache tags as deleted to revalidate associated entries. Use this tool to delete cache entries marked by specific tags, causing associated entries to be revalidated. This should be employed cautiously due to potential cache stampede risks. It's useful when the origin returns status codes like 404 or 410. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_id_or_namestringOptionalThe ID or name of the project associated with the cache tags to delete. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe identifier for the team on whose behalf the cache deletion request is performed. Only used when mode is 'execute'.
team_slugstringOptionalSpecify the team slug to perform the cache deletion on behalf of a team. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'dangerouslyDeleteByTags'.
#

VercelApi.DeleteDeployment

Delete a Vercel deployment using its ID or URL. Use this tool to delete a Vercel deployment by providing the deployment's `id` or `url`. Useful for managing and cleaning up deployments.

Parameters

ParameterTypeReq.Description
deployment_idstringRequiredThe ID of the deployment to be deleted. Use this if not providing a URL.
deployment_urlstringOptionalA Deployment or Alias URL for identifying the deployment to delete. The ID will be ignored if this is provided.
team_identifierstringOptionalThe unique identifier for the team on whose behalf the request is executed.
team_slugstringOptionalThe Team slug to perform the deletion on behalf of. Specify which team's deployment to delete.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteDeployment'.
#

VercelApi.DeleteEdgeConfig

Delete a Vercel Edge Config by ID. Use this tool to delete a specific Edge Config in Vercel by providing its unique ID. This will remove the configuration from the system.

Parameters

ParameterTypeReq.Description
edge_config_idstringRequiredThe unique identifier of the Edge Config to be deleted.
team_identifierstringOptionalThe unique identifier for the team on whose behalf the request is made.
team_slugstringOptionalThe slug of the team on whose behalf the request is performed.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteEdgeConfig'.
#

VercelApi.DeleteEdgeConfigSchema

Deletes an existing Edge Config schema. Use this tool to delete the schema of an existing Edge Config in a Vercel project. This can be useful for managing and updating Edge Configurations efficiently.

Parameters

ParameterTypeReq.Description
edge_config_idstringRequiredThe unique identifier for the specific Edge Config schema to be deleted.
team_identifierstringOptionalThe identifier of the team on whose behalf the request is made.
team_slugstringOptionalThe slug representing the team on whose behalf the request is performed. It uniquely identifies the team within Vercel.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteEdgeConfigSchema'.
#

VercelApi.DeleteEdgeConfigTokens

Delete tokens from an existing Edge Config. Use this tool to delete one or more tokens associated with a specific Edge Config in Vercel. It is useful for managing and securing access by removing outdated or compromised tokens.

Parameters

ParameterTypeReq.Description
edge_config_idstringRequiredThe unique identifier for the Edge Config from which tokens will be deleted. Required for specifying the target Edge Config.
tokens_to_deletearray<string>RequiredA list of token identifiers to be deleted from the Edge Config. Each token should be a string.
team_identifierstringOptionalThe unique identifier of the team to perform the request on behalf of.
team_slugstringOptionalThe Team slug representing the team on whose behalf the request is performed.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteEdgeConfigTokens'.
#

VercelApi.DeleteExperimentationItem

Delete an existing experimentation item. This tool deletes a specific experimentation item identified by its itemId within the given integration configuration and resource.

Parameters

ParameterTypeReq.Description
experiment_item_idstringRequiredThe unique identifier for the experimentation item to be deleted.
integration_configuration_idstringRequiredThe ID of the integration configuration to identify the correct setup.
resource_idstringRequiredThe unique identifier for the resource containing the item to be deleted. This is required to specify which resource the item belongs to.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint ''.
#

VercelApi.DeleteIntegrationLogDrain

Delete an Integration log drain by ID. Use this tool to delete a specific Integration log drain by its ID. Applicable when you need to remove log drains associated with an integration, especially under OAuth2 constraints.

Parameters

ParameterTypeReq.Description
log_drain_idstringRequiredThe ID of the log drain to be deleted. This identifies the specific log drain for removal.
team_identifierstringOptionalThe identifier of the Team on whose behalf the request is made.
team_slugstringOptionalThe slug of the team on whose behalf the request is performed.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteIntegrationLogDrain'.
#

VercelApi.DeleteIntegrationResource

Delete a resource from an integration by ID. Use this tool to delete a resource associated with a specific integration installation. You need the installation and resource IDs to successfully execute this operation.

Parameters

ParameterTypeReq.Description
integration_installation_idstringRequiredThe ID of the installation to delete the resource from.
resource_idstringRequiredThe ID of the resource to be deleted. Required for identifying the specific resource within the integration.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'delete-integration-resource'.
#

VercelApi.DeleteProject

Delete a Vercel project by ID or name. Use this tool to delete a specific Vercel project by providing either the project's ID or name. Ideal for cleaning up unused projects or managing active projects through automation.

Parameters

ParameterTypeReq.Description
project_identifier_or_namestringRequiredThe unique project identifier or the project name to specify which project to delete.
team_identifierstringOptionalThe unique identifier of the team to perform the project deletion.
team_slugstringOptionalThe slug representing the team to execute the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteProject'.
#

VercelApi.DeleteProjectEnvVariable

Delete a project's specific environment variable. This tool deletes a specified environment variable from a project by using the environment variable's identifier. You can specify the project using its ID or name.

Parameters

ParameterTypeReq.Description
environment_variable_identifierstringRequiredThe unique identifier of the environment variable to be deleted.
project_identifier_or_namestringRequiredThe unique project identifier or name to identify the target project for which the environment variable should be deleted.
custom_environment_identifierstringOptionalThe unique custom environment identifier within the project.
team_identifierstringOptionalThe Team identifier to perform the request on behalf of.
team_slugstringOptionalThe Team slug used to perform the request on behalf of a team.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'removeProjectEnv'.
#

VercelApi.DeleteProjectEnvVariables

Delete multiple environment variables from a Vercel project. Use this tool to delete several environment variables for a specific Vercel project at once. It's useful when managing project configurations and needing to remove obsolete or sensitive data efficiently. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_id_or_namestringOptionalThe unique project identifier or the project name to specify which project to delete variables from. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe Team identifier to perform the request on behalf of when deleting environment variables. Only used when mode is 'execute'.
team_slugstringOptionalThe slug representing the team on whose behalf the request is performed. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'batchRemoveProjectEnv'.
#

VercelApi.DeleteTeam

Delete a team from your Vercel account. Use this tool to send a request to delete a specific team under your Vercel account by providing the team ID. Optional reasons for deletion can be included. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
team_identifierstringOptionalThe unique identifier of the team to be deleted in your Vercel account. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
new_default_team_idstringOptionalSpecify the team ID to set as the new default after deletion. Only used when mode is 'execute'.
team_slugstringOptionalThe slug of the team you want to delete. Used to identify the team for the delete operation. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteTeam'.
#

VercelApi.DeleteTeamInviteCode

Delete an active team invite code in Vercel. Use this tool to remove an active team invite code for a specified team on Vercel. Call this tool when you need to cancel or invalidate an existing invite.

Parameters

ParameterTypeReq.Description
team_identifierstringRequiredThe unique identifier of the team to perform the operation for in Vercel.
team_invite_code_idstringRequiredThe ID of the team invite code to be deleted in Vercel.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteTeamInviteCode'.
#

VercelApi.DeleteVercelDomain

Delete a domain from Vercel and remove associated aliases. Use this tool to delete a previously registered domain from Vercel. This action also removes any aliases linked to the domain.

Parameters

ParameterTypeReq.Description
domain_namestringRequiredThe domain name to be deleted from Vercel. This action will also remove any associated aliases.
team_identifierstringOptionalThe identifier of the team to perform the domain deletion request on behalf of.
team_slugstringOptionalThe specific team slug to perform the deletion request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteDomain'.
#

VercelApi.DeleteVercelWebhook

Delete a specific webhook from Vercel. This tool deletes a specified webhook from a Vercel project using its unique ID. It should be called when you need to remove an existing webhook integration.

Parameters

ParameterTypeReq.Description
webhook_idstringRequiredThe unique identifier of the webhook to be deleted.
team_identifierstringOptionalThe Team identifier used to perform the request on behalf of the specified team.
team_slugstringOptionalThe slug representing the Vercel team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteWebhook'.
#

VercelApi.DisableRollingReleases

Disable rolling releases for a Vercel project. Use this tool to disable future rolling releases for a specified Vercel project. Note that this will not affect any current rollouts in progress. For ongoing rollouts, additional actions like completing or aborting may be required.

Parameters

ParameterTypeReq.Description
project_id_or_namestringRequiredProject ID or URL-encoded name to specify the Vercel project.
team_identifierstringOptionalThe identifier of the team to execute the request on behalf of.
team_slugstringOptionalThe slug identifying the team to perform the request on behalf of. This should be a string value.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteRollingReleaseConfig'.
#

VercelApi.DomainAvailabilityStatus

Check if a domain is available for purchase. This tool checks the availability of a specified domain. If the domain is available, it can be purchased using the appropriate Vercel endpoints.

Parameters

ParameterTypeReq.Description
domain_name_to_check_availabilitystringRequiredThe domain name to check for availability. Must be a valid and complete domain name string.
team_identifierstringOptionalA unique identifier for the team whose domain availability is being queried. This is a string value.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getDomainAvailability'.
#

VercelApi.DownloadCacheArtifact

Downloads a cache artifact using its hash identifier. Use this tool to retrieve a cache artifact from Vercel by specifying its hash. The artifact is returned as an octet-stream. Ensure to verify the content-length header and response body for correctness.

Parameters

ParameterTypeReq.Description
artifact_hashstringRequiredThe unique hash identifier for the cache artifact to download.
ci_environmentstringOptionalSpecify the continuous integration or delivery environment from which the artifact is downloaded.
interactive_shell_clientintegerOptionalSet to 1 if the client is an interactive shell; otherwise set to 0.
team_identifierstringOptionalThe Team identifier to perform the request on behalf of.
team_slugstringOptionalThe slug of the team to perform the request on behalf of, identifying which team's artifact to download.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'downloadArtifact'.
#

VercelApi.EditProjectEnvironmentVariable

Edit a specific environment variable for a project. Use this tool to modify an environment variable of a Vercel project by providing the variable's ID and the project's ID or name. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_id_or_namestringOptionalSpecify the unique project identifier or the project name. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
environment_variable_idstringOptionalThe unique environment variable identifier for the Vercel project. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier for the team on whose behalf the request is made. Only used when mode is 'execute'.
team_slugstringOptionalThe identifier for the team on whose behalf the request is made. This is usually a URL-friendly name for the team. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'editProjectEnv'.
#

VercelApi.ExchangeSsoToken

Exchange OAuth code for an OIDC token to authenticate users. Call this tool to exchange an OAuth authorization code for an OIDC token during the SSO process. This helps authenticate users in Vercel without persisting the token. Refer to the Vercel SSO documentation for more details.

Parameters

ParameterTypeReq.Description
authorization_codestringRequiredThe sensitive OAuth authorization code received from Vercel for the SSO token exchange process.
integration_client_idstringRequiredThe unique client ID for the integration, required for authentication.
integration_client_secretstringRequiredThe secret key for the integration client, used for authentication.
authorization_statestringOptionalThe state received from the initialization request for security validation.
integration_redirect_uristringOptionalThe URL where the user will be redirected after authentication.
sso_grant_typestringOptionalSpecifies the grant type as 'authorization_code' for OAuth process.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'exchange-sso-token'.
#

VercelApi.FetchAccountInfo

Fetch the best account or user's contact info. Use this tool to retrieve detailed contact information for a user's account, ideal for scenarios where you need user engagement or account verification.

Parameters

ParameterTypeReq.Description
integration_configuration_idstringRequiredThe unique identifier for the integration configuration. Required to fetch the user's account info.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'get-account-info'.
#

VercelApi.FetchDeploymentLogs

Retrieve build logs for a specific deployment by ID. Use this tool to access the build logs or events of a deployment using its deployment ID and build ID. It can stream logs continuously or return them in JSON format based on input parameters.

Parameters

ParameterTypeReq.Description
deployment_identifier_or_hostnamestringRequiredThe unique identifier or hostname of the deployment to fetch logs for.
build_event_delimiternumberOptionalSpecify the delimiter type for separating logged events. Use '0' for no delimiter and '1' for an alternative separation method.
deployment_build_idstringOptionalThe unique identifier for the deployment build for which logs are to be retrieved.
enable_live_streamingnumberOptionalSet to '1' to enable live streaming of events as they happen. Use '0' to disable live streaming.
event_orderstringOptionalSpecifies the order of returned events by timestamp. Use 'forward' for chronological order or 'backward' for reverse order.
fetch_until_timestampnumberOptionalTimestamp up to which the build logs should be retrieved.
filter_by_status_codestringOptionalSpecify the HTTP status code range to filter deployment events.
include_buildsnumberOptionalSpecify whether to include build events (1) or not (0) in the response.
maximum_events_to_returnnumberOptionalSpecify the max number of events to return. Use `-1` for all available logs.
start_timestamp_for_logsnumberOptionalTimestamp from which to start retrieving build logs. Provide in milliseconds.
team_identifierstringOptionalIdentifies the team on whose behalf the request is performed.
team_slugstringOptionalThe unique identifier (slug) of the Team for which the request is made. Used to specify the team context.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getDeploymentEvents'.
#

VercelApi.FetchDomainPrice

Retrieve price data for a specific domain from Vercel. Use this tool to get pricing information for a particular domain. It should be called when you need to verify or compare the cost of registering or renewing a domain via Vercel's registrar service.

Parameters

ParameterTypeReq.Description
domain_namestringRequiredThe domain name to check the pricing for. Provide a fully qualified domain like 'example.com'.
number_of_yearsstringOptionalSpecify the number of years for which the domain pricing is needed. Typically set to 1 or more.
team_identifierstringOptionalA string representing the unique identifier of the team associated with the domain. This is required for specifying which team's domain pricing information should be retrieved.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getDomainPrice'.
#

VercelApi.FetchDomainTransferAvailability

Fetch a domain's transfer status or availability. Use this tool to check if a domain transfer is available or to obtain the transfer status if a transfer is in progress.

Parameters

ParameterTypeReq.Description
domain_namestringRequiredThe domain name to check for transfer status or availability.
team_identifierstringOptionalThe Team identifier to perform the request on behalf of. It should be a string representing the team's unique ID.
team_slugstringOptionalThe identifier slug of the team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getDomainTransfer'.
#

VercelApi.FetchIntegrationResource

Fetch a resource using its partner ID. Use this tool to get detailed information about a specific resource by providing the integration configuration and resource IDs.

Parameters

ParameterTypeReq.Description
integration_configuration_idstringRequiredThe ID of the specific installation to which the resource belongs.
third_party_resource_idstringRequiredThe ID provided by the third-party provider for the specific resource.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'get-integration-resource'.
#

VercelApi.FetchProjectDomain

Fetch domain details for a specific project. Use this tool to obtain detailed information about a project's domain using the project's ID or name and the domain name.

Parameters

ParameterTypeReq.Description
project_domain_namestringRequiredThe name of the project's domain to fetch details for.
project_id_or_namestringRequiredThe unique project identifier or the project name for fetching domain details.
team_identifierstringOptionalThe Team identifier to perform the request on behalf of.
team_slugstringOptionalThe slug of the team on whose behalf the request is made.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getProjectDomain'.
#

VercelApi.ForceCompleteRollingRelease

Complete a rolling release to serve 100% traffic from canary. This tool should be used to force-complete a rolling release in Vercel projects, ensuring that the canary deployment is now serving 100% of the traffic. Call this tool when you need to finalize a rolling release deployment. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_identifierstringOptionalThe project ID or URL-encoded project name in Vercel. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier for the team on whose behalf the request is performed. Only used when mode is 'execute'.
team_slugstringOptionalThe slug of the team for which the request is performed. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'completeRollingRelease'.
#

VercelApi.GetAccessGroupProject

Retrieve details of a specific access group project. Use this tool to obtain information about a specific project within an access group by providing the access group identifier or name and the project ID.

Parameters

ParameterTypeReq.Description
access_group_id_or_namestringRequiredThe identifier or name of the access group for the project.
project_idstringRequiredThe unique identifier for the project within the access group. It is required to fetch the project details.
team_identifierstringOptionalThe identifier of the team to perform the request on behalf of. This should be a string representing the team's unique ID.
team_slugstringOptionalThe Team slug to perform the request on behalf of. Provide the specific slug associated with the team.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'readAccessGroupProject'.
#

VercelApi.GetActiveAttackStatus

Retrieve active attack data from the Vercel firewall. Use this tool to obtain information about any active attacks detected by Vercel's firewall within the specified number of days.

Parameters

ParameterTypeReq.Description
project_idstringRequiredThe unique identifier of the project to retrieve attack data for.
active_days_sincenumberOptionalNumber of days in the past to look for active attack data. Defaults to 1 day if not specified.
team_identifierstringOptionalThe unique identifier of the team to perform the request on behalf of.
team_slugstringOptionalThe slug of the team to perform the request on behalf of. This identifies which team to target for the retrieval of attack data within Vercel's system.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getActiveAttackStatus'.
#

VercelApi.GetAuthenticatedUserInfo

Retrieve current authenticated user's information. Use this tool to obtain details about the currently authenticated user from Vercel.

Parameters

No parameters required.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getAuthUser'.
#

VercelApi.GetCustomProjectEnvironments

Retrieve custom environments for a specified project. Use this tool to get custom environments of a project on Vercel. These environments cannot be named 'Production' or 'Preview'.

Parameters

ParameterTypeReq.Description
project_id_or_namestringRequiredThe unique identifier or name of the project to retrieve custom environments.
git_branch_namestringOptionalSpecify the git branch to fetch custom environments from. This identifies the branch to retrieve environments for.
team_identifierstringOptionalThe identifier for the Team to perform the request on behalf of. Expected as a string.
team_slugstringOptionalThe slug of the team to perform the request on behalf of. This identifies the specific team related to the project.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint ''.
#

VercelApi.GetDeploymentAliases

Fetch aliases for a specific deployment by ID. Retrieves all aliases associated with a given deployment ID. Use this to find or verify domain aliases linked to a specific Vercel deployment.

Parameters

ParameterTypeReq.Description
deployment_idstringRequiredThe ID of the deployment for which to list the aliases.
team_identifierstringOptionalThe identifier of the team to perform the request on behalf of. It is required to retrieve deployment aliases.
team_slugstringOptionalThe slug representing the team on whose behalf the request is made.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'listDeploymentAliases'.
#

VercelApi.GetDeploymentCheckDetails

Retrieve details for a specific deployment check. This tool is used to obtain detailed information about a single check within a specified deployment. Use it when you need insights or results from a specific deployment check.

Parameters

ParameterTypeReq.Description
check_identifierstringRequiredThe unique identifier of the check to fetch details for.
deployment_idstringRequiredThe ID of the deployment for which the check details are required.
team_idstringOptionalThe identifier for the team on whose behalf the request is performed.
team_slugstringOptionalThe slug identifier for the team to perform the request on behalf of. It uniquely represents the team within the system.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getCheck'.
#

VercelApi.GetDeploymentInfo

Retrieve deployment information by ID or URL. Use this tool to get details about a Vercel deployment using either its ID or URL. This is useful for obtaining deployment specifics, especially when the user or team owns the deployment.

Parameters

ParameterTypeReq.Description
deployment_id_or_urlstringRequiredThe unique identifier or hostname of the deployment to retrieve details for.
include_git_repo_informationstringOptionalSet to 'true' to include Git repository details or 'false' to exclude them.
team_identifierstringOptionalThe unique identifier for the team on whose behalf the request is made.
team_slugstringOptionalThe Team slug for performing the request on behalf of that team.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getDeployment'.
#

VercelApi.GetDeploymentRuntimeLogs

Get logs for a specific deployment's runtime. Use this tool to retrieve a stream of runtime logs for a given deployment in a project. This is useful for monitoring and debugging deployment processes.

Parameters

ParameterTypeReq.Description
deployment_idstringRequiredThe unique identifier for the deployment whose runtime logs are to be retrieved.
project_idstringRequiredThe unique identifier for the project related to the deployment. This is necessary to retrieve the correct runtime logs.
team_identifierstringOptionalThe unique identifier for the team to make the request on behalf of.
team_slugstringOptionalThe unique slug representing the team on whose behalf the request is made.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getRuntimeLogs'.
#

VercelApi.GetDnsRecords

Retrieve DNS records for a specified domain name. This tool fetches DNS records for a given domain. It returns up to 20 records by default, with additional records available through pagination.

Parameters

ParameterTypeReq.Description
domain_namestringRequiredThe domain name for which to retrieve DNS records. Must be a valid domain.
maximum_records_to_liststringOptionalSpecify the maximum number of DNS records to retrieve in a single request.
records_created_after_timestampstringOptionalGet records created after this specified JavaScript timestamp. It filters DNS records based on the creation date.
team_identifierstringOptionalThe identifier of the team to perform the request on behalf of.
team_slugstringOptionalThe slug representing the team on whose behalf the request is made.
until_timestampstringOptionalRetrieve records created before the specified JavaScript timestamp.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getRecords'.
#

VercelApi.GetDomainAuthCode

Retrieve the auth code for transferring a domain from Vercel. This tool is used to obtain the auth code needed to transfer a domain from Vercel to another registrar. It should be called when a domain transfer from Vercel is intended.

Parameters

ParameterTypeReq.Description
domain_namestringRequiredThe domain name for which the auth code is being requested. It should be a valid domain registered with Vercel.
team_idstringOptionalThe ID representing the Vercel team associated with the domain. Required for accessing team-specific domains.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getDomainAuthCode'.
#

VercelApi.GetDomainConfiguration

Retrieve configuration details for a specific domain. This tool calls the Vercel API to get the configuration settings for a given domain. It should be used when you need insights into the current setup or settings of a domain on Vercel.

Parameters

ParameterTypeReq.Description
domain_namestringRequiredThe name of the domain to retrieve configuration details for.
include_only_assigned_nameserversstringOptionalWhen true, only nameservers assigned directly to the domain are included. When false, parent zone nameservers are included if no direct assignment exists.
project_id_or_namestringOptionalThe project ID or name associated with the domain, used if not yet linked to a project.
team_identifierstringOptionalThe identifier for the team to perform the request on behalf of. It specifies which team's context to use when fetching domain configurations.
team_slugstringOptionalThe Team slug used to perform the request on behalf of a specific team.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getDomainConfig'.
#

VercelApi.GetDomainContactInfoSchema

Retrieve the schema for TLD-specific contact information. Use this tool to get the necessary contact information schema required by specific TLDs for a domain. This is helpful when additional TLD-specific details are needed for domain registration or management.

Parameters

ParameterTypeReq.Description
domain_namestringRequiredThe domain name for which to retrieve the TLD-specific contact information schema.
team_idstringOptionalA unique identifier for the team within Vercel. Required to retrieve domain-specific contact info.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getContactInfoSchema'.
#

VercelApi.GetDomainInfo

Retrieve information on a single domain from Vercel. Use this tool to get detailed information about a specific domain associated with a Vercel account or team. This can be useful for managing domains or checking their configuration.

Parameters

ParameterTypeReq.Description
domain_namestringRequiredThe name of the domain to retrieve information for.
team_identifierstringOptionalThe identifier for the team to perform the request on behalf of. Typically a unique string.
team_slugstringOptionalThe slug identifier for the team on behalf of whom the request is made. It uniquely identifies the team in Vercel.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getDomain'.
#

VercelApi.GetDomainOrderInfo

Retrieve information about a domain order by its ID. Use this tool to get detailed information about a specific domain order using its unique ID. It is useful for checking the status and details of a domain order processed through the registrar.

Parameters

ParameterTypeReq.Description
order_idstringRequiredThe unique ID of the domain order to retrieve information about.
team_idstringOptionalThe ID of the team associated with the domain order. This identifies the specific team within Vercel that the domain order belongs to.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getOrder'.
#

VercelApi.GetDomainPrice

Retrieve domain price and purchase period details. Use this tool to obtain the cost of purchasing a specific domain and the duration of a single purchase period, replacing the deprecated endpoint for domain price checking.

Parameters

ParameterTypeReq.Description
domain_namestringRequiredThe domain name to check the purchase price for.
domain_status_for_pricingstringOptionalSpecifies the domain status ('new', 'renewal', 'transfer', 'redemption') to check the price for.
team_identifierstringOptionalThe Team identifier for executing the request on behalf of a specific team. This is usually a unique string assigned to the team.
team_slug_for_requeststringOptionalThe slug identifier of the team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'checkDomainPrice'.
#

VercelApi.GetEdgeConfig

Retrieve Edge Config details from Vercel. Use this tool to obtain configuration details for a specific Edge Config in Vercel. It should be called when you need to access or review settings for an Edge Config using its unique identifier.

Parameters

ParameterTypeReq.Description
edge_config_idstringRequiredThe unique identifier for the Edge Config to retrieve details from Vercel.
team_identifierstringOptionalThe unique identifier for the team to perform the request on behalf of in Vercel.
team_slugstringOptionalThe slug of the team to perform the request on behalf of in Vercel. This identifier is needed to specify which team's settings are being accessed.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getEdgeConfig'.
#

VercelApi.GetEdgeConfigBackups

Retrieve backups of an Edge Config. This tool retrieves and returns backups for a specified Edge Config. It should be called when there is a need to access or review past configurations of an Edge Config managed by Vercel.

Parameters

ParameterTypeReq.Description
edge_config_idstringRequiredThe unique identifier for the Edge Config whose backups you want to retrieve.
backup_limitnumberOptionalThe maximum number of Edge Config backups to return. This is useful for paginating results.
include_metadatastringOptionalIndicate if metadata should be included in the response. Use 'true' to include.
next_page_tokenstringOptionalA token for fetching the next page of results if pagination is needed.
team_identifierstringOptionalThe identifier for the team on whose behalf the request is made.
team_slugstringOptionalThe team slug to perform the request on behalf of. It identifies the specific team in Vercel.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getEdgeConfigBackups'.
#

VercelApi.GetEdgeConfigItem

Retrieve a specific Edge Config Item by its identifiers. Use this tool to get details of a specific Edge Config Item using its configuration ID and item key.

Parameters

ParameterTypeReq.Description
edge_config_idstringRequiredThe ID of the Edge Config to retrieve a specific item from.
edge_config_item_keystringRequiredThe key of the specific Edge Config Item to retrieve.
team_identifierstringOptionalThe ID of the team to perform the request on behalf of.
team_slugstringOptionalThe slug of the team for which the Edge Config Item is requested.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getEdgeConfigItem'.
#

VercelApi.GetEdgeConfigItems

Retrieve all items from an Edge Config. Call this tool to obtain all items within a specified Edge Config by providing the Edge Config ID. Useful for accessing configuration details stored in Vercel's Edge Config.

Parameters

ParameterTypeReq.Description
edge_config_idstringRequiredThe ID of the Edge Config to retrieve items from. This is required to specify which Edge Config data to access.
team_identifierstringOptionalThe Team identifier to perform the request for a specific Vercel team.
team_slugstringOptionalThe slug representing the team on whose behalf the request is made. Each team has a unique slug identifier.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getEdgeConfigItems'.
#

VercelApi.GetEdgeConfigs

Fetch all Edge Configs from Vercel's service. Use this tool to retrieve a comprehensive list of all Edge Configurations available in a Vercel account.

Parameters

ParameterTypeReq.Description
team_identifierstringOptionalSpecify the Team identifier for which the Edge Configs need to be fetched.
team_slugstringOptionalThe Team slug to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getEdgeConfigs'.
#

VercelApi.GetEdgeConfigSchema

Retrieve the schema of an Edge Config. This tool is used to obtain the schema details of a specific Edge Config by its ID. It should be called when there's a need to understand the structure or configuration of a given Edge Config.

Parameters

ParameterTypeReq.Description
edge_config_idstringRequiredThe identifier for the specific Edge Config to retrieve its schema. It is required to specify which configuration's schema you want to query.
team_identifierstringOptionalThe unique identifier for the team to make requests on their behalf.
team_slugstringOptionalThe slug of the team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getEdgeConfigSchema'.
#

VercelApi.GetEdgeConfigTokenInfo

Retrieve metadata about an Edge Config token. Use this tool to obtain metadata for a specific Edge Config token by providing the edgeConfigId and token. Ideal for understanding token attributes and usage in Edge Config.

Parameters

ParameterTypeReq.Description
edge_config_idstringRequiredThe identifier for the Edge Config to retrieve metadata for. This is required to specify which configuration token's information is needed.
edge_config_tokenstringRequiredThe token used to obtain metadata for a specific Edge Config.
team_identifierstringOptionalThe identifier of the team to perform the request on behalf of.
team_slugstringOptionalThe Team slug for performing the request on behalf of a specific team.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getEdgeConfigToken'.
#

VercelApi.GetEdgeConfigTokens

Retrieve all tokens of a specific Edge Config. This tool retrieves all tokens related to a specified Edge Config. It should be called when you need to access or manage tokens for an Edge Config identified by its edgeConfigId.

Parameters

ParameterTypeReq.Description
edge_config_idstringRequiredA string representing the unique identifier of the Edge Config to retrieve tokens for. This ID is necessary to specify which Edge Config's tokens are being accessed.
team_identifierstringOptionalThe ID of the team to perform the request on behalf of. It identifies which team's Edge Config tokens to retrieve.
team_slugstringOptionalSlug of the team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getEdgeConfigTokens'.
#

VercelApi.GetFirewallConfig

Retrieve the active firewall configuration for a project. This tool is used to obtain the active firewall configuration for a specific project by retrieving the specified version of the configuration.

Parameters

ParameterTypeReq.Description
firewall_configuration_versionstringRequiredThe deployed version of the firewall configuration to retrieve.
project_idstringRequiredThe unique identifier for the project whose firewall configuration is being retrieved.
team_identifierstringOptionalThe identifier for the team to perform the request on behalf of.
team_slugstringOptionalThe team slug to perform the request on behalf of. It identifies the specific team by its slug name.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getFirewallConfig'.
#

VercelApi.GetIntegrationConfiguration

Retrieve configuration details by ID. Use this tool to fetch the configuration details using a specific ID. The authenticated user or team must own the configuration to access it.

Parameters

ParameterTypeReq.Description
configuration_idstringRequiredID of the configuration to retrieve. The user or team must own this configuration.
team_identifierstringOptionalThe identifier for the team on whose behalf the request is made.
team_slugstringOptionalThe unique team slug to perform the request on behalf of a specific team.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getConfiguration'.
#

VercelApi.GetIntegrationResources

Retrieve all resources for a given installation ID. Use this tool to get all resources associated with a specific integration installation. It requires the installation ID to fetch the relevant information.

Parameters

ParameterTypeReq.Description
installation_idstringRequiredThe unique identifier of the integration installation to fetch resources for.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'get-integration-resources'.
#

VercelApi.GetInvoiceDetails

Retrieve invoice details and status by ID. This tool retrieves the details and status of an invoice using its ID. Use this when you need specific information about a particular invoice, such as its current status or other details.

Parameters

ParameterTypeReq.Description
integration_configuration_idstringRequiredThe unique identifier for the integration configuration. Required to specify the configuration context for the invoice retrieval.
invoice_idstringRequiredThe unique identifier of the invoice to retrieve details and status for.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'get-invoice'.
#

VercelApi.GetLastPromoteAliasesStatus

Retrieve aliases and their mapping status from last promote request. Call this tool to obtain a list of aliases related to the most recent promote request, along with their current mapping status for a specified project.

Parameters

ParameterTypeReq.Description
project_idstringRequiredSpecify the Project ID to filter the promote aliases related to that specific project.
aliases_created_before_timestampnumberOptionalGet aliases created before this epoch timestamp.
filter_failed_aliasesbooleanOptionalSet to true to filter results to only include aliases that failed to map to the requested deployment.
get_aliases_created_after_epochnumberOptionalGet aliases created after the specified epoch timestamp.
max_aliases_to_listnumberOptionalSpecify the maximum number of aliases to list from the request. The maximum allowed is 100.
team_identifierstringOptionalThe Team identifier to perform the request on behalf of. Must be a string.
team_slugstringOptionalThe slug representing the team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'listPromoteAliases'.
#

VercelApi.GetMemberRoleInfo

Retrieve member role and details for a specific member ID. Use this tool to get the role and additional information for a member using their member ID. It is useful for verifying membership details and roles within installations.

Parameters

ParameterTypeReq.Description
integration_configuration_idstringRequiredA unique identifier for the integration configuration. Required to specify which integration to retrieve member details from.
member_idstringRequiredThe ID of the member to retrieve role and details for. This corresponds to the "user_id" claim in the SSO OIDC token.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'get-member'.
#

VercelApi.GetProjectEnvironmentVariables

Retrieve environment variables for a specified project. Use this tool to get the environment variables associated with a project by providing its `id` or `name`. Useful for managing and configuring project settings.

Parameters

ParameterTypeReq.Description
project_id_or_namestringRequiredThe unique identifier or name of the project to retrieve environment variables for.
caller_sourcestringOptionalSpecify the source making the API call.
custom_environment_idstringOptionalThe unique custom environment identifier within the project. Use this to specify a specific custom environment.
custom_environment_slugstringOptionalThe custom environment slug (name) within the project to filter specific settings.
decrypt_valuesstringOptionalSet to 'true' to decrypt environment variable values. Use 'false' to keep them encrypted.
filter_by_git_branchstringOptionalSpecify the git branch to filter the environment variable results. Must have target set to 'preview'.
team_identifierstringOptionalThe unique identifier of the team to perform the request on behalf of.
team_slugstringOptionalThe Team slug to perform the request on behalf of. Use this to specify the team context for the request.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'filterProjectEnvs'.
#

VercelApi.GetProjectInfo

Retrieve specific project details using project ID or name. This tool retrieves information about a specific project by using the project ID or name. It's useful for accessing project details from Vercel.

Parameters

ParameterTypeReq.Description
project_identifier_or_namestringRequiredThe unique project identifier or the project name to retrieve details.
team_identifierstringOptionalThe unique identifier for the team to perform the request on behalf of.
team_slugstringOptionalThe unique slug representing the team on whose behalf the request is performed.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getProject'.
#

VercelApi.GetRegisteredDomains

Retrieve a list of registered domains for the user or team. This tool fetches a list of domains registered under the authenticated user or team from Vercel. It is useful for managing or reviewing domain configurations.

Parameters

ParameterTypeReq.Description
domains_created_since_timestampnumberOptionalGet domains created after the specified JavaScript timestamp.
maximum_domains_to_listnumberOptionalThe maximum number of domains to include in the list returned by the request.
team_idstringOptionalThe unique Team identifier to retrieve domains for a specific team instead of the authenticated user.
team_slugstringOptionalThe team slug used to perform the request on behalf of a specific team.
until_timestampnumberOptionalFetch domains created before this JavaScript timestamp.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getDomains'.
#

VercelApi.GetRollingRelease

Retrieve the rolling release for a specific project. Use this tool to get details about a project's rolling release, including its current status (active, aborted, or completed). Useful when monitoring or managing project deployments.

Parameters

ParameterTypeReq.Description
project_id_or_namestringRequiredThe project ID or URL-encoded project name to identify the specific project.
filter_by_release_statestringOptionalFilter the rolling release by its state: ACTIVE, COMPLETE, or ABORTED.
team_identifierstringOptionalThe unique identifier of the team on whose behalf the request is made.
team_slugstringOptionalThe slug that identifies the team on whose behalf the request is made. This is required for team-specific data access.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getRollingRelease'.
#

VercelApi.GetRollingReleaseBillingStatus

Get the billing status for a project's rolling releases. This tool retrieves the billing status for a specific project's rolling releases from Vercel. It determines if the project is eligible for configuration under rolling releases based on the team's billing status.

Parameters

ParameterTypeReq.Description
project_id_or_namestringRequiredProject ID or name, URL-encoded, to identify the project for which to retrieve billing status.
team_identifierstringOptionalThe identifier for the team to perform the request on behalf of.
team_slugstringOptionalThe slug representation of the team to perform the request for. Used to specify which team's billing status is being queried.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getRollingReleaseBillingStatus'.
#

VercelApi.GetRollingReleaseConfig

Fetch the rolling releases configuration for a project. Use this tool to obtain the template configuration for future rolling releases in a given project on Vercel. It does not provide settings for already active releases.

Parameters

ParameterTypeReq.Description
project_identifierstringRequiredThe project ID or name, URL-encoded, to identify the project for the configuration request.
team_identifierstringOptionalThe unique identifier for the Team on whose behalf the request is made.
team_slugstringOptionalThe slug representing the team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getRollingReleaseConfig'.
#

VercelApi.GetSupportedTlds

Retrieve a list of TLDs supported by Vercel. This tool provides a list of Top-Level Domains (TLDs) that are supported by Vercel. Use this tool to find out which TLDs can be managed or registered through Vercel's platform.

Parameters

ParameterTypeReq.Description
team_idstringOptionalThe ID of the team for which to retrieve supported TLDs.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getSupportedTlds'.
#

VercelApi.GetTeamInfo

Retrieve information for a specified team using teamId. Use this tool to get detailed information about a team by specifying the teamId. It retrieves the data related to the team, which can include various details pertinent to the team specified.

Parameters

ParameterTypeReq.Description
team_identifierstringRequiredThe unique identifier for the team to retrieve information about.
team_slugstringOptionalA string representing the unique slug of the team. Used to specify which team's data to retrieve.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getTeam'.
#

VercelApi.GetTeamMembers

Retrieve a list of team members for a specified team. Use this tool to get a paginated list of members belonging to a specific team by providing the team ID.

Parameters

ParameterTypeReq.Description
added_since_timestampnumberOptionalInclude team members added since this timestamp in milliseconds.
exclude_project_idstringOptionalExclude members belonging to the specified project using the project ID.
filter_by_team_rolestringOptionalReturn members with the specified team role. Valid roles include OWNER, MEMBER, DEVELOPER, SECURITY, BILLING, VIEWER, VIEWER_FOR_PLUS, and CONTRIBUTOR.
include_members_untilnumberOptionalTimestamp in milliseconds to include members added until this time.
member_limitnumberOptionalSpecify the maximum number of team members to return in a single request.
project_id_for_eligible_membersstringOptionalInclude team members eligible for the specified project by providing the project ID.
search_team_membersstringOptionalSearch for team members by their name, username, or email.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getTeamMembers'.
#

VercelApi.GetTldPrice

Retrieve base price for a specific TLD. Use this tool to get the base price for a top-level domain (TLD). It does not account for premium domain pricing. For specific domain prices, refer to a different endpoint.

Parameters

ParameterTypeReq.Description
top_level_domainstringRequiredThe top-level domain (TLD) for which to retrieve the base price. Examples include 'com', 'net', 'org'.
registration_yearsstringOptionalThe number of years for which the TLD registration price should be calculated. Provide this as an integer representing the duration in years.
team_idstringOptionalThe ID of the team for which the TLD price data is requested.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getTldPrice'.
#

VercelApi.GetUserTeams

Retrieve all teams for the authenticated user. Call this tool to get a list of all teams the authenticated user is a member of, with pagination support.

Parameters

ParameterTypeReq.Description
max_number_of_teamsnumberOptionalMaximum number of teams to return in the response.
teams_created_since_timestampnumberOptionalTimestamp in milliseconds to include only teams created since this time.
teams_created_untilnumberOptionalTimestamp in milliseconds to filter Teams created until the specified time.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getTeams'.
#

VercelApi.GetVercelDeploymentFiles

Retrieve the file structure of a Vercel deployment. Use this tool to get the file structure of a Vercel deployment by providing the unique deployment identifier. Useful for analyzing the contents and structure of deployed source code.

Parameters

ParameterTypeReq.Description
deployment_identifierstringRequiredThe unique identifier for the deployment to retrieve its file structure.
team_identifierstringOptionalThe identifier of the team on whose behalf the request is made.
team_slugstringOptionalThe slug of the team performing the request. It is required for team-scoped requests.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'listDeploymentFiles'.
#

VercelApi.GetWebhook

Retrieve details of a specific webhook using its ID. Use this tool to obtain information about a specific webhook by providing its ID. It should be called when details are needed for a webhook managed by Vercel.

Parameters

ParameterTypeReq.Description
webhook_idstringRequiredThe unique identifier of the webhook to retrieve details for.
team_identifierstringOptionalThe identifier of the team on whose behalf the request is made. Required to specify the team context.
team_slugstringOptionalThe slug representing the team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getWebhook'.
#

VercelApi.ImportResourceToVercel

Import or synchronize a resource to Vercel. This tool is used to import or update a resource in Vercel's installation. It should be called when resources created externally need to be synchronized with Vercel. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
integration_configuration_idstringOptionalThe unique identifier for the integration configuration in Vercel. Required to specify which configuration to use when importing the resource. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
resource_identifierstringOptionalThe unique identifier for the resource to be imported or synchronized with Vercel. This ID is used to match the resource between the partner's system and Vercel's system. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'import-resource'.
#

VercelApi.InitiateProjectTransfer

Initiate a project transfer request between teams. This tool initiates a project transfer request from one team to another on Vercel. It returns a code valid for 24 hours, which can be used to accept the transfer via a specified endpoint or claim URL.

Parameters

ParameterTypeReq.Description
project_id_or_namestringRequiredThe ID or name of the project to transfer between teams.
team_identifierstringOptionalThe unique identifier of the team initiating the project transfer.
team_slugstringOptionalThe Team slug to perform the project transfer request on behalf of. This is a unique identifier for the team on Vercel.
webhook_callback_urlstringOptionalThe URL to send a webhook to when the project transfer is accepted.
webhook_signing_secretstringOptionalThe secret key used to sign the webhook payload with HMAC-SHA256 for security verification.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'createProjectTransferRequest'.
#

VercelApi.InitiateUserDeletion

Initiates user deletion and sends a confirmation email. Use this tool to start the deletion process for a user by emailing a confirmation link. The user has to follow the link to complete the deletion. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'requestDelete'.
#

VercelApi.InvalidateAuthToken

Invalidate an authentication token to revoke access. This tool is used to invalidate an authentication token, ensuring it is no longer valid for any future HTTP requests. Call this tool when you need to revoke access granted by a specific token.

Parameters

ParameterTypeReq.Description
token_idstringRequiredThe ID of the token to invalidate. Use 'current' to invalidate the token used for this request.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteAuthToken'.
#

VercelApi.InvalidateCacheByTags

Mark cache tags as stale for revalidation in the background. Use this tool to mark specific cache tags as stale, prompting them to be revalidated during the next request. This is useful when data associated with these tags has changed and needs refreshing. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_id_or_namestringOptionalSpecify the project ID or name for which the cache tags should be marked as stale. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_idstringOptionalThe Team identifier to execute the request for. Provide the team's unique ID. Only used when mode is 'execute'.
team_slugstringOptionalThe identifier (slug) for the team to perform the request on their behalf. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'invalidateByTags'.
#

VercelApi.InviteUserToTeam

Invite a user to join a Vercel team. This tool invites a user to join a specified Vercel team. The user issuing the command must be an OWNER of the team. Specify the user with an email or ID; ID takes precedence if both are provided. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
team_idstringOptionalThe unique identifier for the Vercel team to which the user is being invited. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'inviteUserToTeam'.
#

VercelApi.IssueVercelCertificate

Request a new SSL certificate from Vercel. This tool is used to issue a new SSL certificate through Vercel's API. It's called when you need to obtain a certificate for secure communication with your Vercel-hosted applications.

Parameters

ParameterTypeReq.Description
common_names_for_certificatearray<string>OptionalList of common names (domains) that the SSL certificate should be issued for.
team_idstringOptionalThe identifier for the Vercel team on whose behalf the certificate request is made.
team_slugstringOptionalThe team slug identifier for cert request on behalf of a specific team.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'issueCert'.
#

VercelApi.JoinVercelTeam

Join a Vercel team using invite code or team ID. This tool allows a user to join a Vercel team by providing an invite code or team ID. It should be called when a user wants to become a member of a specified team on Vercel.

Parameters

ParameterTypeReq.Description
team_idstringRequiredThe unique ID of the Vercel team to join. Use this if you have the team ID instead of an invite code.
team_invite_codestringOptionalThe invite code used to join a specific Vercel team. This is a string value provided to new members for team access.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'joinTeam'.
#

VercelApi.ListAccessGroupMembers

Retrieve members of a specific access group. This tool calls the API to list all members within a specified access group. Use it to retrieve member information for management or review purposes.

Parameters

ParameterTypeReq.Description
access_group_id_or_namestringRequiredSpecify the ID or name of the access group to list its members.
continuation_cursor_for_pagingstringOptionalCursor used to retrieve the next page of access group members.
member_limitintegerOptionalSpecify the maximum number of access group members to return.
member_search_querystringOptionalSearch for members using their name, username, or email.
team_identifierstringOptionalThe Team identifier for which to list access group members.
team_slugstringOptionalThe unique slug of the team for which you want to list access group members.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'listAccessGroupMembers'.
#

VercelApi.ListAccessGroupProjects

Retrieve a list of projects for a given access group. This tool should be called to obtain a list of projects associated with a specific access group by providing the group ID or name.

Parameters

ParameterTypeReq.Description
access_group_identifierstringRequiredThe ID or name of the Access Group to list its projects.
continuation_cursorstringOptionalThe continuation cursor used to retrieve the next page of results in a paginated response.
max_project_countintegerOptionalMaximum number of access group projects to return. Must be an integer.
team_identifierstringOptionalThe unique identifier for the team to perform the request on behalf of. This specifies which team's access group projects to list.
team_slugstringOptionalThe slug of the team to perform the request on behalf of. Specify to filter projects by team.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'listAccessGroupProjects'.
#

VercelApi.ListAccessGroups

Retrieve a list of access groups within Vercel. Use this tool to obtain a detailed list of all access groups available in your Vercel account.

Parameters

ParameterTypeReq.Description
access_groups_limitintegerOptionalSpecify the maximum number of access groups to be returned in the response.
continuation_cursor_for_next_pagestringOptionalA string to retrieve the next page of results using a continuation cursor.
max_projects_in_responseintegerOptionalSpecify the maximum number of projects to include in the response list.
members_inclusion_limitintegerOptionalSpecify the number of members to include in the response.
project_idstringOptionalFilter access groups by the specified project ID in Vercel.
search_access_groups_by_namestringOptionalProvide a name or keyword to search for specific access groups.
team_identifierstringOptionalThe ID of the team for which to list access groups. Specify this to perform the request on behalf of a specific team.
team_slugstringOptionalA string representing the Team slug to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'listAccessGroups'.
#

VercelApi.ListAliases

Retrieve a list of Vercel aliases for a user or team. This tool retrieves a list of aliases for the authenticated Vercel user or team. Optionally, it can filter aliases by a specific domain or project.

Parameters

ParameterTypeReq.Description
aliases_created_after_timestampnumberOptionalGet aliases created after this JavaScript timestamp. Use a timestamp in milliseconds since the epoch.
created_after_timestampnumberOptionalReturn aliases created after this UNIX timestamp.
filter_by_domainstringOptionalReturn only aliases associated with the specified domain name.
get_aliases_before_timestampnumberOptionalRetrieve aliases created before the specified JavaScript timestamp.
maximum_aliases_to_listnumberOptionalSpecifies the maximum number of aliases to retrieve in the request.
project_id_filterstringOptionalFilter to list aliases associated with the specified project ID.
rollback_deployment_idstringOptionalSpecify the deployment ID to get aliases that would be rolled back for that deployment.
team_identifierstringOptionalThe identifier for the team to perform the request on behalf of. Use this to specify the team whose aliases should be listed.
team_slugstringOptionalThe slug identifier for the team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'listAliases'.
#

VercelApi.ListDeploymentChecks

List all checks for a specific deployment. Fetches and lists all checks created for a given deployment using its ID.

Parameters

ParameterTypeReq.Description
deployment_idstringRequiredThe ID of the deployment to retrieve checks for.
team_identifierstringOptionalThe ID of the team to perform the request for. This identifies which team's context is used.
team_slugstringOptionalThe Team slug used to perform the request. This identifies the team under which the deployment was made.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getAllChecks'.
#

VercelApi.ListIntegrationConfigurationProducts

Retrieve products for a specific integration configuration. Use this tool to list all available products for a given integration configuration. It helps discover resources that can be provisioned for integrations. The response includes product IDs, slugs, names, supported protocols, and metadata requirements.

Parameters

ParameterTypeReq.Description
integration_configuration_idstringRequiredID of the specific integration configuration to list available products for.
team_identifierstringOptionalThe Team identifier to perform the request on behalf of. It specifies which team's configuration products to list.
team_slugstringOptionalThe slug of the team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getConfigurationProducts'.
#

VercelApi.ListProjectMembers

Retrieve all members of a specified project on Vercel. Use this tool to get a list of all team members associated with a particular project in Vercel. Call it when you need to know who is involved in a given project.

Parameters

ParameterTypeReq.Description
project_id_or_namestringRequiredThe ID or name of the project to list members for.
added_since_timestampintegerOptionalTimestamp in milliseconds to include members added since this time.
end_time_timestampintegerOptionalThe timestamp in milliseconds to include project members added until this time.
member_limitintegerOptionalSpecify the maximum number of project members to return. Provide an integer value.
search_project_membersstringOptionalSearch for project members by name, username, or email.
team_identifierstringOptionalThe unique identifier of the team to perform the request on behalf of. This should be a string.
team_slugstringOptionalThe Team slug to perform the request on behalf of, identifying the specific team associated with the project.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getProjectMembers'.
#

VercelApi.ListUserEvents

Fetches a list of user-generated events on Vercel. This tool retrieves events generated by user actions on Vercel, such as logging in, creating deployments, or joining teams. If a `teamId` is provided, events related to that specific team are returned.

Parameters

ParameterTypeReq.Description
deprecated_user_idstringOptionalDeprecated. Use 'principal_id' instead. If both 'principal_id' and 'deprecated_user_id' exist, 'principal_id' will be used.
end_time_filterstringOptionalTimestamp to filter events created until this time.
event_types_filterstringOptionalComma-delimited list of event types to filter the results by.
filter_by_principal_idstringOptionalFilter events generated by a specific principal when retrieving events for a Team.
include_event_payloadstringOptionalSet to 'true' to include the 'payload' field in each event response.
include_items_since_timestampstringOptionalTimestamp to only include items created since then. Use ISO 8601 format.
maximum_items_to_returnnumberOptionalMaximum number of items that can be returned from the request.
project_ids_filterstringOptionalComma-separated list of project IDs to filter the events by.
team_identifierstringOptionalSpecify the Team ID to retrieve events related to that team.
team_slugstringOptionalThe Team slug to perform the request on behalf of. Use this to specify which team's events to retrieve.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'listUserEvents'.
#

VercelApi.ListVercelDeployments

Retrieve deployments from Vercel for a user or team. This tool fetches the list of deployments for the authenticated user or team from Vercel. It should be called when users need to view their recent deployment history. If a deployment is incomplete, the URL will be null.

Parameters

ParameterTypeReq.Description
branch_name_filterstringOptionalSpecify the branch name to filter deployments.
created_after_timestampnumberOptionalRetrieve deployments created after this Date timestamp. Defaults to current time if not specified.
deployment_namestringOptionalThe name of the deployment to filter results.
deployment_since_timestampnumberOptionalRetrieve deployments created after this JavaScript timestamp.
deployment_state_filterstringOptionalFilter deployments by their state, such as `BUILDING`, `ERROR`, `INITIALIZING`, `QUEUED`, `READY`, or `CANCELED`.
fetch_deployments_before_timestampnumberOptionalSpecify a JavaScript timestamp to retrieve deployments created before this time.
filter_by_environmentstringOptionalSpecify the environment to filter deployments (e.g., 'production', 'staging').
filter_by_project_idstringOptionalFilter deployments using a specific project ID or name.
filter_by_project_idsarray<string>OptionalFilter deployments from specified project IDs. Cannot be used with the 'filter_by_project_id' argument.
filter_by_rollback_candidacybooleanOptionalSet to true to filter and include only rollback candidate deployments.
filter_by_shastringOptionalFilter deployments based on the specific SHA value.
get_deployments_before_timestampnumberOptionalA timestamp to get deployments created before a specific date. Useful for filtering older deployments. Defaults to the current time if not specified.
maximum_deployments_to_listnumberOptionalSets the maximum number of deployments to retrieve in one request.
team_identifierstringOptionalThe identifier for the team to perform the request on behalf of. Use when filtering deployments by team.
team_slugstringOptionalThe team slug to perform the request on behalf of. Specify which team's deployments to retrieve.
user_filterstringOptionalFilter deployments by the user who created them. Provide a username or user ID.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getDeployments'.
#

VercelApi.ListVercelWebhooks

Retrieve a list of webhooks from Vercel. This tool is used to get all the webhooks associated with a Vercel account. Use this to monitor or manage integrations and callbacks configured in a Vercel environment.

Parameters

ParameterTypeReq.Description
project_idstringOptionalThe unique identifier for the project to retrieve webhooks from.
team_identifierstringOptionalThe identifier for the Vercel team to perform the request on behalf of.
team_slugstringOptionalThe slug identifier for the team to perform the request on behalf of. This is used to specify which team's webhooks you want to retrieve.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getWebhooks'.
#

VercelApi.MoveProjectDomain

Transfer a domain from one project to another. Use this tool to move a project's domain to a different project, and optionally transfer redirects associated with that domain. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_id_or_namestringOptionalProvide the unique project identifier or the project name for the domain transfer. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
project_domain_namestringOptionalThe domain name of the project to be moved to another project. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe identifier for the team on whose behalf the request is made. Only used when mode is 'execute'.
team_slugstringOptionalThe slug for the team on whose behalf the request is made. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'moveProjectDomain'.
#

VercelApi.NotifyVercelOfUpdates

Send update notifications to Vercel for installations or resources. Use this tool to notify Vercel of changes to installations or resources. Trigger 'resource.updated' events when a resource linked to Vercel is modified, such as renaming a database or suspending a resource. Trigger 'installation.updated' events when an installation's billing plan changes without Vercel's involvement. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
integration_configuration_idstringOptionalThe ID of the integration configuration. It links the notification to the specific Vercel installation or resource. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'create-event'.
#

VercelApi.PauseProject

Pause a Vercel project by its ID. Use this tool to pause a Vercel project by providing its project ID. This will disable auto-assigning custom production domains and block active Production Deployments if applicable.

Parameters

ParameterTypeReq.Description
project_idstringRequiredThe unique identifier for the Vercel project you wish to pause.
team_identifierstringOptionalThe identifier of the team to perform the request on behalf of.
team_slugstringOptionalThe Team slug to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'pauseProject'.
#

VercelApi.PromoteDeploymentToProduction

Promotes a deployment to production without rebuilding it. Use this tool to promote an existing deployment to production on Vercel. This action does not rebuild the deployment. To rebuild, use the create-deployments endpoint instead.

Parameters

ParameterTypeReq.Description
deployment_identifierstringRequiredThe ID of the deployment to be promoted to production. It should be a valid string representing the deployment ID.
project_idstringRequiredThe unique identifier of the project associated with the deployment to promote.
team_identifierstringOptionalThe unique identifier for the team on whose behalf the request is made. It should be a string value.
team_slugstringOptionalThe slug of the team to perform the promotion request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'requestPromote'.
#

VercelApi.PurchaseDomain

Facilitates the purchase of a specified domain. Call this tool to purchase a domain through Vercel's new domain acquisition endpoints. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
team_identifierstringOptionalThe unique identifier for the team to perform the domain purchase request. Only used when mode is 'execute'.
team_slugstringOptionalThe slug representing the team to perform the purchase on behalf of. This identifies the team within Vercel. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'buyDomain'.
#

VercelApi.PurchaseDomainVercel

Purchase a domain with Vercel's API. This tool allows users to purchase a single domain using Vercel's API. It should be called when a user wants to buy a domain name. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
domain_namestringOptionalThe domain name that you wish to purchase using Vercel's API. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_idstringOptionalThe unique identifier for the team under which the domain will be purchased. This is expected to be a string. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'buySingleDomain'.
#

VercelApi.PurchaseMultipleDomains

Purchase multiple domains simultaneously. Use this tool to buy several domains at once through Vercel's service. It should be called when a user wants to acquire multiple domain names in a single request. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
team_idstringOptionalThe unique identifier for the team under which the domains will be purchased. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'buyDomains'.
#

VercelApi.PushEdgeConfig

Push configuration data to Edge Config for syncing. Use this tool to push configuration data into the Edge Config when Edge Config syncing is enabled. It is used to update the relevant configurations for experimentation through Vercel. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
integration_configuration_idstringOptionalThe unique identifier for the integration configuration. Use this to specify which configuration to push to Edge Config. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
resource_identifierstringOptionalThe ID of the resource for the configuration data to be pushed. Required for identifying the target Edge Config. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint ''.
#

VercelApi.QueryArtifactsInfo

Retrieve detailed information about multiple artifacts. This tool queries detailed information about an array of artifacts. It should be called when you need specifics or insights regarding multiple artifacts from the Vercel platform.

Parameters

ParameterTypeReq.Description
artifact_hashesarray<string>RequiredAn array of artifact hashes to query information for.
team_identifierstringOptionalThe identifier of the team to perform the request on behalf of.
team_slugstringOptionalThe slug identifying the team for which the request is performed.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'artifactQuery'.
#

VercelApi.ReadAccessGroup

Retrieve details of a specific access group. Use this tool to fetch information about an access group by its ID or name. It helps in obtaining the detailed configuration and properties of the specific access group.

Parameters

ParameterTypeReq.Description
access_group_id_or_namestringRequiredThe ID or name of the access group to retrieve details for.
team_identifierstringOptionalThe identifier of the team to perform the request on behalf of.
team_slugstringOptionalThe Team slug used to perform the request on behalf of the specified team.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'readAccessGroup'.
#

VercelApi.RecordCacheEvents

Record artifacts cache usage events for Vercel. Use this tool to log cache usage events, including types 'HIT' or 'MISS', and sources 'LOCAL' or 'REMOTE'. Useful for tracking cache performance and usage. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
team_identifierstringOptionalThe Team identifier to perform the request on behalf of. Used to specify which team's cache usage events are being recorded. Only used when mode is 'execute'.
team_slugstringOptionalThe Team slug to perform the request on behalf of. It identifies the specific team within Vercel. Only used when mode is 'execute'.
ci_environmentstringOptionalThe continuous integration or delivery environment where this artifact is downloaded. Only used when mode is 'execute'.
is_interactive_shellintegerOptionalSet to 1 if the client is an interactive shell, otherwise set to 0. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'recordEvents'.
#

VercelApi.RemoveBypassRule

Removes a bypass rule from the firewall. Use this tool to remove a system bypass rule from the Vercel firewall, ensuring that specific IPs can no longer bypass the security restrictions. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_idstringOptionalThe unique identifier for the project from which to remove the bypass rule. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier for the team on whose behalf the request is made. Only used when mode is 'execute'.
team_slugstringOptionalThe Team slug indicating which team to perform the request on behalf of. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'removeBypassIp'.
#

VercelApi.RemoveCertificate

Remove a certificate from Vercel using its ID. This tool removes a specific certificate from a Vercel account identified by its ID. It should be called when you need to delete an existing certificate to manage SSL/TLS configurations.

Parameters

ParameterTypeReq.Description
certificate_idstringRequiredThe unique identifier of the certificate to remove.
team_identifierstringOptionalThe identifier for the team on whose behalf the removal request is made.
team_slugstringOptionalThe slug of the team to perform the request on behalf of in Vercel.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'removeCert'.
#

VercelApi.RemoveCustomEnvironment

Remove a specified custom environment from a project. This tool removes a custom environment from a project, excluding 'Production' or 'Preview'. Use it when you need to delete a specific environment from a Vercel project.

Parameters

ParameterTypeReq.Description
custom_environment_identifierstringRequiredThe unique identifier for the custom environment within the project to be removed.
project_identifier_or_namestringRequiredThe unique project identifier or the project name to target the environment removal.
delete_unassigned_environment_variablesbooleanOptionalDelete environment variables that are not assigned to any environments when set to true.
team_identifierstringOptionalThe identifier for the team to make the request on behalf of.
team_slugstringOptionalThe slug representing the team on whose behalf to perform the request.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'removeCustomEnvironment'.
#

VercelApi.RemoveDnsRecord

Removes an existing DNS record from a domain. Use this tool to remove a DNS record from a specified domain. Useful when you need to delete outdated or incorrect DNS entries.

Parameters

ParameterTypeReq.Description
dns_record_idstringRequiredThe unique identifier of the DNS record to be removed. Required for specifying which record to delete.
domain_namestringRequiredThe domain from which the DNS record will be removed. Provide the full domain name.
team_identifierstringOptionalThe identifier for the team on whose behalf the request is performed.
team_slugstringOptionalThe slug representing the team on whose behalf the DNS record is removed.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'removeRecord'.
#

VercelApi.RemoveProjectDomain

Removes a domain from a specified project. Use this tool to remove a domain from a Vercel project by specifying the project's ID or name along with the domain name.

Parameters

ParameterTypeReq.Description
project_domain_namestringRequiredThe domain name of the project to be removed.
project_id_or_namestringRequiredThe unique project identifier or name to specify which project's domain is to be removed.
remove_redirectsbooleanOptionalSet to true to remove all domains from the project that redirect to the domain being removed.
team_identifierstringOptionalThe identifier for the team on whose behalf the request is performed.
team_slugstringOptionalThe slug identifier of the team to perform the request on behalf of. Used to specify which team's project domain should be removed.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'removeProjectDomain'.
#

VercelApi.RemoveProjectMember

Removes a member from a specific project. This tool removes a specified member from a project. It should be used when you need to revoke a member's access to a project.

Parameters

ParameterTypeReq.Description
project_id_or_namestringRequiredThe ID or name of the project from which the member will be removed.
user_idstringRequiredThe unique user ID of the member to be removed from the project.
team_identifierstringOptionalThe identifier for the team on whose behalf the request is made. This should be a string.
team_slugstringOptionalThe slug used to identify the Team for which the request is being made.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'removeProjectMember'.
#

VercelApi.RemoveTeamMember

Remove or dismiss a team member or leave a team. This tool removes a team member from a team, dismisses a user who requested access, or allows a user to leave a team on Vercel.

Parameters

ParameterTypeReq.Description
team_idstringRequiredThe ID of the team from which to remove or dismiss a member, or leave.
user_idstringRequiredThe unique identifier of the user to be removed or dismissed from the team.
new_default_team_idstringOptionalThe ID of the team to set as the new default team for the Northstar user when removing another team member.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'removeTeamMember'.
#

VercelApi.RemoveVercelConfiguration

Delete a Vercel configuration by ID. Use this tool to remove a specific Vercel configuration and its associated resources by providing the configuration ID.

Parameters

ParameterTypeReq.Description
configuration_idstringRequiredThe unique identifier of the Vercel configuration to be deleted.
team_identifierstringOptionalThe identifier for the team on behalf of which the configuration is removed.
team_slugstringOptionalThe team slug representing the Vercel team to perform the action on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'deleteConfiguration'.
#

VercelApi.RenewDomain

Renews a domain registration through Vercel. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
domain_namestringOptionalThe domain name to be renewed, in string format. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier for the team that owns the domain. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'renewDomain'.
#

VercelApi.RequestTeamAccess

Request to join a team on Vercel. This tool allows users to request access to a specific team on Vercel as a member. The request needs to be approved by a team owner, and only 10 users can have pending requests for a team at the same time. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
team_idstringOptionalThe unique identifier of the Vercel team you want to join. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'requestAccessToTeam'.
#

VercelApi.RequestVercelInvoiceRefund

Request a refund for an invoice in Vercel. Use this tool to request a refund for an invoice created via the Submit Invoice API in Vercel. Call this when a refund is necessary. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
vercel_integration_configuration_idstringOptionalThe unique identifier for the Vercel integration configuration related to the invoice. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
invoice_idstringOptionalThe unique identifier for the invoice for which the refund is requested. This ID is obtained from the invoice creation process. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'update-invoice'.
#

VercelApi.RerequestCheck

Retries a failed deployment check. Use this tool to retry a specific deployment check that has failed. Ideal when you need to manually reinvoke a check due to a transient failure or updated conditions.

Parameters

ParameterTypeReq.Description
check_to_rerun_idstringRequiredThe ID of the check you want to rerun. This identifies the specific failed check to retry.
deployment_idstringRequiredThe ID of the deployment for which the check needs to be rerun. This specifies the which specific deployment's check is to be retried.
mark_check_as_runningbooleanOptionalMark the check as running if set to true when re-requested.
team_identifierstringOptionalThe Team identifier to perform the request on behalf of. It specifies which team's context the request should be executed in.
team_slugstringOptionalThe identifier for the team to perform the check rerequest on behalf of. Use the team's slug format.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'rerequestCheck'.
#

VercelApi.RetrieveAuthTokenMetadata

Retrieve metadata about an authentication token. This tool retrieves metadata about an authentication token for the currently authenticated user. It should be called when details about a specific token are needed, such as checking token permissions or validity.

Parameters

ParameterTypeReq.Description
authentication_token_identifierstringRequiredThe ID of the token to retrieve metadata for. Use "current" for the token that the current request is authenticated with.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getAuthToken'.
#

VercelApi.RetrieveAuthTokens

Retrieve a list of the current user's authentication tokens. Use this tool to get a list of authentication tokens for the current user. It is useful for managing and reviewing user access tokens.

Parameters

No parameters required.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'listAuthTokens'.
#

VercelApi.RetrieveBillingPlans

Retrieve billing plans for a specific integration and product. Use this tool to obtain a list of billing plans associated with a specified integration and product. It retrieves the available plans using the integration and product identifiers.

Parameters

ParameterTypeReq.Description
integration_identifier_or_slugstringRequiredThe unique identifier or slug for the integration to retrieve billing plans for. Use the specific key related to the integration.
product_id_or_slugstringRequiredThe unique identifier or slug for the product to retrieve billing plans.
additional_metadatastringOptionalOptional metadata for the request, provided as a string.
team_identifierstringOptionalThe identifier for the team to perform the request on behalf of.
team_slugstringOptionalThe unique team slug used to identify which team's context the request should be performed in.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getBillingPlans'.
#

VercelApi.RetrieveCertificateById

Retrieve a Vercel certificate using its ID. Use this tool to get information about a specific Vercel certificate by providing its ID.

Parameters

ParameterTypeReq.Description
certificate_idstringRequiredThe unique identifier of the certificate to be retrieved from Vercel.
team_identifierstringOptionalThe identifier of the team to perform the request on behalf of.
team_slugstringOptionalThe slug identifying the team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getCertById'.
#

VercelApi.RetrieveCustomEnvironment

Retrieve custom environment details for a project. Use this tool to obtain information about a custom environment in a project, excluding 'Production' or 'Preview' environments.

Parameters

ParameterTypeReq.Description
custom_environment_identifierstringRequiredThe unique identifier for a custom environment within the project, excluding 'Production' or 'Preview'.
project_identifier_or_namestringRequiredThe unique project identifier or the project's name to retrieve details for.
team_identifierstringOptionalThe unique Team identifier used to perform the request on behalf of a specified team.
team_slugstringOptionalThe Team slug used to perform the request.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getCustomEnvironment'.
#

VercelApi.RetrieveDeploymentFileContents

Retrieve the contents of a file from a Vercel deployment. Use this tool to get the content of a specific file from a Vercel deployment by providing the deployment and file identifiers. The response provides the file contents encoded in base64.

Parameters

ParameterTypeReq.Description
deployment_unique_identifierstringRequiredThe unique identifier for the deployment from which to retrieve the file.
file_identifierstringRequiredThe unique identifier for the file you want to retrieve from the deployment.
file_pathstringOptionalPath to the file to fetch, applicable only for Git-based deployments.
team_identifierstringOptionalThe identifier of the team to make the request on behalf of.
team_slugstringOptionalThe slug of the team to perform the request on behalf of. Specify which team's context to use.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getDeploymentFileContents'.
#

VercelApi.RetrieveEdgeConfigBackup

Retrieve a specific Edge Config version from backup storage. Use this tool to fetch a particular version of an Edge Config that is stored as a backup. This is helpful for accessing historical configurations or restoring previous settings.

Parameters

ParameterTypeReq.Description
edge_config_backup_version_idstringRequiredThe unique identifier for the backup version of the Edge Config to retrieve.
edge_config_idstringRequiredThe ID of the Edge Config to retrieve from backup storage.
team_identifierstringOptionalThe unique identifier of the Team to perform the request on behalf of.
team_slugstringOptionalThe team's unique slug to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getEdgeConfigBackup'.
#

VercelApi.RetrieveIntegrationConfigurations

Retrieve all configurations for an authenticated integration. Use this tool to access configurations associated with an authenticated integration on Vercel, excluding those from the authorization flow when using the `project` view.

Parameters

ParameterTypeReq.Description
configuration_view_typestringRequiredSpecify 'account' to view all configurations or 'project' to exclude configurations generated from the authorization flow.
installation_typestringOptionalSpecifies the installation type. Options are 'marketplace' or 'external'.
integration_idstringOptionalThe ID or slug of the integration to retrieve configurations for.
team_identifierstringOptionalSpecifies the Team ID to perform the request on behalf of.
team_slugstringOptionalThe Team slug to perform the request on behalf of when retrieving configurations.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getConfigurations'.
#

VercelApi.RetrieveIntegrationLogDrains

Retrieve all integration log drains for the user or team. This tool retrieves a list of all integration log drains defined for the authenticated user or team. It is especially useful when using an OAuth2 token, as the list is limited to log drains created by the authenticated integration.

Parameters

ParameterTypeReq.Description
team_identifierstringOptionalThe identifier for the Team to perform the request on behalf of.
team_slugstringOptionalThe slug of the team to perform the request on behalf of. Used to specify which team's log drains to retrieve.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getIntegrationLogDrains'.
#

VercelApi.RetrieveProjectBypassRules

Retrieve the bypass rules for a specified project. Use this tool to access the system bypass rules configured for a specific project on Vercel. It is useful for security management and monitoring of firewall settings.

Parameters

ParameterTypeReq.Description
project_idstringRequiredThe unique identifier of the project for which to retrieve bypass rules.
filter_by_domainstringOptionalSpecify the domain to filter bypass rules. This filters rules related to the given domain.
filter_by_project_scopebooleanOptionalSet to true to filter results by project-scoped rules.
filter_by_source_ipstringOptionalSpecify a source IP to filter the system bypass rules for a project.
pagination_offsetstringOptionalPagination offset, retrieving results after the specified ID.
result_limitnumberOptionalThe maximum number of rules to retrieve. Specify as a number. This is useful for controlling the volume of data returned.
team_identifierstringOptionalThe unique identifier of the team on whose behalf the request is performed.
team_slugstringOptionalThe slug representing the team to make the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getBypassIp'.
#

VercelApi.RetrieveProjectDomains

Retrieve domains linked to a specific project. Use this tool to get the domains associated with a project by providing the project's ID or name. This can help manage and review project-related domains efficiently.

Parameters

ParameterTypeReq.Description
project_id_or_namestringRequiredSpecify the unique project identifier or the project name.
created_before_timestampnumberOptionalGet domains created before this JavaScript timestamp for filtering results.
custom_environment_idstringOptionalThe unique custom environment identifier within the project.
domains_created_since_timestampnumberOptionalGet domains created after this JavaScript timestamp.
domains_sort_orderstringOptionalSort order for domains based on creation date.
filter_by_git_branchstringOptionalSpecify the branch to filter domains associated with that branch.
filter_by_redirect_targetstringOptionalSpecify the redirect target to filter domains. Useful for targeting specific redirections.
filter_by_verification_statusstringOptionalFilter domains by their verification status (e.g., verified, unverified).
filter_production_domainsstringOptionalSet to 'true' to filter only production domains; otherwise, returns all.
filter_target_domainstringOptionalSpecify 'production' or 'preview' to filter domains based on their target environment.
include_redirect_domainsstringOptionalSpecify whether to include redirect project domains. Use "true" to include (default), "false" to exclude.
max_domains_to_listnumberOptionalThe maximum number of domains to list in the response, with a maximum value of 100.
team_identifierstringOptionalThe unique identifier for the team to perform the request on behalf of.
team_slugstringOptionalThe slug representing the team on whose behalf the request is made.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getProjectDomains'.
#

VercelApi.RetrieveProjectEnvironmentVariable

Retrieve the environment variable for a given project. Call this tool to access the environment variable details for a specific project using its ID or name.

Parameters

ParameterTypeReq.Description
environment_variable_idstringRequiredThe unique ID for the environment variable to retrieve its decrypted value.
project_identifier_or_namestringRequiredThe unique identifier or name of the project to retrieve its environment variable.
team_identifierstringOptionalThe identifier for the team to perform the request on behalf of.
team_slugstringOptionalThe slug for the team to perform the request on behalf of. This identifies the team in a user-friendly way.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getProjectEnv'.
#

VercelApi.RetrieveProjectsList

Retrieve the list of user's or team's projects. This tool fetches the list of projects associated with the authenticated user or team. It supports pagination and allows filtering through query parameters.

Parameters

ParameterTypeReq.Description
exclude_repositoriesstringOptionalComma-separated list of repository names to exclude from the results.
filter_by_edge_config_idstringOptionalFilter results by connected Edge Config ID. Provide the ID as a string to retrieve projects linked to this specific config.
filter_by_edge_config_token_idstringOptionalFilter results by the connected Edge Config Token ID. Provide the specific token ID to refine project search.
filter_by_elastic_concurrencystringOptionalFilter projects by elastic concurrency status. Use '1' for enabled or '0' for disabled.
filter_by_repostringOptionalFilter the project results by the specified repository name, also used for project count.
filter_by_repository_idstringOptionalFilter the project results by specifying the Repository ID.
filter_by_static_ips_enabledstringOptionalSet to '1' to filter projects with Static IPs enabled, '0' otherwise.
include_deprecated_projectsbooleanOptionalInclude deprecated projects in the results when set to True.
max_projects_returnedstringOptionalSpecifies the maximum number of projects to return in the list.
repository_url_filterstringOptionalURL to filter projects associated with a specific repository.
require_git_fork_authorizationstringOptionalSet to '1' to require authorization for Git fork PRs before deployment, or '0' to disable.
search_by_project_namestringOptionalSearch for projects using a keyword or term in the name field.
team_identifierstringOptionalThe ID of the team to perform the request on behalf of.
team_slugstringOptionalThe team slug to perform the request on behalf of, representing a specific team within Vercel.
updated_afterstringOptionalFilter projects updated after the specified timestamp or using a continuation token.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getProjects'.
#

VercelApi.RetrieveVercelAlias

Retrieve Vercel alias information for a host name or alias ID. Use this tool to fetch alias details for a specified host name or alias ID on Vercel.

Parameters

ParameterTypeReq.Description
alias_identifierstringRequiredThe alias or alias ID of the Vercel entity to retrieve.
after_timestampnumberOptionalGet the alias only if it was created after this JavaScript timestamp (milliseconds since epoch).
created_after_timestampnumberOptionalRetrieve the alias only if it was created after the specified timestamp (in milliseconds).
created_before_timestampnumberOptionalRetrieve the alias only if it was created before this JavaScript timestamp.
project_idstringOptionalFetch the alias only if it is associated with this project ID in Vercel.
team_identifierstringOptionalThe Team identifier to perform the request on behalf of.
team_slugstringOptionalThe Team slug to perform the request on behalf of. This specifies the team context for the alias retrieval.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'getAlias'.
#

VercelApi.SetDeploymentAlias

Assigns a new alias to a Vercel deployment. Use this tool to create or update an alias for a specific Vercel deployment. If the alias is currently linked to another deployment, it will be reassigned to the specified deployment.

Parameters

ParameterTypeReq.Description
deployment_idstringRequiredThe ID of the deployment to assign the alias to. This identifier is crucial for specifying which deployment will receive the new alias.
deployment_aliasstringOptionalThe alias to assign to the specified Vercel deployment.
redirect_hostnamestringOptionalHostname to redirect the alias to, using status code 307. This will override the deployment ID from the URL.
team_identifierstringOptionalThe identifier of the team to perform the alias assignment on behalf of. Required for team-based operations.
team_slugstringOptionalThe Team slug to perform the request on behalf of. This identifies the team for the deployment operation.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'assignAlias'.
#

VercelApi.SetFirewallConfiguration

Update firewall configuration with specified rules. This tool sets or overwrites the firewall configuration with the provided rules and settings on Vercel. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_idstringOptionalThe unique identifier for the project to configure the firewall settings. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier of the team to perform the request on behalf of. Only used when mode is 'execute'.
team_slugstringOptionalThe slug representing the team for which the firewall configuration will be updated. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'putFirewallConfig'.
#

VercelApi.SubmitBillingData

Submit billing and usage data to the server. This tool should be used to send billing and usage data at least once a day, ideally once per hour, using the provided access token for authorization. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
integration_configuration_idstringOptionalA string representing the unique identifier for the integration configuration. This is required to submit billing data. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'submit-billing-data'.
#

VercelApi.SubmitInvoiceToVercel

Submit an invoice to Vercel's billing system. Use this tool to submit an invoice to Vercel, creating it in their billing system and sending it to the customer. Suitable for different billing plans at various stages of the billing period. Ensure compliance with billing limitations. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
integration_configuration_idstringOptionalThe unique ID for the Vercel integration configuration. This links the invoice submission to the correct integration setup in Vercel. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'submit-invoice'.
#

VercelApi.SubmitPrepaymentBalances

Submit prepayment balances to Vercel for billing. This tool sends prepayment balances to Vercel, which should be done at least daily, but ideally hourly. It requires the access token provided during the installation process for authorization. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
integration_configuration_idstringOptionalThe unique identifier for the integration configuration. Use the ID provided during the integration setup. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'submit-prepayment-balances'.
#

VercelApi.TransferDomainToVercel

Transfer a domain to Vercel from another registrar. Use this tool to initiate the transfer of a domain from its current registrar to Vercel. This is useful when consolidating domain management under Vercel's services. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
domain_namestringOptionalThe domain name to be transferred to Vercel. It should be a valid domain currently registered elsewhere. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier for the Vercel team requesting the domain transfer. It helps associate the domain transfer with the correct Vercel team. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'transferInDomain'.
#

VercelApi.UnpauseProject

Unpause a Vercel project using its project ID. Use this tool to unpause a Vercel project by providing its project ID. The tool confirms successful unpausing or indicates failure if the project ID is invalid.

Parameters

ParameterTypeReq.Description
project_idstringRequiredThe unique identifier for the Vercel project to be unpaused.
team_identifierstringOptionalThe identifier for the team on behalf of which the request is performed. Used to specify the target team in Vercel.
team_slugstringOptionalThe slug identifying the team to perform the request on behalf of. Required for targeting the correct team's project.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'unpauseProject'.
#

VercelApi.UpdateAccessGroup

Update metadata for an access group. Use this tool to update the metadata of a specified access group by its ID or name. This is helpful when you need to modify access controls or group settings. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
access_group_id_or_namestringOptionalThe ID or name of the access group to update. Use either the unique identifier or the group's name to specify which access group you want to modify. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier for the team on whose behalf the request is performed. Only used when mode is 'execute'.
team_slugstringOptionalThe identifier for the team, used to perform the request on its behalf. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateAccessGroup'.
#

VercelApi.UpdateAccessGroupProject

Update an access group project in Vercel. This tool allows updating the details of a specific access group project in Vercel. It should be called when modifications to an existing access group project are needed, such as changing roles or permissions.

Parameters

ParameterTypeReq.Description
access_group_id_or_namestringRequiredSpecify the access group by its ID or name to target the update.
project_idstringRequiredThe unique identifier for the project to update in the access group.
project_rolestringRequiredSpecify the project role to add to the access group. Choose from 'ADMIN', 'PROJECT_VIEWER', or 'PROJECT_DEVELOPER'.
team_identifierstringOptionalThe unique identifier for the team on whose behalf the request is made.
team_slugstringOptionalThe unique identifier for the team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateAccessGroupProject'.
#

VercelApi.UpdateApexDomain

Update or move the apex domain configuration. This tool updates or moves the apex domain configuration. It is not used for updating auto-renew or nameservers, for which separate endpoints should be used. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
apex_domain_namestringOptionalThe apex domain to update or move. Accepts a string value representing the domain name (e.g., 'example.com'). Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier for the team to perform the domain update on behalf of. This allows the request to be associated with a specific team. Only used when mode is 'execute'.
team_slugstringOptionalThe slug identifying the Team on whose behalf the request is made. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'patchDomain'.
#

VercelApi.UpdateAttackChallengeMode

Updates Attack Challenge mode setting for a project. This tool updates the Attack Challenge mode setting for a project in Vercel's security settings. Use it when you need to enable or disable the Attack Challenge mode.

Parameters

ParameterTypeReq.Description
enable_attack_challenge_modebooleanRequiredSet to true to enable Attack Challenge mode; false to disable it.
project_idstringRequiredThe unique identifier of the project to update the Attack Challenge mode for.
attack_mode_active_untilnumberOptionalThe UNIX timestamp indicating when the Attack Challenge mode should be active until. Specify this to control the duration of the mode being enabled.
team_identifierstringOptionalThe unique identifier for the team on whose behalf the request is made.
team_slugstringOptionalThe unique slug of the team on behalf of which the request is made.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateAttackChallengeMode'.
#

VercelApi.UpdateCustomEnvironment

Update a custom environment for a Vercel project. Use this tool to update a custom environment in a Vercel project. The environment should not be named 'Production' or 'Preview'. Useful for managing project-specific settings.

Parameters

ParameterTypeReq.Description
custom_environment_idstringRequiredThe unique identifier for the custom environment within the project.
project_identifier_or_namestringRequiredThe unique project identifier or project name for the custom environment.
branch_matcher_typestringOptionalSpecifies the branch matcher type: 'equals', 'startsWith', or 'endsWith'.
branch_name_patternstringOptionalSpecify a portion or full Git branch name for matching. Used to identify branches in custom environments.
custom_environment_descriptionstringOptionalOptional description of the custom environment to be updated.
custom_environment_slugstringOptionalSlug of the custom environment to update. Must not be 'Production' or 'Preview'.
team_identifierstringOptionalThe identifier of the team to perform the request on behalf of.
team_slugstringOptionalThe slug of the team to perform the update on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateCustomEnvironment'.
#

VercelApi.UpdateDnsRecord

Update an existing DNS record for a domain. This tool updates an existing DNS record for a specified domain name. It should be called when changes to a DNS record are needed, such as modifying the value or type. The tool returns details of the updated record after the operation is successful. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
dns_record_idstringOptionalThe unique identifier of the DNS record to be updated. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier of the team performing the request. Only used when mode is 'execute'.
team_slugstringOptionalThe slug representing the Team to perform the DNS update on behalf of. It is used to specify the team context for the request. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateRecord'.
#

VercelApi.UpdateDomainAutoRenew

Update the auto-renew setting for a domain. Use this tool to toggle the auto-renewal option for a specific domain. Useful for managing domain renewal preferences.

Parameters

ParameterTypeReq.Description
domain_namestringRequiredThe domain for which you want to update the auto-renew setting. It should be a valid domain name, such as 'example.com'.
enable_auto_renewbooleanRequiredSet to true to enable auto-renewal of the domain, or false to disable it.
team_idstringOptionalThe unique identifier for the team associated with the domain.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateDomainAutoRenew'.
#

VercelApi.UpdateDomainNameservers

Update the nameservers for a domain. Use this tool to change the nameservers of a domain via Vercel. An empty array can be provided to revert to Vercel's default nameservers.

Parameters

ParameterTypeReq.Description
domain_namestringRequiredThe domain name to update the nameservers for. Provide the full domain, e.g., 'example.com'.
nameservers_listarray<string>RequiredA list of nameservers to set for the domain. Pass an empty list to revert to Vercel's default nameservers.
team_idstringOptionalThe unique identifier for the team to which the domain belongs. If not provided, the default team context is used.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateDomainNameservers'.
#

VercelApi.UpdateEdgeConfig

Update an existing Edge Config to apply changes. This tool updates an existing Edge Config with new settings. It should be called when there is a need to modify the settings of an Edge Config identified by its ID.

Parameters

ParameterTypeReq.Description
edge_config_identifierstringRequiredThe unique identifier of the Edge Config to be updated. This is required to specify which configuration should be modified.
edge_config_slugstringRequiredThe unique slug identifier for the Edge Config that needs updating.
team_slugstringRequiredThe slug identifying the team on whose behalf the request is performed.
team_identifierstringOptionalThe unique identifier of the team to perform the request for. Required for updating the Edge Config on behalf of a specific team.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateEdgeConfig'.
#

VercelApi.UpdateEdgeConfigItems

Batch update Edge Config Items efficiently. Use this tool to update multiple Edge Config Items in a single request. Ideal for making bulk modifications to your Vercel Edge Configurations. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
edge_config_identifierstringOptionalThe identifier for the specific Edge Config to update in the batch request. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier of the Team on whose behalf the request is made. Only used when mode is 'execute'.
team_slugstringOptionalThe unique slug of the team to perform the request on behalf of. It identifies the team in a URL-friendly format. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'patchEdgeConfigItems'.
#

VercelApi.UpdateEdgeConfigSchema

Update an Edge Config's schema to modify its structure. Use this tool to update the schema of an Edge Config in Vercel. It is useful when changes to the structure or configuration settings of an Edge Config are needed.

Parameters

ParameterTypeReq.Description
edge_config_identifierstringRequiredThe unique identifier for the Edge Config to update its schema.
edge_config_schema_definitionstringRequiredJSON string defining the updated structure and settings of the Edge Config.
enable_dry_runstringOptionalSet to true to simulate the update without applying changes. Useful for testing.
team_identifierstringOptionalThe unique ID of the team on whose behalf the request will be made.
team_slugstringOptionalThe Team slug to perform the request on behalf of. It identifies the specific team for the operation.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'patchEdgeConfigSchema'.
#

VercelApi.UpdateExistingCheck

Updates an existing deployment check. Use this tool to update an existing check in a deployment on Vercel. Ensure that OAuth2 authentication is used to avoid errors. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
deployment_idstringOptionalThe identifier for the deployment to update the check for. Ensure it is a valid string. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
check_identifierstringOptionalThe unique identifier of the check to be updated. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe identifier of the Team to perform the request on behalf of. Only used when mode is 'execute'.
team_slugstringOptionalThe slug of the team to perform the request on behalf of. This identifies the team within Vercel. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateCheck'.
#

VercelApi.UpdateExperimentationItem

Update an existing experimentation item. Use this tool to modify the details of an existing experimentation item in a Vercel installation. It's called when you need to update specific experimentation parameters or configurations. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
integration_configuration_idstringOptionalThe ID of the integration configuration to be updated. This identifies which configuration is being patched. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
resource_identifierstringOptionalThe unique identifier of the experimentation resource to update. Provides context for which item needs modification. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
experiment_item_idstringOptionalThe unique identifier for the experimentation item to be updated. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint ''.
#

VercelApi.UpdateFirewallConfig

Modify the existing firewall config for a project. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_identifierstringOptionalThe unique identifier for the project to modify the firewall config. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier for the team to perform the request on behalf of. Only used when mode is 'execute'.
team_slugstringOptionalThe Team slug used to identify the team for the request. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateFirewallConfig'.
#

VercelApi.UpdateIntegrationDeployment

Update a deployment integration action. Use this tool to update the action of a deployment integration for a specific installation. It is ideal for modifying settings or actions related to deployment integrations. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
deployment_idstringOptionalThe unique identifier for the deployment to update. This is required to specify which deployment's integration action should be modified. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
integration_configuration_idstringOptionalThe ID of the integration configuration to update. This is required to specify which integration setup the action applies to. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
resource_idstringOptionalThe unique identifier for the resource to be updated in the deployment integration. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
deployment_actionstringOptionalSpecifies the action to be taken for the deployment integration. Expected as a descriptive string indicating the action type. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'update-integration-deployment-action'.
#

VercelApi.UpdateIntegrationInstallation

Updates an integration installation configuration. Use this tool to update the configuration of an existing integration installation. Call it when changes to the integration setup are necessary. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
integration_configuration_idstringOptionalThe ID of the integration configuration to update. This should be a string identifying the specific installation. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'update-installation'.
#

VercelApi.UpdateProjectDataCache

Update the data cache for a Vercel project. This tool updates the data cache feature on a specified Vercel project. Use it when you need to refresh or modify the data cache to ensure the project is up-to-date with the latest changes.

Parameters

ParameterTypeReq.Description
project_idstringRequiredThe unique identifier for the Vercel project to update the data cache.
disable_data_cachebooleanOptionalSet to true to disable the project's data cache, or false to enable it. Default is false.
team_identifierstringOptionalThe unique Team ID to perform the request on behalf of. Required for targeted updates.
team_slugstringOptionalThe Team slug to perform the request on behalf of. Use this to specify which team's project to update.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateProjectDataCache'.
#

VercelApi.UpdateProjectDetails

Update a project's fields using its name or ID. Use this tool to modify specific details of a Vercel project by providing its name or ID. Ideal for updating project configurations or metadata. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_id_or_namestringOptionalThe unique identifier or name of the Vercel project to be updated. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier of the team on whose behalf the request is made. Only used when mode is 'execute'.
team_slugstringOptionalThe slug of the team on whose behalf the request is made. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateProject'.
#

VercelApi.UpdateProjectDomainConfig

Update a project's domain configuration. Use this tool to update a project's domain settings, including the domain name, associated git branch, and redirect options.

Parameters

ParameterTypeReq.Description
project_domain_namestringRequiredThe project domain name to be updated. Example: 'example.com'.
project_identifier_or_namestringRequiredThe unique project identifier or the project name used to update domain configuration.
linked_git_branchstringOptionalThe Git branch to associate with the project domain.
redirect_status_codeintegerOptionalHTTP status code for the domain redirect. Acceptable values are 301, 302, 307, 308, or None if no redirect is required.
redirect_target_domainstringOptionalSpecify the target destination domain for the redirect of a project domain.
team_identifierstringOptionalThe identifier for the team to perform the request on behalf of.
team_slugstringOptionalThe slug identifier for the team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateProjectDomain'.
#

VercelApi.UpdateProjectProtectionBypass

Update the deployment protection bypass for a Vercel project. Use this tool to modify the deployment protection automation bypass settings for a specific Vercel project.

Parameters

ParameterTypeReq.Description
project_id_or_namestringRequiredThe unique Vercel project identifier or project name to update the protection bypass for.
create_new_automation_bypassbooleanOptionalCreate a new automation bypass after revoking the current secret.
optional_secret_valuestringOptionalOptional value of the secret to generate; omit for OAuth2 tokens.
revoke_automation_bypassstringOptionalSecret value of the automation bypass to be revoked for a Vercel project.
team_identifierstringOptionalThe identifier for the team to perform the request on behalf of.
team_slugstringOptionalThe slug of the team to perform the request on behalf of.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateProjectProtectionBypass'.
#

VercelApi.UpdateResource

Update an existing resource with new information. Use this tool to update details of a specific resource in an installation. Supports partial updates, allowing changes to be made without modifying the entire resource. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
integration_configuration_idstringOptionalThe unique identifier for the integration configuration to update. Required for identifying which integration configuration is being modified. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
resource_idstringOptionalThe unique identifier of the resource to be updated. This is required to specify which resource you are targeting for updates. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'update-resource'.
#

VercelApi.UpdateResourceSecrets

Updates the secrets of a specified resource. This tool updates the secrets of a specified resource and connected projects. Old secrets may still be used by existing projects until manually redeployed. Useful for resetting resource credentials. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
integration_configuration_idstringOptionalThe unique identifier for the integration configuration associated with the resource. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
integration_product_id_or_slugstringOptionalSpecify the product ID or slug to identify the integration product for the resource update. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
resource_idstringOptionalThe unique identifier for the resource whose secrets are being updated. This is required to specify which resource's secrets need modification. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'update-resource-secrets'.
#

VercelApi.UpdateRollingReleaseConfig

Update or disable rolling releases for a Vercel project. Use this tool to update or disable rolling releases for a specific Vercel project. It changes the configuration for future deployments without affecting in-progress rollouts. Disabling the feature requires additional API calls to complete or abort current rollouts.

Parameters

ParameterTypeReq.Description
project_id_or_namestringRequiredProject ID or name (URL-encoded) for updating rolling release settings.
team_identifierstringOptionalThe identifier for the team to perform the request on behalf of.
team_slugstringOptionalThe slug identifying the team for which the request is made.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateRollingReleaseConfig'.
#

VercelApi.UpdateSecretsById

Update the secrets of a Vercel resource by ID. This tool updates the secrets for a given resource in Vercel, affecting connected projects with the new secrets. Note that existing projects using old secrets require manual redeployment to apply changes. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
integration_configuration_idstringOptionalThe ID of the integration configuration. This identifies the specific configuration in Vercel to update secrets for. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
resource_idstringOptionalThe unique identifier of the Vercel resource whose secrets are to be updated. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'update-resource-secrets-by-id'.
#

VercelApi.UpdateTeamInfo

Update information of a specified team. Use this tool to modify details of an existing team by providing the team ID and the updated information. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
team_identifierstringOptionalThe unique identifier for the team whose information you want to update. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_slugstringOptionalThe unique slug for the team used to perform the request. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'patchTeam'.
#

VercelApi.UpdateTeamMember

Update a team member's role or confirm membership. This tool updates a team member's details within a specified team, such as modifying their role or confirming an unconfirmed member's request to join. It requires the authenticated user to have 'OWNER' privileges in the team. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
member_idstringOptionalThe unique identifier for the team member to update. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_idstringOptionalThe unique ID of the team where the member's role or membership status will be updated. It is required to identify the specific team. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'updateTeamMember'.
#

VercelApi.UpdateUrlProtectionBypass

Update the protection bypass for a Vercel URL. Use this tool to update the protection bypass for an alias or deployment URL in Vercel, enabling user or comment access on preview deployments. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
alias_or_deployment_idstringOptionalThe ID of the alias or deployment for which to update the protection bypass. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe unique identifier of the team on whose behalf the request is made. Only used when mode is 'execute'.
team_slugstringOptionalThe team slug representing which team the request should be performed for in Vercel. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'patchUrlProtectionBypass'.
#

VercelApi.UploadCertificate

Uploads a certificate to Vercel. Use this tool to upload a new certificate to the Vercel platform. This is needed when adding or updating SSL certificates for your domains. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
team_identifierstringOptionalThe unique identifier for the team to perform the request on behalf of. Only used when mode is 'execute'.
team_slugstringOptionalSpecify the team slug to perform the request on behalf of in Vercel. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'uploadCert'.
#

VercelApi.UploadClientCertToProject

Upload a client certificate for mTLS authentication. Use this tool to upload a client certificate to a Vercel project for mutual TLS (mTLS) authentication with external origins. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Parameters

ParameterTypeReq.Description
modestringRequiredOperation mode: 'get_request_schema' returns the OpenAPI spec for the request body, 'execute' performs the actual operation
get_request_schemaexecute
project_id_or_namestringOptionalThe unique identifier or name of the Vercel project to upload the client certificate to. This is required to specify which project the mTLS certificate should be associated with. Required when mode is 'execute', ignored when mode is 'get_request_schema'.
team_identifierstringOptionalThe string identifier of the team to perform the request on behalf of. Only used when mode is 'execute'.
team_slugstringOptionalThe slug representing the team on whose behalf the request is made. Only used when mode is 'execute'.
request_bodystringOptionalStringified JSON representing the request body. Required when mode is 'execute', ignored when mode is 'get_request_schema'

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'uploadProjectClientCert'.
#

VercelApi.VerifyProjectDomain

Verify the status of a project domain's verification challenge. This tool attempts to verify a project domain marked as `verified = false` by checking the correctness of its verification challenge. Use this to confirm domain ownership for a project.

Parameters

ParameterTypeReq.Description
project_id_or_namestringRequiredThe unique project identifier or the project name to verify the domain for.
verify_domain_namestringRequiredThe domain name you want to verify for the project.
team_identifierstringOptionalThe Team identifier to perform the request on behalf of. Provide as a string.
team_slugstringOptionalThe Team slug used to perform the verification request on behalf of a specific team.

Requirements

Secrets:VERCEL_ACCESS_TOKEN

Output

Type:json— Response from the API endpoint 'verifyProjectDomain'.
Last updated on