Translation MCP Server¶
Localize your app from inside Claude Code, Cursor, or Codex — without copy-pasting strings into a chat box and hoping the file still parses.
You're already translating with AI. Do it safely.¶
If you ship a mobile app, you've probably already pasted a strings.xml or en.json into ChatGPT or Claude and asked it to translate. It works… until it doesn't:
- The model "helpfully" reformats your file and breaks the XML or JSON
%1$s/{count}placeholders get translated, reordered, or dropped- Plurals collapse into a single form and crash on certain languages
- Brand names and product terms get translated when they shouldn't be
- There's no memory between runs, so every translation starts from scratch
The GetTranslated MCP server gives you the convenience of translating from your AI editor with the safety of a real localization pipeline underneath.
What it is¶
MCP (Model Context Protocol) is the standard that lets AI editors call external tools. Our MCP server exposes your GetTranslated project to Claude Code, Cursor, Codex, and any MCP-capable client.
Instead of pasting files into a chat, you say what you want:
"Upload
src/i18n/locales/en.json, translate the new strings to Spanish and French, then write the translated files back."
Claude calls the right tools, and the same engine the CLI and SDKs use does the work — format-aware parsing, placeholder protection, translation memory, protected words, and validation included.
Why it beats raw LLM translation¶
| Pasting into a chatbot | GetTranslated MCP |
|---|---|
| Reformats and breaks your file | Parses and re-emits valid Android XML, iOS .strings, RN JSON |
| Translates/garbles placeholders | Protects placeholders and validates them |
| Forgets between runs | Reuses translation memory so you only pay for changes |
| Translates your brand terms | Honors protected words you define |
| No record of what changed | Tracked, reviewable, versioned in your project |
It's the difference between "an AI translated my file" and "my localization pipeline ran, driven by an AI."
What you can do from the chat¶
- Inspect — project config, translation progress, file list, validation issues
- Upload — sync source files for iOS, Android, React Native, or Flutter
- Translate — run AI translation across your target languages (it batches automatically for large projects)
- Download — get translated files back in platform-native format
- Configure — set target languages, translation tone, and protected words
- Quality — run a grammar pass on your base strings
Built for a developer's workflow¶
- No context switching — stay in the editor you already write code in
- Same key as the CLI — authenticate with your project's Server API Key
- Project-scoped and safe — the MCP can only touch the one project its key belongs to; rotate the key anytime
- Works with your stack — Android (
strings.xml), iOS (.strings/.stringsdict), React Native (i18next JSON), Flutter (.arb)
Get connected in two minutes¶
- Copy your Server API Key from your project settings
- Add the server to your editor (one command for Claude Code or Codex, a small JSON entry for Cursor)
- Ask your assistant to translate
Full steps, example prompts, and the complete tool list are in the MCP Quick Start Guide and Tool Reference.