---
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-support-docs/copilot
---
# How to Translate Support Docs 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 docs/getting-started.md to Spanish using the translate tool"
3. Copilot creates docs/es/getting-started.md with the translated content
4. Review the translation in your editor
5. Ask Copilot to translate the remaining docs in the same directory

## Example Prompt

```
Translate all markdown files in docs/en/ to Spanish and French using the translate tool. Put them in docs/es/ and docs/fr/.
```

## Tips

- Copilot preserves markdown structure including links, code blocks, and images
- Use for docs-as-code workflows where documentation lives in git
- Ask Copilot to update any relative links for the new locale directory
