Multilingual integration

MCP for TranslatePress

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.

Get the free plugin Read the docs

plugin-data-readplugin-data-write

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

Just ask.

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 real calls.

wpmcp, translatepress

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

Frequently asked

Questions, answered.

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.

More integrations