Get started: localize your app with PTC

STEP 1

Open your agent page

Sign up to PTC and open the Connect your agent to PTC page. Your token is already there.

STEP 2

Add PTC to your agent

claude mcp add --transport http ptc https://app.ptc.wpml.org/mcp \
  --header "Authorization: Bearer <your agent token>"

// .cursor/mcp.json
{ "mcpServers": { "ptc": { "url": "https://app.ptc.wpml.org/mcp",
  "headers": { "Authorization": "Bearer <your agent token>" } } } }

export PTC_API_TOKEN='<your agent token>'
codex mcp add ptc --url https://app.ptc.wpml.org/mcp --bearer-token-env-var PTC_API_TOKEN

The page in PTC shows the same snippet with your token filled in, also for VS Code and other agents. Copy it from there.

STEP 3

Give your agent one prompt

Set up PTC translations.

That is the whole instruction. Name the languages in the prompt if you like, and PTC will not ask for them again.

PTC works through its command-line tool, which your agent installs in your repository. The agent asks you once to run ptc auth login and approve the sign-in in your browser.

STEP 4

Answer a few questions

PTC asks only what the code cannot tell it. Answer in the chat with your agent:

• Which languages to translate into.
• Your existing translations: use them, or translate everything again.
• Source improvements: whether PTC may propose fixes to texts that translate badly, such as sentences glued from fragments or missing plurals.
• How translations arrive: as pull or merge requests from your own CI, or as files your agent writes into your working folder.
• The price: PTC shows an estimate and waits for your yes. On the free trial there is nothing to confirm while the trial covers the work.

STEP 5

Get ready-to-publish translations

PTC guides your agent through the preparation:

• Finds your resource files (JSON, YAML and gettext PO files).
• Explains unclear texts to PTC, with the code around them.
• Writes your product description and imports your glossary.
• Applies the source fixes you approved.

Then PTC translates and reviews every language. With CI, each push sends only the new and changed texts, and the translations come back as a pull or merge request.

STEP 1

Upload your resource files or connect Git

Choose One-off to upload your files by hand, or Continuous to connect a GitLab, GitHub or Bitbucket repository and pick the branch PTC watches.

STEP 2

Choose the original and target languages

Pick the language your texts are written in and the languages you need. During the trial you can translate into two languages.

STEP 3

Choose the resource files to translate

With Git, select the files PTC translates and how the translated files are named. PTC reads JSON, PO and POT, XLIFF, YAML, Properties, Android XML, iOS Strings, Stringsdict and Property List files, and Magento CSV.

STEP 4

Tell PTC about your product

Say what your product is called, what it does and who it is for. PTC fills these in from your files for you to check. You can also add your existing translations and your glossary. Then click Translate.

STEP 5

Get the completed translations

After an upload, click Download translations. With Git, PTC opens a pull or merge request with every language, and translates new and changed texts automatically each time you push.