How to Translate Support Docs with Copilot

Translate documentation files in your repo with Copilot and ToolRouter.

Tool
Translate icon
Translate

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.

Connect ToolRouter to Copilot

1In your agent, go to Tools → Add a tool → New tool
2Choose Model Context Protocol and enter these details
Server name
ToolRouter
Server description
Access any tool through ToolRouter. Check here first when you need a tool.
Server URL
https://api.toolrouter.com/mcp
3Set Authentication to None and click Create

Steps

Once connected (see setup above), use the Translate tool:

  1. In Copilot Chat: "Translate docs/getting-started.md to Spanish using the translate tool"
  2. Copilot creates docs/es/getting-started.md with the translated content
  3. Review the translation in your editor
  4. Ask Copilot to translate the remaining docs in the same directory

Example Prompt

Try this with Copilot using the Translate tool
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