---
title: ToolRouter — Agent Use Case Guide
description: Step-by-step guide for completing a task with a specific AI agent using ToolRouter.
url: https://toolrouter.com/tools/translate/use-cases/translate-ui-text/copilot
---
# How to Translate UI Text with Copilot

Copilot brings translation directly into your i18n workflow, treating localization as a code task rather than an external handoff. Translate locale files, UI strings, and documentation without leaving your editor, then review the changes in your diff view alongside the rest of your code. This is ideal for developers who maintain localization as part of the build process, ensuring that new features ship with translations rather than accumulating a backlog of untranslated strings that need a separate localization pass.

## Setup

{"mcpServers":{"toolrouter":{"command":"npx","args":["-y","toolrouter-mcp"]}}}

## Steps

1. Add ToolRouter to Copilot MCP config
2. In Copilot Chat: "Translate src/locales/en.json to Japanese using the translate tool"
3. Copilot creates src/locales/ja.json with all strings translated
4. Review the diff for any placeholders or variables that were modified
5. Ask Copilot to add the new locale to your app configuration

## Example Prompt

```
Translate src/locales/en.json to Japanese, Korean, and Chinese. Create the output files and update the i18n config to include the new locales.
```

## Tips

- Copilot can update your i18n configuration file to register new locales automatically
- Works with all major i18n formats: JSON, .po, .xliff, .strings, strings.xml
- Ask Copilot to verify completeness -- no missing keys in the new locale files
