The TextUnited MCP server is a Model Context Protocol connection that lets you translate text inside an AI assistant using your own terminology, domains, and style guides. It exposes 32 tools across translation, terminology and domains, and style guides. It translates text only, not files, jobs, or whole projects.
What tools does the TextUnited MCP server expose?
The server exposes 32 tools across three areas: translation does the work, terminology and domains decide which words count as correct, and style guides decide how the result should read. You reach all of them from the same connection you set up earlier, without switching tools or leaving the AI assistant you already use.
How does translation work inside your assistant?
A translation request takes a piece of text, a source language, and a target language, and returns translatedText. Behind that simple shape, several settings can be applied: source language, Translation Memory, domain, preferred terms, and style guide. The assistant resolves what you name and performs the translation in one step.
- Source language. Set it explicitly. Automatic detection gets unreliable on short strings, because there is not enough text to detect from.
- Translation Memory. If your company already has a relevant match, it is used.
- Domain. A domain such as Information technology pulls in terminology from that field.
- Preferred terms. You can supply pairs for a single translation, for example framework → marco de trabajo.
- Style guide. A published guide, with the variant that matches the selected language and domain, can be applied.
What does a real translation request sound like?
A good request names the target language, the domain, any term you want kept, and the style guide to follow. You do not need internal IDs, because the assistant resolves the language, the domain, and the guide for you. Here is an example you can adapt:
Translate this into German. Use the Information technology domain, keep framework as Rahmenwerk, and apply the technical docs style guide.
Ready to connect your AI assistant?
Set up the TextUnited MCP server to give your AI assistant access to your terminology, domains, style guides, and translation tools.
How do terminology and domains shape the output?
Terminology and domains are what make the output sound like your company instead of a generic engine. A domain groups terminology for a field such as Information technology. Terminology concepts hold your approved words per language, so the translator knows which term is correct. Through the same connection you can:
- List, create, rename, activate, and deactivate domains.
- Search concepts and pull up their full records.
- Create, update, and delete multilingual terminology concepts.
- Set a term as Preferred, Accepted, or Rejected, and record a definition, part of speech, gender, number, abbreviation, example, tags, and domain.
- Manage tags, concept classes, and terminology import history.
- Read the list of available languages and countries.
How do style guides work?
Style guides carry the rules a translation must follow. You can list, read, create, update, and delete them, browse templates, and build a variant for a particular language, a particular domain, or both. One rule matters more than the rest: only published guides can be applied to a translation. A draft is invisible to the translated output.
What can the TextUnited MCP server not do?
It translates text. It does not translate files, jobs, or whole projects. There is also no separate review or quality assessment step. What you can do instead is run the same text again with a different domain, terminology set, or style guide, and compare the results yourself.
What is the style guide trap to avoid?
A style guide can be published and still be wrong for your language pair. The technical docs guide is published, but its general rules are written for translations into Polish. Applying it to Polish-to-Spanish would push Polish-target rules onto Spanish output. The Information technology domain still applies; the guide does not. Always check that the variant matches the language you are translating into.
How should I get started?
Ask your assistant which domains and style guides are available, then translate one real string where you already know the approved wording. If the output uses your term, the connection is doing its job.
Try it with your own terminology
Start a free TextUnited trial and see how your terminology, domains, and style rules can shape translation inside your workflows.