Add accounts and paid features
When a feature needs sign-in, subscriptions or a store, the authentication and Marketplace guidance helps your assistant choose an integration, provision its services and connect it to your app.
Overview
The Vercel Plugin helps your coding assistant choose and use Vercel products while working on an application. Its guidance connects backend architecture, authentication, storage and AI development with deployment and ongoing operations, so the assistant can work across the services a feature needs.
The assistant can select relevant skills, and you can request specific guidance or invoke the bundled commands through your tool. Where supported, startup hooks add project context in empty folders and detected Vercel, Next.js or eve projects. Skills are not injected on every prompt or tool call by default.
The bundled Vercel MCP connection adds account operations that can read and change resources after authorization. The guidance remains useful without account access; installing the plugin alone does not establish that access.
Use Cases
Build an agent that resumes work
For an agent that needs tools, messaging channels or work that survives interruptions, the plugin helps your assistant choose an architecture and use eve, AI SDK or Workflow. The ai-architect specialist provides design guidance.
Trace a broken user journey
When a page loads but the feature fails, the verification skill guides the assistant through the browser, API, stored data and response. Tracing guidance helps investigate slow or failed server requests.
Investigate a failed release
Use deployment guidance to inspect a build, review logs and decide whether to fix, promote or roll back a deployment. The deployment-expert specialist covers release workflows, configuration and domains.
Move heavy tests off your laptop
The offload-to-sandbox skill guides the assistant through running builds, test suites or parallel experiments in Vercel Sandboxes and collecting the results. These tasks require access to a Vercel project.
Components
Skills provide instructions for your assistant; the entries below describe what each set of instructions covers. Component availability and invocation depend on the coding tool and installation method.
To select a skill manually, type a slash in Claude Code and choose its vercel-prefixed entry. Cursor, Grok Build, Copilot CLI and Antigravity use the skill's bare name after a slash. Codex uses a dollar sign followed by the skill name. VS Code's native repository plugin uses vercel-plugin followed by a colon and the skill name after a slash. Native Kimi plugins use skill:vercel-plugin: followed by the skill name after a slash; a bare name does not select a plugin skill.
The bundled commands use the vercel prefix in Claude Code and OpenCode, and vercel-plugin in native Kimi plugins. In Kimi, the command and skill named bootstrap are distinct: choose the skill-prefixed entry for guidance. Codex and Antigravity do not document a commands component; Cursor, Grok Build and Copilot CLI do not establish how these bundled commands are invoked. For an installation translated by Plugins CLI, choose the entries your tool actually lists rather than assuming the native plugin's prefix.
Skills
This plugin's skills 38What you’ll need
Showing all 38
AI apps and agents
build-agents
Start building an AI agent, with eve as the default framework.
ai-sdk
Build AI interfaces, streamed responses, generated output and tool-calling agents.
ai-gateway
Connect models through AI Gateway and manage routing, authentication and spending.
eve
Develop durable eve agents with tools, channels, schedules and frontend clients.
chat-sdk
Build bots for multiple messaging platforms from one codebase.
workflow
Build durable tasks and agents that pause, resume and retry.
The linked page covers the upstream Workflow skill. This plugin bundles a synchronized copy that can differ from an independent upstream installation.
vercel-connect
Connect apps and agents to third-party services with scoped credentials.
vercel-sandbox
Run generated or user-submitted code in isolated Linux environments.
vercel-agent
Configure Vercel Agent for chat, code review and production investigations.
App architecture and services
create-a-backend
Choose services, runtimes and storage for APIs and background workloads.
auth
Add authentication, sessions and protected routes with supported identity providers.
marketplace
Find, provision and manage third-party integrations through Vercel Marketplace.
vercel-storage
Choose and connect file storage, shared configuration, Postgres or Redis.
vercel-functions
Configure and troubleshoot server-side code running on Vercel Functions.
vercel-services
Combine frontends and backends in one Vercel project; Services is in beta.
microfrontends
Compose independently deployed frontends and manage routing between them.
routing-middleware
Intercept requests before cache for redirects, rewrites and personalization.
queues
Build background message processing with retries and delays; Vercel Queues is in beta.
daemons
Run long-lived container workers; the public beta supports production deployments only.
vercel-schedules
Schedule recurring work or one-time runs for functions, routes and queues.
vercel-flags
Plan feature flags, targeting, experiments and gradual releases across frameworks.
flags-sdk
Implement Flags SDK declarations, adapters and static variants in Next.js or SvelteKit.
Setup and releases
bootstrap
Prepare linked services, environment variables and repository startup in order.
vercel-cli
Use Vercel CLI for deployment, configuration, logs, domains and platform operations.
The linked page covers the upstream Vercel CLI skill. The plugin maintains its own synchronized copy and accompanying guidance.
env-vars
Manage environment variables, local files, secrets and OIDC tokens.
deployments-cicd
Configure deployments, release promotion, rollbacks and CI workflows.
domains
Search, register and manage domains, DNS, transfers and renewals.
access-protected-vercel-deployment
Access protected deployments from automated browsers and command-line requests.
vercel-firewall
Configure traffic filtering, rate limits, bot controls and attack response.
Testing and performance
verification
Check a complete user journey across browser, API, data and response.
offload-to-sandbox
Move heavy builds, tests and parallel experiments to remote sandboxes.
react-best-practices
Review React and Next.js code for rendering, data-fetching and bundle performance.
This plugin calls its copy react-best-practices; the upstream skill is named vercel-react-best-practices. The plugin also supplies its own skill metadata.
cdn-caching
Diagnose stale content, cache misses, revalidation and caching costs.
runtime-cache
Cache reusable results by region and invalidate entries with tags.
custom-metrics
Record application measurements; querying requires Observability Plus and team availability.
vercel-tracing
Instrument server code and investigate requests through OpenTelemetry spans.
is-agentic
Audit a public site's accessibility to agents; the score and report are public.
knowledge-update
Supply corrections and newer Vercel product guidance to the assistant.
No matching results.
Commands
4bootstrapPrepare project linking, integrations, environment settings and database or development startup.
Prepare a repository
Where your tool exposes bundled commands, select bootstrap in the repository you want to prepare. Claude Code and OpenCode use the vercel prefix; native Kimi plugins use vercel-plugin. For an installation translated by Plugins CLI, use the name shown by your tool. The instructions check Vercel CLI authentication and project linking before provisioning services or running database and development scripts.
See the bootstrap command instructions for the checks and execution order.
deployDeploy with preflight checks; defaults to preview, but a project's first deployment reaches production.
Deploy the current project
Where your tool exposes bundled commands, select deploy in your project. Claude Code and OpenCode use the vercel prefix; native Kimi plugins use vercel-plugin. For an installation translated by Plugins CLI, use the name shown by your tool. The instructions use a preview deployment by default and require explicit confirmation when you request production. A project's first deployment goes to production even without a production argument.
The command also asks the assistant to flag uncommitted files that would be uploaded. Review the deployment command instructions before deploying.
envList, download, add, remove or compare environment variables.
Manage project settings
Where your tool exposes bundled commands, select env and specify whether you want to list, pull, add, remove or compare variables. Claude Code and OpenCode use the vercel prefix; native Kimi plugins use vercel-plugin. For an installation translated by Plugins CLI, use the name shown by your tool. Identify the intended environment before changing settings.
The environment command instructions describe the supported actions and their checks.
statusInspect deployments, project configuration, domains and environment-variable counts.
Check project health
Where your tool exposes bundled commands, select status in a linked Vercel project. Claude Code and OpenCode use the vercel prefix; native Kimi plugins use vercel-plugin. For an installation translated by Plugins CLI, use the name shown by your tool. Its instructions gather diagnostics without destructive operations and report variable counts rather than secret values.
See the status command instructions for the diagnostic scope.
Agents
3ai-architect
Plan AI application architecture, model integration, agents and durable workflows.
Request architecture help
In Claude Code, ask for the ai-architect specialist. In OpenCode 2, ask your primary agent to use the ai-architect subagent. In VS Code, choose it from the Agent dropdown; in Copilot CLI, use the agent picker. Describe the feature, existing stack and constraints.
Kimi Code does not expose the bundled specialist agents. Read the ai-architect instructions for its design scope.
deployment-expert
Investigate deployment failures and plan releases, rollbacks, configuration and domains.
Request deployment help
In Claude Code, ask for deployment-expert. In OpenCode 2, ask your primary agent to use that subagent. In VS Code, choose it from the Agent dropdown; in Copilot CLI, use the agent picker. Provide the affected project, deployment and symptoms.
Kimi Code does not expose the bundled specialist agents. See the deployment-expert instructions for its troubleshooting scope.
performance-optimizer
Investigate loading speed, rendering, caching and asset delivery.
Request performance help
In Claude Code, ask for performance-optimizer. In OpenCode 2, ask your primary agent to use that subagent. In VS Code, choose it from the Agent dropdown; in Copilot CLI, use the agent picker. Identify the slow page or interaction and any measurements you have.
Kimi Code does not expose the bundled specialist agents. See the performance-optimizer instructions for the areas it investigates.
Hooks
5Check session guidance state
Runs at session start; on Claude Code, clearing or compaction does not trigger its guidance reset.
Report usage and profile the project
Reports plugin usage at session start and profiles eligible projects for relevant guidance.
Add session context
Adds Vercel context at session start in eligible projects; empty folders receive instructions to begin execution.
Report skill use
After a supported Skill-tool load, reports the bundled skill or command name.
Clean up session files
Removes the plugin's temporary session files when the session ends.
Plugin usage reporting
Reporting is enabled by default. The plugin sends events to Vercel's telemetry service that can include:
- A daily-use event, limited to once per UTC day after successful reporting.
- A first-use event for the local user profile.
- The plugin version.
- The detected coding-tool category; custom tool names are reduced to a fixed category.
- A random installation identifier. Requests also carry timestamps and random event or session identifiers.
- The name of a bundled skill or command loaded through a supported Skill tool. OpenCode reports its bundled skill loads separately; its command invocations are not counted.
Skill-load reports are not throttled like daily-use reports. They show that guidance was loaded, not that the task succeeded. Native Cursor skill loads are not observable through its hook API and are not counted.
The plugin excludes prompt text, shell commands, tool-call contents, skill arguments, file paths, project names and account IDs from its documented reports.
Disable plugin reporting
Set VERCEL_PLUGIN_TELEMETRY to off in the environment that launches your coding tool, then restart that tool. OpenCode needs its background service restarted. This disables reporting while leaving other plugin actions enabled. Plugins CLI and Vercel CLI have separate reporting controls.
These hook rows are bundled for Claude Code and load when the plugin is enabled; no manual hook-file setup is needed. Use Claude Code's hook browser to inspect registered hooks and their source. Registration does not prove execution: enable VERCEL_PLUGIN_LOG_LEVEL at debug in the launch environment to inspect plugin diagnostics. To stop the bundled hooks, disable the plugin in the plugin manager and apply the change or restart. Claude Code also documents an all-hooks control, with managed-policy exceptions; it does not support disabling one configured hook while retaining it.
Project profiling and startup context normally activate in empty folders and detected Vercel, Next.js or eve projects. The startup context in an empty folder tells the assistant to skip planning, choose defaults and start execution, including non-interactive scaffolding. Reporting can still run outside eligible projects. Turning off reporting does not disable startup instructions.
MCP servers
1vercel
Access Vercel documentation, projects, deployments and logs, including account tools that change resources.
Account tools require sign-in and access to the intended teams. Vercel accepts reviewed clients or clients using Client ID Metadata Documents (CIMD); check your tool's Install route before relying on account access. Available tools also depend on the connection and team permissions.
Install
Choose your coding tool, then an installation method. Install the plugin as a whole; Vercel account authorization is needed only for account operations.
Claude Code
Have Claude Code available on your PATH, Node.js 18 or later, Git and Bun. The Plugins CLI (npm package plugins) detects installed coding tools and can install into several of them.
Installer reporting includes the source you enter, plugin names, target tools and scope. To opt out before running it, set DO_NOT_TRACK or DISABLE_TELEMETRY to 1 in the installer's environment.
Before activating the plugin, open your project rather than an empty folder unless you want immediate scaffolding. In an empty folder, startup instructions tell the assistant to choose defaults and begin execution. Plugin reporting is also on by default; set VERCEL_PLUGIN_TELEMETRY to off in the environment that launches Claude Code to disable reporting.
- 01
Run the installer in a terminal.
npx plugins add vercel/vercel-plugin - 02
Review the detected tools, plugin and installation scope before confirming. Ensure Claude Code is included; the default scope is your user account.
- 03
Start Claude Code in your project. For a session already open, apply pending plugin changes with the reload command.
Inside Claude Code/reload-plugins - 04
Open the plugin manager's Installed tab and confirm the Vercel plugin is enabled. Open the slash menu and check for a bundled skill such as env-vars.
Claude Code is a Vercel-reviewed MCP client. Account tools still need separate authorization and access to the intended teams. The Vercel MCP guide covers direct server setup; Vercel does not document a plugin-specific sign-in procedure for this route.
Have Claude Code and Vercel CLI installed. Vercel CLI requires Node.js 20 or later. Plugin-only setup detects Claude Code and Codex, asks before installing into them and skips AI Gateway setup.
Vercel CLI reports usage, including commands, arguments and account identifiers. To disable reporting for this run, set VERCEL_TELEMETRY_DISABLED to 1 in its environment. Plugin reporting is separate.
Before opening the installed plugin in Claude Code, use your project folder unless you want immediate scaffolding: startup context in an empty folder instructs the assistant to choose defaults and execute. To disable plugin reporting before launch, set VERCEL_PLUGIN_TELEMETRY to off in Claude Code's environment.
- 05
Run setup in a terminal and review the confirmation prompts, including any installation into Codex.
vercel setup --plugin - 06
Start a Claude Code session in your project, or apply pending changes in an existing session.
Inside Claude Code/reload-plugins - 07
Confirm the Vercel plugin is enabled in the plugin manager's Installed tab and that a bundled skill such as env-vars appears in the slash menu.
Claude Code is a Vercel-reviewed MCP client. Authorize account tools only when needed, reviewing the teams and permissions granted. The Vercel MCP guide covers direct server setup; Vercel does not document a plugin-specific sign-in procedure for this route.
Agent plugins are a Preview feature in VS Code. Your organization's settings must allow them. This route uses the unified Customization Marketplace's Browse page.
Review the marketplace trust prompt before installing. Plugin MCP servers are implicitly trusted by VS Code. Where startup context loads, an empty folder tells the assistant to choose defaults and begin execution. To disable plugin reporting before launch, set VERCEL_PLUGIN_TELEMETRY to off in VS Code's environment.
- 05
Run Chat: Open Customizations from the Command Palette. Select Browse, then open the source menu and choose Configure Marketplaces.
- 06
Choose Add Marketplace and enter https://github.com/vercel/vercel-plugin. Return to Browse and select the added marketplace from the source menu.
- 07
Select its vercel-plugin entry, choose Install and review the trust prompt. Adding the marketplace alone does not install the plugin.
- 08
Start a fresh session in your project with the intended harness. In Customizations, select Plugins and confirm the Vercel plugin is listed and enabled for that harness and workspace.
If the unified Browse page is unavailable, these marketplace-configuration steps are not documented for that interface. Use the Plugins CLI method instead.
VS Code with Copilot is a Vercel-reviewed MCP client. Authorize account access separately and review the teams granted access. The Vercel MCP guide covers direct server setup; Vercel does not document a plugin-specific sign-in procedure for this installation.
Have VS Code available through its code or code-insiders command, Node.js 18 or later, Git and Bun. Agent plugins are a Preview feature; your organization must allow them. This installer registers the plugin directory in your user-level plugin locations.
Installer reporting includes the entered source, plugin names, target tools and scope. Set DO_NOT_TRACK or DISABLE_TELEMETRY to 1 in its environment before running it to opt out.
Where startup context loads, an empty folder instructs the assistant to choose defaults and begin execution. Open your project unless you want that behavior. Set VERCEL_PLUGIN_TELEMETRY to off in VS Code's environment before launch to disable plugin reporting. VS Code implicitly trusts MCP servers bundled with an installed plugin.
- 05
Run the installer in a terminal.
npx plugins add vercel/vercel-plugin - 06
Review the detected tools and ensure VS Code is included before confirming the user-account installation.
- 07
Start a fresh session with your intended harness and project. Open Chat: Open Customizations, select Plugins and confirm Vercel is listed and enabled for that harness and workspace.
VS Code with Copilot is a Vercel-reviewed MCP client. Account tools still need separate authorization; review the requested teams and permissions. The Vercel MCP guide covers direct server setup; Vercel does not document a plugin-specific sign-in procedure for this route.
Use the Antigravity App for this marketplace installation, following Vercel's Antigravity instructions.
- 05
Open Customizations, then Marketplace.
- 06
Search for Vercel, open the Vercel Plugin entry and install it.
- 07
Inspect active skills from the Customizations menu in the agent side panel and look for Vercel guidance.
For Vercel account tools, Antigravity IDE 2.6.0 or later supports the Client ID Metadata Documents (CIMD) sign-in accepted by Vercel. When the bundled MCP server connects, Antigravity prompts for browser sign-in. Review the connection and intended team access before approving it; installation alone does not authorize account tools.
Use the standalone GitHub Copilot CLI for this route.
Before opening a session with the plugin enabled, use your project folder unless you want immediate scaffolding: startup context in an empty folder instructs the assistant to choose defaults and execute. Set VERCEL_PLUGIN_TELEMETRY to off in Copilot CLI's environment before launch to disable plugin reporting.
- 05
Add Vercel's marketplace from a terminal.
copilot plugin marketplace add vercel/vercel-plugin - 06
Install the plugin listed in that marketplace.
copilot plugin install vercel-plugin@vercel - 07
List installed plugins and confirm the Vercel installation appears.
In a terminalcopilot plugin list - 08
Start a Copilot CLI session in your project.
Vercel accepts reviewed MCP clients or clients using Client ID Metadata Documents (CIMD). GitHub added CIMD support in Copilot CLI 1.0.83, but unresolved login reports mean account sign-in should not be assumed. Vercel does not document a plugin-specific sign-in procedure for this route. Check the Vercel MCP requirements and confirm authorization before using account tools.
Have the standalone GitHub Copilot CLI available on your PATH, Node.js 18 or later, Git and Bun. Plugins CLI adds the source as a marketplace and installs the plugin for your user account.
Installer reporting includes the entered source, plugin names, target tools and scope. Set DO_NOT_TRACK or DISABLE_TELEMETRY to 1 in its environment before running it to opt out.
Before opening the installed plugin, use your project folder unless you want immediate scaffolding. Startup context in an empty folder instructs the assistant to choose defaults and execute. Set VERCEL_PLUGIN_TELEMETRY to off in Copilot CLI's environment before launch to disable plugin reporting.
- 05
Run the installer in a terminal.
npx plugins add vercel/vercel-plugin - 06
Review the detected targets and ensure GitHub Copilot CLI is included before confirming.
- 07
List installed plugins and confirm the Vercel installation appears, then start a Copilot CLI session in your project.
In a terminalcopilot plugin list
Vercel accepts reviewed MCP clients or clients using Client ID Metadata Documents (CIMD). GitHub added CIMD support in Copilot CLI 1.0.83, but unresolved login reports mean account sign-in should not be assumed. Vercel does not document a plugin-specific sign-in procedure for this route. Check the Vercel MCP requirements and confirm authorization before using account tools.
Have Cursor available on your PATH, Node.js 18 or later, Git and Bun. On macOS and Linux, Plugins CLI places this installation in a shared Claude Code plugin cache; Cursor's documentation does not confirm discovery from that cache.
Installer reporting includes the entered source, plugin names, target tools and scope. Set DO_NOT_TRACK or DISABLE_TELEMETRY to 1 in the installer's environment before running it to opt out.
If Cursor loads the startup context, an empty folder instructs the assistant to choose defaults and begin execution. Open your project unless you want that behavior. To disable plugin reporting before launch, set VERCEL_PLUGIN_TELEMETRY to off in Cursor's environment.
- 05
Run the installer in a terminal.
npx plugins add vercel/vercel-plugin - 06
Review the detected tools and scope, ensuring Cursor is included before confirming.
- 07
Restart Cursor, then type a slash in Agent chat and search for a bundled skill such as env-vars.
If the skill is absent, this installation is not confirmed as available in Cursor. Check Cursor's plugin instructions for supported loading methods.
Cursor is a Vercel-reviewed MCP client. Account tools still require separate authorization and intended team access. The Vercel MCP guide covers direct server setup; Vercel does not document a plugin-specific sign-in procedure for this installation.
Use Codex CLI for this route. Plugins are not available in the Codex IDE extension. This method adds Vercel's repository as a marketplace and installs its listed plugin.
The repository's plugin declares startup behavior and reporting that differ from the curated Codex package used by Plugins CLI. Review the components offered by Codex before enabling them; do not assume the two methods install identical surfaces.
- 05
Add the Vercel marketplace from a terminal.
codex plugin marketplace add vercel/vercel-plugin - 06
Open the plugin browser inside Codex CLI. Choose the vercel marketplace and install its listed vercel-plugin entry.
/plugins - 07
Start a new Codex session. Return to the plugin browser and confirm the installation is listed; use the skill picker to look for env-vars. Codex mentions skills with a dollar sign followed by their name.
Codex CLI is a Vercel-reviewed MCP client, but installation does not confirm account authorization. Confirm access to the intended teams before using account tools. The Vercel MCP guide covers direct server setup; Vercel does not document a plugin-specific sign-in procedure for this route.
Have Codex CLI available on your PATH, Node.js 18 or later, Git and Bun. Plugins CLI installs Vercel through Codex's curated marketplace entry, which omits incompatible upstream lifecycle hooks.
The installer reports the source you enter, plugin names, target tools and scope. To disable this reporting, set DO_NOT_TRACK or DISABLE_TELEMETRY to 1 in its environment before running it.
- 05
Run the installer in a terminal.
npx plugins add vercel/vercel-plugin - 06
Review the detected tools and scope before confirming. Ensure Codex is included and follow any authentication prompt. Other detected tools can receive installations too.
- 07
Start a new Codex session. Open the plugin browser and confirm Vercel is installed.
Inside Codex CLI/plugins
If Claude Code was installed into as well, review its startup behavior and reporting before launching it; Components › Hooks covers those actions. Codex CLI is a Vercel-reviewed MCP client, but account tools require separate authorization. Vercel documents direct setup in the Vercel MCP guide, without a plugin-specific sign-in procedure for this route.
Have Codex CLI and Vercel CLI installed. The CLI package requires Node.js 20 or later. Plugin-only setup targets Codex and Claude Code when found, with confirmation prompts, and skips AI Gateway setup.
Vercel CLI reports commands, arguments and account identifiers. Set VERCEL_TELEMETRY_DISABLED to 1 in its environment before this run to disable that reporting.
- 05
Run setup in a terminal, review the detected tools and follow any authentication prompt.
vercel setup --plugin - 06
Start a new Codex session. Open the plugin browser and confirm Vercel is installed.
Inside Codex CLI/plugins
The curated Codex package omits incompatible upstream lifecycle hooks. If setup also installs into Claude Code, review that installation's startup behavior and reporting before opening it. Codex CLI is a Vercel-reviewed MCP client, but account authorization remains separate. The Vercel MCP guide covers direct setup, without a plugin-specific sign-in procedure for this route.
Use OpenCode 2. Its native plugin installation includes skills, specialist agents, commands, session context and the Vercel MCP connection without requiring Node.js or Bun.
Open your project unless you want immediate scaffolding: in an empty folder, startup context instructs the assistant to choose defaults and begin execution. Plugin reporting is enabled by default. To disable it, set VERCEL_PLUGIN_TELEMETRY to off in the environment that launches OpenCode.
- 05
Install the plugin from a terminal.
opencode plugin add github:vercel/vercel-plugin - 06
If you changed the reporting environment variable, restart OpenCode's background service so it receives the new environment.
opencode service restart - 07
Open your project in OpenCode 2. The plugin's commands use the vercel: prefix. OpenCode's documentation does not provide a separate command that confirms this plugin's skills are available.
Only account operations need Vercel sign-in. Those tools can read and change resources, so review the teams and permissions you authorize.
- 05
If you need account tools, open the MCP controls inside OpenCode, select vercel and sign in. Grant access to the intended teams.
Inside OpenCode 2/mcps
Have Grok Build available on your PATH, Node.js 18 or later, Git and Bun. Plugins CLI delegates this installation to Grok Build's native plugin system.
The installer reports the entered source, plugin names, target tools and scope. Set DO_NOT_TRACK or DISABLE_TELEMETRY to 1 in its environment before running it to opt out.
Where the startup context loads, an empty folder instructs the assistant to choose defaults and begin execution. Use your project folder unless you want immediate scaffolding. Plugin reporting is on by default; set VERCEL_PLUGIN_TELEMETRY to off in Grok Build's environment before launch to disable it.
- 05
Run the installer in a terminal.
npx plugins add vercel/vercel-plugin - 06
Review the plugin, detected tools and scope. Confirm that Grok Build is included before approving installation.
- 07
Open Grok Build in your project. Use its extensions modal to inspect installed plugins and available skills, including a bundled skill such as env-vars.
Vercel account access requires a reviewed client or Client ID Metadata Documents (CIMD). Grok Build is not on Vercel's reviewed-client list, and its documentation does not establish CIMD support. Do not rely on Vercel account tools through this installation; check the current Vercel MCP requirements before connecting.
Have Kimi Code installed, Node.js 18 or later, Git and Bun. This method installs for your user account. Kimi supports the plugin's skills, commands, hooks and MCP servers, but does not expose its specialist agents.
Installer reporting includes the entered source, plugin names, target tools and scope. Set DO_NOT_TRACK or DISABLE_TELEMETRY to 1 in its environment before running it to opt out.
Where startup context loads, an empty folder instructs the assistant to choose defaults and begin execution. Use your project folder unless you want that behavior. To disable plugin reporting before the next session, set VERCEL_PLUGIN_TELEMETRY to off in Kimi Code's environment.
- 05
Run the installer in a terminal.
npx plugins add vercel/vercel-plugin - 06
Review the detected tools and confirm Kimi Code is included before approving installation.
- 07
Start a new Kimi Code session in your project, then list installed plugins and check that Vercel appears.
Inside Kimi Code/plugins list
Vercel account access requires a reviewed client or Client ID Metadata Documents (CIMD). Kimi Code is not on Vercel's reviewed-client list, and its documentation does not establish CIMD support. Do not rely on Vercel account tools through this installation; check the current Vercel MCP requirements before connecting.