--- title: Use v0 from an MCP Client description: Create, import, edit, and deploy apps and manage v0 resources from an MCP client docs_index: /docs/llms.txt lastUpdated: 2026-10-01 product: v0 API type: guide related: - /docs/api/v2/guides/integrating-v0-into-agents - /docs/api/v2/reference/mcp-servers/create-mcp-server - /docs/api/v2/reference/chats/create-chat --- > For an index of all documentation, see [/docs/llms.txt](/docs/llms.txt). The v0 MCP server lets another agent use v0. Connect it to an IDE, desktop assistant, or agent runtime to create and import chats, edit files, continue app builds, deploy apps, and manage MCP servers, webhooks, usage, and preview settings. To give v0 access to an external service's tools instead, [create an MCP server](/docs/api/v2/reference/mcp-servers/create-mcp-server). The MCP server runs at: ```txt https://v0.app/api/mcp ``` ## 1. Connect your MCP client Use the remote MCP URL directly if your client supports streamable HTTP MCP servers: ```json { "mcpServers": { "v0": { "url": "https://v0.app/api/mcp" } } } ``` If your client requires a local stdio bridge, use `mcp-remote`: ```json { "mcpServers": { "v0": { "command": "npx", "args": ["mcp-remote", "https://v0.app/api/mcp"] } } } ``` The first connection starts an OAuth flow. Sign in to v0, choose the account or team you want the client to use, and approve the connection. > The MCP server uses OAuth for MCP clients. Do not put a v0 API key in your MCP client configuration. ## 2. Use v0 tools The v0 MCP server has full parity with the public v0 API v2, with two exceptions: - **Streaming operations** are not exposed as MCP tools. Use the synchronous or async tools instead. - **ZIP file downloads** (`chats.downloadFiles`) are not exposed. Use `chats.getFiles` to read source files. Tool names match the API operation names, such as `chats.create` and `messages.send`. Your MCP client discovers each tool's input schema. See the [v0 API v2 reference](/docs/api/v2/reference/chats/create-chat) for parameters and response details. ### Async generation `chats.createAsync` returns `chatId` and `messageId` immediately. `messages.sendAsync` and `messages.resolveAsync` return only `messageId`; retain the `chatId` you supplied. Poll `messages.get` with the `chatId` and returned `messageId` until the assistant message's `finishReason` is non-null. Inspect the completed message for pending tasks before continuing. ### Additional tools | Tool | Purpose | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `chats.getUrl` | Get the canonical v0 web URL for a chat you can access. Pass `chatId` after creating or importing a chat and share the returned URL. | | `import-claude-design-from-url` | Import a Claude Design HTML export from a Claude-hosted HTTPS URL into a new private v0 chat. The HTML is uploaded to a public Vercel Blob before generation starts. | Use `chats.getUrl` to open the conversation in v0 and `chats.getPreview` to open the generated app preview. ## 3. Try common workflows Once connected, ask your MCP client to work with v0. ### Create a chat ```txt Create a v0 chat that builds a React dashboard with charts and filters. ``` ### List chats ```txt List my v0 chats related to React dashboards. ``` ### Get chat details ```txt Show me the details of v0 chat chat_abc123. ``` ### List messages in a chat ```txt List the messages in v0 chat chat_abc123. ``` ### Continue an existing chat ```txt Send a message to chat chat_abc123 asking v0 to add dark mode support. ``` ### Resolve a pending task When v0 pauses for input—such as approving a plan, answering a question, granting a permission, or finishing integration setup—resolve the task to let it continue. ```txt Approve the plan that v0 proposed in chat chat_abc123. ``` ### Get a preview URL ```txt Get the preview URL for chat chat_abc123. ``` ### Import an existing app ```txt Import my GitHub repository https://github.com/acme/dashboard into a new v0 chat, then get the chat URL so I can open it in v0. ``` You can also import inline source files, a ZIP archive, an existing Vercel project, or a Claude Design HTML export. ### Read and edit source files ```txt Read the files in chat chat_abc123 and update the homepage heading to "Acme Dashboard". ``` ### Deploy an app ```txt Deploy the app in chat chat_abc123 to Vercel. ``` `chats.deploy` creates a Vercel project if the chat does not have one. Use the Vercel CLI to look up Vercel projects, deployments, deployment status, and deployment logs. ### Manage resources and review usage ```txt List my configured MCP servers and webhooks. ``` ```txt Show my v0 usage summary and recent usage events. ``` ## 4. Reconnect or change accounts If the client loses access, reconnect the v0 MCP server from your MCP client. If you need to switch users or teams, remove the existing v0 MCP connection in the client and connect to `https://v0.app/api/mcp` again. ## Troubleshooting **Connection failed** - Verify the MCP server URL is `https://v0.app/api/mcp`. - Make sure your MCP client supports remote MCP servers or is configured through `mcp-remote`. **Authentication failed** - Reconnect the v0 MCP server in your client. - If your team requires SSO, complete the re-authentication link returned by the tool response, then retry the request. **Tool is missing** - Restart or reconnect your MCP client so it refreshes the server's tool list. - Check the v0 API v2 reference for the resource you expect the MCP server to use. --- For a semantic overview of all documentation, see [/docs/sitemap.md](/docs/sitemap.md) For an index of all available documentation, see [/docs/llms.txt](/docs/llms.txt) For agent-facing discovery, including API and MCP surfaces, see [/docs/agents.md](/docs/agents.md)