Multilingual integration
TranslatePress AI agent tool reference
TranslatePress keeps string translations in a dictionary table per language. WP MCP reads and writes them on the plugin-data pair: translatepress-list-languages lists the site's languages, translatepress-get-strings pages through a language's strings filtered by a search and by status (not translated, machine translated, human reviewed), and translatepress-update-strings sets translations on existing rows by id, sanitized the way TranslatePress's own editor does it, and marks them human reviewed. Rows are created by TranslatePress when it meets a string, so the write never inserts one. Every write is snapshotted as a row image, and access needs the capability TranslatePress gates its translation editor behind.
TranslatePress in plain language: TranslatePress MCP.
In practice
How TranslatePress work goes with an agent.
TranslatePress does not translate posts. It translates strings: every phrase it meets on a rendered page becomes a row in a per-language dictionary table, with the original text, the translation and a status of not translated, machine translated or human reviewed. That is the data an agent works on. The usual jobs are counting what is still missing in a language, reviewing the machine output that automatic translation left behind, and filling in navigation, button and checkout strings. WP MCP reads those rows by status and search, and writes translations back by row id.
How many Spanish strings still have no translation, and what are the ten most visible ones?
Runs translatepress-list-languages to confirm es_ES is a translation language, then translatepress-get-strings with status 0 and a page size of 10. Read only, nothing is snapshotted because nothing is written.
Go through the machine-translated German strings that contain "Warenkorb" and tidy the wording.
Runs translatepress-get-strings with status 1 and a search on the original text, then translatepress-update-strings with the corrected rows. The affected rows are snapshotted as a row image first and each rewritten row is marked human reviewed.
Clear the French translation of string 482, it is wrong and I want it retranslated.
Runs translatepress-update-strings with an empty translated value, which sets the row back to not translated. The row is snapshotted before the change, so rollback-operation restores the old text and status.
Add a new string "Free shipping over 50" to the Italian dictionary.
Refused. translatepress-update-strings only changes rows that exist, and an unknown id comes back as unknown_string. TranslatePress adds a row itself the first time a page shows the string, so visit the page, then ask again.
What your AI can do
Real TranslatePress operations, every write reversible.
- List the site's TranslatePress languages
- Find untranslated or machine-translated strings in a language
- Write translations for existing strings, marked human reviewed
- Roll back any translation write exactly
Example prompts
Example TranslatePress prompts.
How many Spanish strings are still untranslated?
Review the machine-translated German strings on the checkout and fix the awkward ones.
Translate the untranslated French navigation strings.
Under the hood
The TranslatePress calls, under the hood.
plugin-data-read({ operation: "translatepress-get-strings", args: { language: "es_ES", status: 0 } }), 0 = not translated
plugin-data-write({ operation: "translatepress-update-strings", args: { language: "es_ES", translations: [{ id: 91, translated: "…" }] } }), snapshotted
Safety and access
What can be undone on TranslatePress, and what costs what.
Recoverable on TranslatePress
- Every translatepress-update-strings call is snapshotted as an image of the dictionary rows it names.
- rollback-operation puts the previous translation and status back exactly.
- A cleared translation (empty value) is restored the same way.
TranslatePress limits and opt-ins
- Strings cannot be created. Only existing dictionary rows by id are updated, at most 100 per call, and each id may appear once per call.
- The default language has no dictionary, so only translation languages can be read or written.
- A language whose dictionary table does not exist yet is refused with dictionary_missing until TranslatePress creates it on the first visit.
- Access needs the capability TranslatePress gates its translation editor behind, which is manage_options unless a site changes it with trp_translating_capability.
Free or Pro: TranslatePress support is free. List languages, read strings and update translations are all in the free plugin, with no Pro licence involved, and there is no opt-in filter to flip before the write works. The one gate is TranslatePress's own editor capability. Pro does not add TranslatePress operations; the page-level translation workflow in Pro (find-missing-translations, create-translation and the page text pair) targets Polylang and WPML, which translate whole posts rather than strings.
In the free plugin
The TranslatePress integration is in the free plugin.
The core TranslatePress tools ship in the free, GPL plugin with the full snapshot and undo engine, and no trial clock. Pro adds 133 more tools, including Elementor deep editing, the other page builders, the forms adapter pack and, for some integrations, extra operations. The pricing page lists what each tier includes.
Frequently asked
TranslatePress MCP: questions, answered.
With TranslatePress, can the agent add new strings?
No. TranslatePress creates dictionary rows itself when it meets a string on the site, so the write only fills in translations for rows that already exist.
What do the status numbers 0, 1 and 2 mean?
They are TranslatePress's own values: 0 is not translated, 1 is machine translated and 2 is human reviewed. translatepress-get-strings can filter by any of them. A non-empty write sets status 2, and an empty write sets status 0, so reviewed strings stay distinguishable from automatic ones.
Is the text sanitized before it is saved?
Yes. Translations are cleaned the way TranslatePress's own editor cleans them, using its trp_sanitize_string function when present and a script-stripping wp_kses_post fallback otherwise. A value that is a bare URL is passed through esc_url_raw. Unsafe markup does not reach the dictionary table.
Will TranslatePress show the change immediately?
Yes, in practice. After the rows are written WP MCP flushes TranslatePress's cached lookups, so the next page view reads the new text. A full-page cache or CDN in front of the site can still hold the old HTML, and that is outside what the plugin controls.
Can I page through a large dictionary?
Yes. translatepress-get-strings takes page and per_page, up to 100 rows per page, and returns a total plus each row's id, original, translated text, status and block type. Rows come back in id order, so paging is stable while you work through a language.
Is there an AI agent for TranslatePress?
Yes, through WP MCP rather than TranslatePress itself. An agent you choose, such as Claude or Cursor, can list the site's TranslatePress languages. WP MCP is a separate plugin, not a built-in AI feature of TranslatePress. On the undo side: Every translatepress-update-strings call is snapshotted as an image of the dictionary rows it names.
Related integrations
More integrations for the same agent.
MCP for Polylang
FreeMultilingual, 4 tools.
MCP for WPML
FreeMultilingual, 4 tools.
MCP for Weglot
ProMultilingual, 1 tools.
MCP for GTranslate
ProMultilingual, 2 tools.
MCP for Elementor
ProPage builders, 14 tools.
MCP for Gutenberg
FreePage builders, 4 tools.
Browse the full Integrations hub, or read more on TranslatePress MCP and the WordPress MCP plugin.