v0 MCP integration for AI agents.
Connect AI agents to v0 through 45 structured actions, including find chats, assign project to chat, delete chat, and favorite chat. Review authentication, i…
- ACTION CONTRACTS
- 45
- 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 v0 integration exposes
The v0 Agent App exposes 45 provider-backed actions for ai and developer tools work. Its current contract lets an authorized agent list chats in the connected v0 workspace with optional filters, assign an existing v0 chat to a project container, and delete a v0 chat by chat id. 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 v0 account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real v0 capabilities.
Showing 12 of 45 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
find_chatsREADList chats in the connected v0 workspace with optional filters.
INPUTS: projectId / vercelProjectId / branch / isFavorite / limit
assign_project_to_chatWRITEAssign an existing v0 chat to a project container.
INPUTS: projectId / chatId
delete_chatHIGH IMPACTDelete a v0 chat by chat ID.
INPUTS: chatId
favorite_chatREVIEWMark or unmark a v0 chat as favorite.
INPUTS: chatId / isFavorite
create_chatWRITECreate a new v0 chat and immediately send the first message.
INPUTS: message / projectId / chatPrivacy / responseMode / metadata
create_deploymentWRITECreate a deployment for a specific v0 chat version.
INPUTS: projectId / chatId / versionId
create_env_varsWRITECreate one or more environment variables on a v0 project.
INPUTS: projectId / decrypted / upsert / environmentVariables
create_hookWRITECreate a webhook hook in v0 for chat or message events.
INPUTS: name / url / events / chatId / projectId
create_projectWRITECreate a new v0 project container for chats, environment variables, and deployments.
INPUTS: name / description / icon / instructions / privacy
create_vercel_projectWRITECreate and link a Vercel project from a v0 project.
INPUTS: projectId / name
delete_env_varsHIGH IMPACTDelete one or more environment variables from a v0 project.
INPUTS: projectId / environmentVariableIds
delete_hookHIGH IMPACTDelete a webhook hook by hook ID.
INPUTS: hookId
INPUT CONTRACTS
Know what the action needs before it runs.
find_chats
projectIdOPTIONAL- v0 project ID.
vercelProjectIdOPTIONAL- Filter by linked Vercel project ID.
branchOPTIONAL- Filter by Git branch.
isFavoriteOPTIONAL- Filter by favorite status.
limitOPTIONAL- Maximum number of results to return.
assign_project_to_chat
projectIdOPTIONAL- v0 project ID.
chatIdOPTIONAL- v0 chat ID.
delete_chat
chatIdOPTIONAL- v0 chat ID.
favorite_chat
chatIdOPTIONAL- v0 chat ID.
isFavoriteOPTIONAL- Whether the chat should be favorited.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Find Chats
List chats in the connected v0 workspace with optional filters. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
find_chatsControl Assign Project To Chat
Assign an existing v0 chat to a project container. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
assign_project_to_chatVerify with Assign Project To Chat
Assign an existing v0 chat to a project container. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
assign_project_to_chatSAFETY BOUNDARY
Operate v0 with explicit limits
- Authorize v0 with API key and grant only the provider access required by the selected actions.
- 17 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_chat`, `delete_env_vars`, and `delete_hook` 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 v0 rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the v0 task completed successfully.
CONNECTION MODEL
API key
v0 API key used with the Authorization Bearer header. Get it from v0 settings.
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
- 24
- WRITE SIGNALS
- 13
- HIGH IMPACT
- 4
- REVIEW SIGNALS
- 4
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 v0.