v0 MCP connector for AI agents

CALL ANY TOOL

6 tools covering generate, update, deploy.

v0mcp_createchat

Create a new chat using the v0 platform api. starts a fresh

Create a new chat using the v0 platform api. starts a fresh v0 conversation from an initial message and returns the created chat, including generated ui and a chat id you can use with v0mcp_getchat or v0mcp_sendchatmessage.

Parameters

Name

Type

Required

Description

message

string

Required

The initial message to start the chat with.

attachments

array

Optional

Attachments to include with the initial message.

chatPrivacy

string

Optional

Privacy level for the chat.

designSystemId

string

Optional

The ID of a design system to apply to this chat.

modelConfiguration

object

Optional

Model configuration for the chat.

projectId

string

Optional

Associates the chat with a specific project.

v0mcp_findchats

Find all chats using the v0 platform api. returns the list o

v0mcp_getchat

Get a specific chat by id using the v0 platform api. returns

v0mcp_getuser

Get user information using the v0 platform api. returns deta

v0mcp_sendchatmessage

Send a new message to an existing chat using the v0 platform

Build your Agent

Same auth pattern across every framework.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="v0mcp")

mcp = MultiServerMCPClient({
    "v0mcp": {
        "url": "https://mcp.scalekit.com/v0mcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "v0mcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/v0mcp
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "v0mcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/v0mcp
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="v0mcp")
# Connect to MCP at https://mcp.scalekit.com/v0mcp
# Pass: Authorization: Bearer + token

Try these prompts

Paste any prompt into your agent to get started.

Get started

Copy the prompt

Copied

Create a new chat using the v0 Platform API?

Copy the prompt

Copied

Find all chats using the v0 Platform API?

Advanced

Copy the prompt

Copied

Get a specific chat by ID using the v0 Platform API?

Copy the prompt

Copied

Get user information using the v0 Platform API?

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

1

Authorize

Your user connects

v0 MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

2

Store

Their

v0 MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

3

Resolve

When your agent calls a

v0 MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

4

Audit

Every

v0 MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

No items found.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

One connector today. Ten tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access v0 as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the v0 OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in v0?
Yes. Pass a tool name filter to listScopedTools so the AI agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches v0.

What happens when a user revokes v0 access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Whose v0 usage do generated UIs bill against?
The authorizing user's v0 account. Chats, follow-up messages, and platform calls run with that user's credential and plan limits, never a pooled key.

v0 MCP

v0 MCP tools for AI agents