Localize a Bolt app
Add the hosted localize.dev MCP server to Bolt's connectors, so Bolt's agent can localize the project in the editor into any language.
How it works
Bolt can't run a local process, so it uses the hosted server at https://uselocalize.dev/api/mcp. Add it as a custom MCP server in Connectors, set the transport to HTTP and pick API key as the authentication.
Localize one page at a time. The tool gives the text keys, rewrites the components to the i18n library and writes the locale files, and Bolt applies them to the project.
Set it up
First create an API key in the dashboard. Create a key
- Click + in the chat, open Connectors (MCP) and choose Custom MCP server. Enter the URL and set the transport to HTTP.
- Pick API key as the authentication 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
Transport HTTP
Authentication API key
Key ldv_live_… (your localize.dev API key)What you get
- Where the server goes
Connectors (MCP) → Custom MCP server- 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
checkandconfigdon't use your allowance, so checking the whole project before you start costs nothing.- 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 localize tool.
“Localize the pricing page into Spanish and German.”
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.