All clients
v0
v0 supports custom MCP servers via the v0 API, register the Creatorland server once and reference it in chat sessions.
Setup
v0 by Vercel
Loading setup…
- Who it’s for
- Teams using v0 (Vercel) for UI generation who want their generations grounded in creator data.
- Compatibility
- v0 added custom MCP server support via the v0 API in March 2026. Registration is programmatic rather than via a settings UI: you authenticate the server through the API and then reference the returned identifier when setting up v0 chat sessions. Vercel’s v0 documentation has the current API surface.
- Verify the connection
- After you sign in with your Creatorland account, your tools appear in the client, scoped to your account. If the list comes back empty, that signals the email you signed in with has no Creatorland account yet, create one (or sign in with the right one) at creatorland.com and reconnect. An empty list still confirms the OAuth handshake succeeded and you’re pointed at the right server.
Troubleshooting
- The OAuth handshake runs server-side during registration, you authenticate once when registering and don’t see a browser flow per chat session.
- For team workspaces, the registering user’s OAuth token is what authorizes calls, if that user leaves the workspace, the registration must be redone by another member.
- The v0 MCP surface is still evolving, if registration fails or the docs look out of date, the [troubleshooting guide](/docs/troubleshooting) and [status page](/docs/status) cover the common cases.
