Your assistants are writing and translating for your company on a general model.
Everything that makes it sound like itself — how you name things, in every market you sell in — is sitting somewhere they cannot reach. Connect the MCP server once and your language data becomes available inside the assistant your team already uses. Terminology first, read and written back depending on the token. More of the record follows as each capability opens.
What the assistant can reach
The same terminology your translations are bound by, in the window they are already working in.
Terminology is multilingual by construction: one concept, one agreed meaning, and an approved label in each language you operate in. Which is why the same connection serves someone drafting German product copy and someone translating it — they are asking the same question of the same record.
| Ask | What do we call this, in this market — and what did we decide not to call it. Answered without opening anything. |
| Write with it | Draft or translate against your approved labels rather than the model's best guess at your industry. |
| Add | A term, or a spreadsheet of six hundred, with the rules given in plain language — lower case throughout, except German nouns. |
| Correct | Change an entry, retire one, reorganise domains. No ticket, no training. |
| Audit | Duplicates, entries that contradict each other, casing that drifted across three thousand concepts. The pass nobody does by hand because nobody has a week. |
Read and write are separate permissions. Most people get the first; the handful who settle terminology get the second.
What gets settled there binds everywhere
A decision made in a chat window is a decision the whole company is bound by.
A term corrected in Copilot at eleven o'clock is the term the translation engine enforces that afternoon — whether the content arrives through the interface, through the API, or through a pipeline nobody is watching.
Enforcement is a property of the record, not of the surface somebody happened to be using when they decided. That is what makes this more than a convenient way to edit a list.
Nobody has to be told it is there
IT connects it once. No rollout, no training, nothing installed.
The people writing product descriptions keep writing them where they write them. The assistant simply starts answering with your company's words instead of a general model's.
Which matters more than convenience. Every previous attempt to get an organisation's terminology used has failed at the same point: somebody had to remember to check, in a system they had no other reason to open. This removes the step rather than making it faster.
Who can do what
A token is a person, not a key to the building.
Access is a personal access token with scopes. It represents the individual who created it, so every change carries their name, including changes made by somebody else holding it.
| Read-only exposes nothing else | A token without write access does not surface the write tools at all. The assistant is never offered the option, and the person using it never learns those operations exist. |
| A token cannot exceed its owner | One issued by a regular user cannot be given administrator reach. |
| Expiry and revocation | Tokens run out on a schedule you set, and can be withdrawn at any time. |
| We never hold the token | Only a hash of it, so a breach on our side yields nothing usable. |
The pattern this makes possible. A consultant needs to sort out your terminology. Issue a token that lasts a day, they work through their own assistant, every change is attributed to you, and when the day ends the access ends with nothing to uninstall.
Two doors, same room
For the people who do come in.
Some of your team will open TextUnited, the ones running projects, the ones who own the terminology. For them the same conversation exists inside the terminology interface: adding, correcting, auditing, in the place they were going anyway.
The two are not alternatives. One reaches content being produced in tools we do not own; the other serves the people who work in ours. Most organizations end up using both, for different people.
For whoever is asked to connect it
The paragraph your IT will want.
Remote server over HTTP at `mcp.textunited.com/mcp`. Bearer token in a header or an environment variable. Tools filtered by scope, so a token without write access does not surface the write tools at all. It is a wrapper on the same API the rest of the platform uses; same functionality, same logic, reached a different way.
Connection details for Claude Code, Cursor, the ChatGPT desktop app and Copilot are in the reference.
API and MCP reference →
Before you ask IT
Questions
Does this work with the assistant we already have?
If it is an installed application — the ChatGPT desktop app, Copilot in your Microsoft licence, Claude, Cursor — yes. The browser version of ChatGPT does not support MCP, which catches people out, so it has to be the app rather than the website.
What does it cost to run?
Nothing on our side. The assistant is yours and its model usage is billed by whoever provides it, exactly as it is today. Connecting the server adds no line to your TextUnited invoice.
Can somebody change our terminology by accident?
Only if their token allows it. A read-only token does not expose the tools that write, so the option is never presented. Every change that does happen carries the name of the token's owner.
Our IT has MCP turned off in Copilot.
That is the default for Copilot Business and Enterprise — an administrator enables the policy before any MCP server can be connected. A single setting rather than a project.
What can it reach?
Terminology and the language data behind it. Everything else sits behind a scope that does not exist yet, which is deliberate: capabilities are opened one at a time rather than all at once. The connection you make now does not need redoing when the next one arrives.
Is this instead of the API?
No. The API is how content moves through the rules; this is how the rules are reached and changed. Companies running both use them for different jobs and different people.
Connect once
Connect it once and stop asking people to remember.
The terminology exists. What has always been missing is a way for it to reach the place where your content is actually being written.