Localize a v0 app
Connect v0 to the hosted localize.dev MCP server, so it can add languages to the app it generates and fill in their translations.
How it works
v0 uses custom MCP servers while it generates code. Add the hosted server from the prompt form (+, then MCPs, then Configure) with your API key as a Bearer token.
add_language adds the language to the app's config and translates every existing message into it, so “Add Japanese” is one tool call, not a file per page.
Set it up
First create an API key in the dashboard. Create a key
- Open + in the prompt form, choose MCPs, then Configure, and enter the URL.
- Pick Bearer Token and paste your localize.dev API key.
- Open your project and ask something like the prompt below. The agent sends the files the tool needs and writes back the files it returns.
Name localize
URL https://uselocalize.dev/api/mcp
Authentication Bearer Token
Key ldv_live_… (your localize.dev API key)What you get
- Where the server goes
+ → MCPs → Configure- Server
- The hosted server at
https://uselocalize.dev/api/mcp - Key
- Your localize.dev API key, as a bearer token
- What
init --agentadds - Nothing: a browser builder can't run npx, so it connects to the hosted server.
Good to know
- v0 apps are usually Next.js. The Next.js guide shows the i18n setup localize.dev writes for the App Router.
- If the project syncs to GitHub, the localize.dev GitHub Action can also translate every push and open one pull request with the keys and translations.
Try it
Ask something like this. The agent should call the add_language tool.
“Add Japanese to this app.”
Keep it translated
Text the agent leaves hardcoded still gets caught: npx localize-dev check in CI fails a pull request that adds untranslated copy, and it needs no key.
npx localize-dev checkAll agents and the tool reference are on the MCP server page.