i18n-agent

AI-powered translation for 48 languages with context-aware quality

i18n-agent is an MCP server that provides AI-powered translation capabilities across 48 languages. It is distributed as an npm package (@i18n-agent/mcp-client, version 1.16.3) and communicates over stdio transport. The server is published by ai.i18nagent and connects to a remote backend configured through two environment variables: I18N_AGENT_API_KEY, which authenticates requests, and MCP_SERVER_URL, which points to the backend endpoint.

The server’s stated capability is context-aware translation quality, meaning it attempts to preserve meaning and nuance rather than performing purely literal word substitution. With 48 languages supported, it covers a broad range of locales suitable for internationalisation workflows.

Because no tools are exposed in the current facts, the specific operations an agent can invoke — such as translating a string, detecting a language, or batch-processing resource files — cannot be confirmed from available information. Developers should verify the tool surface by inspecting the running server before building automation around it.

This server is appropriate when an agent needs to translate content at runtime as part of a larger workflow, for example localising generated text before delivery. It requires an active internet connection to reach MCP_SERVER_URL and a valid API key, so it is not suitable for fully offline or air-gapped environments.

Use cases

  • Translate UI strings or content into one of 48 supported languages during an automated pipeline
  • Localise AI-generated text before delivering it to end users in different regions
  • Integrate runtime translation into an agent workflow without building a custom translation layer
  • Supply context-aware translations to reduce post-editing effort in multilingual applications

When to use it

  • When an agent workflow requires translation into any of the 48 supported languages at runtime
  • When context-aware translation quality matters more than simple word-for-word substitution
  • When the deployment environment has outbound internet access to reach the configured MCP_SERVER_URL

When not to use it

  • In air-gapped or offline environments where the server cannot reach MCP_SERVER_URL
  • When no I18N_AGENT_API_KEY is available, as authentication is required
  • When the target language is not among the 48 supported languages
  • When a local, self-contained translation model is required with no external API calls