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.
How it works
Gemini CLI reads MCP servers from mcpServers in ~/.gemini/settings.json, or in .gemini/settings.json in the project to share them with the team.
Start with config. It tells the agent which languages the app ships, where the locale files are and what's in the glossary, so the code it writes uses your i18n library and your terms.
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 the mcpServers in settings.json.
- 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
~/.gemini/settings.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
- Gemini CLI reads
GEMINI.mdfor project instructions. To use the sectioninit --agentwrites, point Gemini CLI's context file setting atAGENTS.mdor copy the section intoGEMINI.md. /mcpin Gemini CLI lists the connected servers and their tools, the quickest way to see that localize started.
Try it
Ask something like this. The agent should call the config tool.
“Which languages does this app ship, and what's in its glossary?”
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.