The MCP server exposes your localization engine directly inside your AI assistant. Test a glossary term, localize a batch of strings, detect a language - without leaving the conversation.
Localize content#
Tell your assistant to localize content and it calls your engine with the full configuration - glossary, brand voice, instructions, and model chain all applied automatically.
"Localize these strings to German through my engine: 'Add to cart', 'Proceed to checkout', 'Your order has been placed'"
The assistant sends the key-value data to your engine, specifying source and target locale. Your engine's glossary enforces exact terms (e.g. "checkout" stays as "Checkout" if you configured it), brand voice applies the correct register, and the configured model chain handles the generation.
You can also provide hints - contextual breadcrumbs that help the engine disambiguate:
"Localize 'Share' to Japanese - it's a button label in a social media context, not a financial share"
What the assistant manages for you#
| Parameter | What it does |
|---|---|
| Engine selection | Which engine to use (defaults to the first in your organization) |
| Source locale | Source language (e.g. en) |
| Target locale | Target language (e.g. de, ja, pt-BR) |
| Data | Key-value map of strings to localize |
| Hints | Optional breadcrumbs per key for disambiguation |
| Reference | Pre-existing localizations for few-shot context |
Batch localization (async)#
For larger payloads or multi-locale runs, the assistant uses async jobs - submit once, get results for every target locale:
"Localize this JSON file to French, German, and Japanese. Use my production engine."
The assistant submits all target locales in a single request. Each locale becomes an independent job that processes in parallel. You can ask for status at any time:
"What's the status of that localization batch?"
The assistant polls the job group and reports progress - how many locales are complete, any failures or warnings, and retrieves results when ready.
Async job capabilities#
- Submit up to 100 target locales per request
- Optional webhook callback when jobs complete
- Idempotency keys to prevent duplicate submissions
- Pipeline configuration overrides per request
- Locked keys excluded from localization
Detect language#
"What language is this text: 'Nous sommes ravis de vous accueillir'"
The assistant detects the language and returns the BCP-47 locale, language name, region, script, and text direction (LTR/RTL).
When to use this vs. the CLI#
| Scenario | Use |
|---|---|
| Testing a glossary term you just added | MCP - instant feedback in the conversation |
| Localizing a single string during code review | MCP - no context switch |
| Running a full project localization across all files | CLI - designed for file-based workflows |
| CI/CD pipeline integration | CLI or API - automated, repeatable |
| Localizing a batch of strings to many locales at once | MCP async jobs - one prompt, parallel processing |