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.
How it works
Devin, the editor formerly called Windsurf, reads MCP servers from ~/.config/devin/mcp_config.json, or .devin/mcp_config.json in the project. The Devin CLI adds one with devin mcp add.
Ask for a dry run first. localize with dry_run reports the keys and rewrites it would make without writing a file, so you see what changes before anything does.
Set it up
First run npx localize-dev login in your terminal. It signs you in through the browser and saves a key, which the server reads, so the config below carries none.
- Add localize to ~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows).
- Restart the agent, or reload its MCP servers, so it starts localize.
- Open your repository and ask it something like the prompt below.
{
"mcpServers": {
"localize": {
"command": "npx",
"args": ["-y", "localize-dev", "mcp"]
}
}
}What you get
- Where the server goes
~/.config/devin/mcp_config.json- Server
localize-dev mcp, started with npx on your machine- Key
- The one
npx localize-dev loginsaved - What
init --agentadds - The
AGENTS.mdsection with the instructions. Add the server by hand, as above.
Good to know
- On Windows the user file is
%APPDATA%\devin\mcp_config.json. - Devin gets no after-edit hook. Run
npx localize-dev check --changedbefore you commit, or in CI, to catch text the agent left hardcoded.
Try it
Ask something like this. The agent should call the localize tool.
“Do a dry run of localizing the settings page, then apply it.”
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.