v0 and Vercel Marketplace
Use the native integration to obtain a database that belongs to the user's Marketplace installation and Vercel project.
- Inspect whether Prisma Postgres is already connected to the current project and environment. Reuse that resource.
- If it is not connected, use the host's native integration flow to select an existing resource or create one. In v0 this may appear as an integration request tool; discover what the host exposes instead of assuming a fixed tool name.
- Wait for the connection and injected environment configuration. Verify which variables the application uses without printing their values.
- If the app sees a variable but a shell command does not, follow the environment-loading step in
prisma-postgres-setup. - Return to
prisma-postgres-setupfor the chosen ORM and query verification.
Where MCP fits
When native Marketplace MCP tools are available, inspect their descriptions, permissions, and resource scope before use. Use them for supported operations on the selected resource. Keep schema changes consistent with the application's migration workflow.
A general Prisma MCP provisioning tool creates a Prisma resource; that alone does not establish Marketplace registration, billing, project connection, or environment injection. Do not substitute it for a blocked native installation. Report the missing connection or permission.
The agent calls MCP tools while building the app. The generated app connects through its ORM or database driver; it does not need to call MCP for normal database queries.
Sources: v0 databases, v0 MCP, Vercel native integrations.