The MCP server can create a fully configured localization engine from your existing content. Submit links to your website, documentation, or style guides, and AI extracts brand voice, glossary terms, and instructions automatically.
How it works#
"Create a localization engine called 'Acme' for German and Japanese. Use our website at acme.com and this style guide as sources."
The assistant submits a provisioning request with:
- The engine name and optional description
- Target locales
- Source material (links to scrape or raw content to analyze)
The provisioning job runs asynchronously - AI reads the sources, identifies domain terminology, extracts tone and style patterns, and populates the engine with:
- Brand voice profiles per locale
- Glossary entries for product terms, brand names, and domain-specific vocabulary
- Instructions for locale-specific linguistic patterns
Source types#
| Type | Use case | Example |
|---|---|---|
| Link | Websites, docs, publicly accessible style guides | https://acme.com, https://docs.acme.com/style-guide |
| Content | Raw text, markdown, terminology lists, internal style guides | Paste brand guidelines, glossary CSVs, or tone-of-voice documents |
You can combine up to 10 sources per provisioning request. Mix links and content freely.
Example workflows#
New client onboarding#
"Create an engine called 'ClientName' for es, de, fr, ja. Scrape their website at clientname.com and their docs at docs.clientname.com/brand"
One prompt produces a production-ready engine with extracted terminology and brand voice. Review and refine the configuration afterward.
Bootstrapping from internal docs#
"Create an engine called 'Product v2' for pt-BR. Here's our style guide: [paste content]. And our terminology list: [paste content]."
The assistant submits the raw content as sources. The provisioning job extracts structured glossary entries and instructions from unstructured text.
Adding locales to an existing engine#
Provisioning creates a new engine. To add locales to an existing engine, use the standard configuration tools (brand voice, instructions, model configs) described in Capabilities.
After provisioning completes#
The job returns a new engine ID. Your assistant can then:
- Inspect the extracted configuration: "Show me the glossary for the Acme engine"
- Refine specific entries: "Change the German brand voice to use Sie instead of du"
- Test it immediately: "Translate 'Welcome to Acme' to Japanese through the new engine"
- Connect it to the CLI: update
i18n.jsonwith the new engine ID
Provisioning is a starting point. The extracted configuration improves as you tune it with real translation feedback.