What it does
While v0 generates code it can read your Brands and tokens and export them (for example as Tailwind or CSS), so the UI it builds uses your real tokens. It can also propose token changes for a person to approve. The tools are listed at /docs/mcp.
Before you start
- A Stoaken account with at least Viewer on a Brand. On the Free plan agents are read only.
- A v0 account.
- Optional: an API key from Settings > API keys (for Bearer Token auth).
Setup
v0 adds MCP servers in its own UI; there is no project file. npx stoaken init --client v0 just prints these steps.
- In a v0 chat, open + > MCPs and add a custom server.
- URL:
https://www.stoaken.com/mcp. - Auth: OAuth, or Bearer Token with your API key.
- Make sure the server is enabled.
Configuration
Nothing to write. The only settings are the URL and the auth type above. v0's permission mode (Ask, Auto, Full) decides whether each tool call asks you first; keep Ask for propose_* tools.
Try it
- "Using Stoaken, get the resolved tokens for the Default theme and build a pricing card with them."
- "Export my Default theme as Tailwind 4 and use it in this project."
Troubleshooting
- OAuth fails: use Bearer Token with an API key instead.
- Tools not offered: the server is disabled in the chat's MCP list.
Limits
- No tool approves or publishes a release.
- The tools are only available to v0 while generating; the app v0 builds can't call them. To ship tokens in that app, export them into its code (or use
stoaken export). - v0 notes that remote MCP may raise per-message cost.