PTC translation MCP server: your agent translates your app
PTC (Private Translation Cloud) has a translation MCP server for Claude Code and Codex. Your agent connects it, and your app comes back translated.
What you get: your app translated, reviewed and delivered
- Your app in the languages you choose, with your terminology, and a translator note next to every text that needed one.
- A language you do not read, safe to ship: PTC reviews every translation before delivery and fixes what the review finds.
- The translations delivered the way you work: through your build system, as files in your project, or as a download.
- Later changes come back translated by themselves, and only the new and changed texts are billed.
Your work: one prompt and a few decisions
Your agent works in your repository and PTC leads it, one task at a time. The eight steps below show one run, one pass of your agent through the work, from your side. The session lines (what you type and what PTC answers in your agent's chat) are examples written before our own recorded run; the exact wording your agent shows will differ.
The run, step by step: from one prompt to your translated app
Your app, in English only
Your texts live in the resource files your framework already uses (Rails, WordPress, i18next, iOS or Android). Nothing else is needed before you start.
Connect PTC to your coding agent
Open your agent token page in PTC (the token is the key your agent uses to reach your account) and copy the one-line command for your agent: Claude Code, Codex, Cursor or any MCP client.
[the connect command copied from your agent token page] PTC is connected to this agent.
One prompt
Tell your agent what you want. PTC leads it from here: it scans your repository, lists the files that hold your texts and fixes code that translates badly.
Set up PTC translations. Scanning the repository. Found 3 resource files with 1,240 texts.
Your decisions: languages, source fixes, delivery
You are asked only what the code cannot settle, each question once, your answer recorded:
- which languages;
- whether PTC may propose fixes to your source texts and code conventions;
- how the translations should arrive.
Which languages do you want? German, French, Spanish and Japanese.
The price, before any paid work
PTC computes the price from its own scan of your files and shows it, at your Pay-As-You-Go rate (a price per word, paid as you go). Nothing is translated until you say yes. On a free trial the price is not asked under the allowance.
1,240 texts, about 8,700 words, into 4 languages: 34,800 words to translate. At your Pay-As-You-Go rate, the first 500 words free, that is about €77. Go ahead? Yes.
Translation and review
PTC builds your glossary from your existing translations and sources, translates with your terms, and reviews every language against what your app is. You wait; nothing is asked of you.
Translating 4 languages. Reviewing each language.
Your translations arrive
The completed translations land in your project, the way you chose in step 4: through your build system on GitHub or GitLab as a change you approve, or as files your agent writes into the project.
Translations are ready for all 4 languages and delivered to your project.
Your app, fully translated and ready to ship
Every language is reviewed and in your project. From here on, PTC can keep your app translated as it changes, and you pay only for the new texts: the section after the steps explains it.
What you need to start

A coding agent that works in your repository
Claude Code or Codex, connected to PTC with the one-line command from your agent token page. The agent runs PTC's small command-line tool inside your repository, so it must be allowed to run commands there.

Your texts in resource files
Rails locale files, PO and POT files, i18next JSON, Apple's string catalogs or Android XML, where your framework keeps them. The list of frameworks is below.

GitHub or GitLab, for automatic delivery
With your repository on GitHub or GitLab, every change comes back translated by itself. Without one, your agent runs one command and PTC writes the translations into the project.

A PTC account, free trial included
The trial covers 20,000 words into 2 languages for 30 days, with no credit card. The price of any paid work is shown before you say yes.
After the setup: continuous localization, billed only for the changes
The steps above are a one-time setup. Once it is done, and if you allow it, PTC takes over: it finds the new and changed texts in your code, translates and reviews them, and delivers them into your project the same way as the first time, in minutes. You run nothing and remember nothing.
The bill covers the delta alone. A one-line fix is billed as a few words; the texts you did not touch are not translated again and not billed again, and the price of each run is shown before any paid work.
PTC is your translation system working in the background: it knows your product, your terms and your translator notes, and applies them to every new text without being told twice.
Compatible frameworks
PTC finds and translates the resource files, the files that hold your app's texts, of these kinds of project:
- Ruby on Rails apps with YAML locale files.
- WordPress plugins and themes, and any project that uses gettext PO and POT files.
- JavaScript web apps with i18next JSON files.
- iOS apps with Apple's string files and string catalogs (the
.stringsand.xcstringsfiles Xcode keeps your texts in). - Android apps with XML string resources.
Compatible coding agents
PTC's MCP server connects to these agents. Your agent token page gives the one-line command for each.
- Claude Code
- Codex
- Cursor
- Any other MCP client
Pay as you go, per word, after a free trial
No subscription, no per-user seats, no minimum. You see the price before any paid work, computed from PTC's own scan of your files, and translation starts on your yes. The free trial covers 20,000 words into 2 languages for 30 days, with no credit card.
Changing a glossary term later re-translates the texts that use it at no charge. So does a correction the reviewers find. PTC translations are covered by the 60-day Translation Quality Guarantee: a translation that is wrong is fixed or refunded within 60 days. Prices are on the pricing page.
Why an LLM alone is not enough: consistent terms, context and a check
An agent working alone translates one term three ways, guesses where a text is unclear, and nobody checks its work. With PTC you get:
- One term, one translation. Your glossary is settled before translation, from your existing translations and sources; you are asked only where they disagree.
- Translations that fit the screen. Your agent reads where each unclear text appears and leaves a translator note that stays with it for every language.
- A check on every language before delivery. PTC reviews each translation against your app's description and glossary and fixes what the review finds.
- Proof of what the agent did. “Done” means PTC verified the step against your files, not that the agent said so.
- Your work kept. Translations you already ship are reused, and every change to your code goes through your agent, where you see it.
Get started with PTC's MCP server
Create your account, open your agent token page and paste the one-line command into your agent. The free trial covers 20,000 words into 2 languages for 30 days, with no credit card.
New to PTC?
Using PTC already?
- The getting-started page has the exact commands for your first prompt.
- The MCP server reference lists what your agent connects to and what it needs.
- How we translate WPML into 21 languages with PTC shows the time it took and what it cost.