Vercel MCP integration for AI agents.
Connect AI agents to Vercel through 24 structured actions, including get auth user, add project domain, delete project env, and verify project domain. Review…
- ACTION CONTRACTS
- 24
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Vercel integration exposes
The Vercel Agent App exposes 24 provider-backed actions for developer tools work. Its current contract lets an authorized agent get the authenticated vercel user, add a domain to a vercel project, and delete a vercel project environment variable. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Vercel account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Vercel capabilities.
Showing 12 of 24 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_auth_userREADGet the authenticated Vercel user.
add_project_domainWRITEAdd a domain to a Vercel project.
INPUTS: teamId / slug / idOrName / name / redirect
delete_project_envHIGH IMPACTDelete a Vercel project environment variable.
INPUTS: teamId / slug / idOrName / id
verify_project_domainREVIEWVerify a Vercel project domain.
INPUTS: teamId / slug / idOrName / domain
create_projectWRITECreate a Vercel project.
INPUTS: teamId / slug / name / framework / rootDirectory
create_project_envWRITECreate a Vercel project environment variable.
INPUTS: teamId / slug / idOrName / key / value
create_webhookWRITECreate a Vercel webhook.
INPUTS: teamId / slug / url / events / projectIds
delete_webhookHIGH IMPACTDelete a Vercel webhook. The returned acknowledgement is generated locally because Vercel responds with 204 No Content.
INPUTS: teamId / slug / id
get_deploymentREADGet a Vercel deployment.
INPUTS: teamId / slug / idOrUrl / withGitRepoInfo
get_deployment_eventsREADGet Vercel deployment events.
INPUTS: teamId / slug / idOrUrl / limit / since
get_domain_configREADGet domain configuration guidance from Vercel.
INPUTS: teamId / slug / domain
get_projectREADGet a Vercel project.
INPUTS: teamId / slug / idOrName
INPUT CONTRACTS
Know what the action needs before it runs.
add_project_domain
teamIdOPTIONAL- The Team identifier to perform the request on behalf of. Provide this or slug, not both. Defaults to the team configured on the connection.
slugOPTIONAL- The Team slug to perform the request on behalf of. Provide this or teamId, not both. Defaults to the team configured on the connection.
idOrNameREQUIRED- Vercel project ID or project name.
nameREQUIRED- Domain name to add to the project.
redirectOPTIONAL- Redirect target for the domain.
delete_project_env
teamIdOPTIONAL- The Team identifier to perform the request on behalf of. Provide this or slug, not both. Defaults to the team configured on the connection.
slugOPTIONAL- The Team slug to perform the request on behalf of. Provide this or teamId, not both. Defaults to the team configured on the connection.
idOrNameREQUIRED- Vercel project ID or project name.
idREQUIRED- Vercel environment variable ID.
verify_project_domain
teamIdOPTIONAL- The Team identifier to perform the request on behalf of. Provide this or slug, not both. Defaults to the team configured on the connection.
slugOPTIONAL- The Team slug to perform the request on behalf of. Provide this or teamId, not both. Defaults to the team configured on the connection.
idOrNameREQUIRED- Vercel project ID or project name.
domainREQUIRED- Domain name.
create_project
teamIdOPTIONAL- The Team identifier to perform the request on behalf of. Provide this or slug, not both. Defaults to the team configured on the connection.
slugOPTIONAL- The Team slug to perform the request on behalf of. Provide this or teamId, not both. Defaults to the team configured on the connection.
nameREQUIRED- Vercel project name.
frameworkOPTIONAL- Framework to set on the project.
rootDirectoryOPTIONAL- Root directory for the project.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Auth User
Get the authenticated Vercel user. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_auth_userControl Add Project Domain
Add a domain to a Vercel project. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_project_domainVerify with Add Project Domain
Add a domain to a Vercel project. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
add_project_domainSAFETY BOUNDARY
Operate Vercel with explicit limits
- Authorize Vercel with API key and grant only the provider access required by the selected actions.
- 8 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_project_env` and `delete_webhook` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Vercel rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Vercel task completed successfully.
CONNECTION MODEL
API key
Vercel personal access token used with the Authorization Bearer header. Create it in your Vercel Account Tokens settings. Team-owned resources also need Team ID or Team slug.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 15
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Vercel.