Docs / Agents
Coding agents and app builders
localize.dev runs as an MCP server, so the agent that writes your UI can also give its text keys and translate it. Editors and terminal agents start npx localize-dev mcp on your machine; builders that run in the browser connect to the hosted server.
Localize an app with Claude Code
Add the localize.dev MCP server and after-edit hook to Claude Code, so new UI text gets translation keys and translations while Claude writes the code.
Localize an app with Cursor
Add the localize.dev MCP server and a Cursor rule, so Cursor's agent gives new UI text translation keys and fills in every language as it edits.
Localize an app with Codex
Add localize.dev to ~/.codex/config.toml so OpenAI Codex can find hardcoded UI text, give it keys and translate it, in the CLI and the IDE extension.
Localize an app with GitHub Copilot
Add the localize.dev MCP server to .vscode/mcp.json, so Copilot's agent mode can give hardcoded UI text keys and fill in every language's translations.
Localize an app with Devin (formerly Windsurf)
Add localize.dev to Devin's mcp_config.json, the editor formerly called Windsurf, so its agent gives UI text translation keys and translates it as it codes.
Localize an app with Gemini CLI
Add localize.dev to Gemini CLI's settings.json so Google's terminal agent can check, localize and translate your app's UI text.
Localize a Lovable app
Connect Lovable to the hosted localize.dev MCP server, and its agent finds the hardcoded text in your app, gives it keys, sets up react-i18next and translates it. The translations stay in your code as locale files, with no script or proxy in front of the site.
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.
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.