v0
by v0
Drive Vercel's v0 app builder from an AI agent — create chats, send prompts, approve the v0 agent's plans and permissions, and fetch preview URLs. 8 tools, OAuth with a single mcp scope, generation spends paid credits.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect v0 via MCP
https://v0.app/api/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
v0 Tools & Capabilities (8)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- One OAuth scope covers everything. v0's authorization server advertised
scopes_supportedof exactly["mcp"]on 2026-08-22. There is no read-only grant, so consent cannot separate listing your chats from creating new ones that spend money. The boundary a reader would want — between the routine read and the credit-spending write — does not exist at the grant. - One listed tool is undocumented.
import-claude-design-from-urlappears in Anthropic's listing and nowhere in v0's 1.3 MB documentation corpus. We could not establish what it does. - We could not read tool schemas or safety annotations. The endpoint returns 401 to an anonymous request. Every parameter named on this page comes from v0's REST reference for the backing endpoint, not from the MCP tool's own schema, and the two can differ.
- Generation costs credits with no in-band cap. Free accounts get $5 monthly and 7 messages per day; paid plans are credit-based. Nothing in the tool surface limits spend per call.
- Training opt-out is a paid-plan feature. v0's pricing comparison lists Data Opt-out as Business and Enterprise only. Prompts and generated code sent through this connector on Free, Premium or Plus have no documented opt-out.
resolveTaskcan approve a shell command. Itsconfirmed-permissionsvariant grants the v0 agent permission to run a tool, script or MCP call it proposed. The approval must match the pending request, but no human sits between your agent and that approval.- The v0 agent's autonomy is set outside MCP. Ask, Auto and Full permission modes are a v0 account setting persisting across chats. The MCP surface neither reads nor changes it, and Full mode skips permission evaluation including v0's own
rm -rfguard, which v0 describes as not a complete safety boundary. - The v0 sandbox holds your project's environment variables. v0 states they are "available to both your app and any agent tool that runs in the sandbox", and the v0 agent can also browse external URLs and search the web. A prompt sent through this connector reaches a runtime that holds secrets and can make outbound requests.
- Team Owners can read chats an agent creates. v0 states anyone with the Vercel Owner role on the owning team can open a team chat by URL and edit or archive it, including private ones.
- Chat visibility may be settable per call. The backing endpoint accepts
privacy: 'public', which v0 defines as indexable by search engines. Whether the MCP tool exposes it is unverified. - No published rate limits for v2. v0 documents a rate-limits endpoint on API v1 only; we found no v2 rate-limit reference and no MCP-specific limit.
- Publishing a template is not on this surface. v0's public Templates gallery is reached through the web interface, with no documented v2 endpoint and no tool.
Frequently asked questions
Yes. Every generation spends credits from your v0 balance, and v0's Create Chat response returns a creditsCost object alongside token counts. v0's pricing page gives Free accounts $5 of monthly credits and a 7-message daily cap, Premium $20 and Plus $30 per user. When credits run out, v0 states that generation pauses.
Not through the tools listed. v0 documents a Deploy Chat endpoint that triggers a Vercel deployment, but the MCP guide names only seven backing endpoints and that is not one of them. Publishing to production is a Publish button in the v0 web interface. Treat this as the current listing's shape, not a guarantee.
No. v0's Get Preview URL endpoint returns a URL, a short-lived token and an expiry timestamp, and v0 states the preview is reached by sending that token in an x-v0-preview-token header. Browsers cannot attach a custom header to an iframe, so v0 documents proxying previews through your own backend instead.
More than a plan. v0's task schema has five variants, and one of them, confirmed-permissions, is documented as resolving a request where the v0 agent wants to execute a tool, shell command, script or MCP call. Calling resolveTask on that variant grants the v0 agent permission to run the command it asked about.
One scope, named mcp. v0's authorization server metadata advertised scopes_supported of exactly that single value on 2026-08-22. There is no read-only variant offered, so nothing at the OAuth grant separates listing your existing chats from creating new ones that spend credits.
The client is holding a stale tool list. v0's troubleshooting section says to restart or reconnect the MCP client so it refreshes the server's tool list, then check the v0 API v2 reference for the resource you expected. Reconnecting also fixes authentication failures after a token expires.
Remove the connection and add it again. v0 states that if you need to switch users or teams you should remove the existing v0 MCP connection in your client and connect to https://v0.app/api/mcp again. The account or team is chosen during the OAuth approval step, not per request.
On most plans, yes. v0's pricing comparison lists Data Opt-out as available only on Business and Enterprise, and its security page describes opting out of content being used for model training as an Enterprise feature. Free, Premium and Plus accounts have no documented opt-out.
No, they are two separate connectors with separate endpoints. Anthropic lists Vercel at mcp.vercel.com with seven read-only tools for inspecting projects, deployments and teams. v0 runs at v0.app/api/mcp and drives the app builder, so its tools generate code and spend credits.
Sources
- v0 guide, "Use v0 from an MCP Client" (retrieved 2026-08-22). Markdown served by appending
.md; this is thedocumentationURL Anthropic's directory publishes. · retrieved 2026-08-22 - v0 API v1 adapter page, "MCP Server" (retrieved 2026-08-22). Describes the same endpoint for IDE clients and supplied the troubleshooting section. · retrieved 2026-08-22
- v0 documentation corpus,
llms.txt(1.3 MB) and semantic sitemap — · (retrieved 2026-08-22). Both grepped for the undocumented tool name; zero hits. · retrieved 2026-08-22 - v0 agent discovery file (retrieved 2026-08-22) · retrieved 2026-08-22
- v0 API reference, Create Chat, Send Message, Resolve Task, Get Preview URL, Deploy Chat, Delete Chat — · · · (retrieved 2026-08-22) · retrieved 2026-08-22
- v0 guide, "Handling Agent Interactions" (retrieved 2026-08-22) · retrieved 2026-08-22
- v0 guide, "Accessing Previews" (retrieved 2026-08-22) · retrieved 2026-08-22
- v0 documentation, Terminal commands, Agentic features and Sandbox — · · (retrieved 2026-08-22) · retrieved 2026-08-22
- v0 documentation, MCP Integrations (retrieved 2026-08-22) · retrieved 2026-08-22
- v0 documentation, Pricing, Security and Sharing — · · (retrieved 2026-08-22) · retrieved 2026-08-22
- v0 documentation, Deployments and Templates — · (retrieved 2026-08-22) · retrieved 2026-08-22
- Live auth check: anonymous
initializetohttps://v0.app/api/mcpreturned HTTP 401 withWWW-Authenticate: Bearer resource_metadata="https://v0.app/.well-known/oauth-protected-resource"; that descriptor returned JSON naming the resource and authorization server, andhttps://v0.app/.well-known/oauth-authorization-serverreturnedscopes_supportedof["mcp"](2026-08-22) · retrieved 2026-08-22 robots.txt(retrieved 2026-08-22). NoDisallowrules and noContent-Signalline; the sitemap is declared. · retrieved 2026-08-22- Vercel changelog, "Deploy from Claude Design to Vercel" (2026-06-23), read from Vercel's changelog sitemap (retrieved 2026-08-22) · retrieved 2026-06-23
- Vercel knowledge base, "Deploy a Claude Design project to Vercel" (retrieved 2026-08-22). Names the Vercel connector and Vercel Drop; does not mention v0. · retrieved 2026-08-22
- Official MCP registry, searched for v0 and Vercel (retrieved 2026-08-22). No Vercel or v0 server listed. · retrieved 2026-08-22
- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- v0 support — · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Developer Tools
- Developer
- v0
- Tools
- 8
- Domain
- v0.app
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.