Multilingual integration
WPML AI agent tool reference
The same four multilingual tools that drive Polylang sit in front of WPML when it is the active plugin: list the configured languages, read a post's translation set, set a post's language, and link posts as translations of each other. The tools map a neutral shape onto WPML's own public API, so an agent works the same way on either plugin. One honest caveat: WPML is a paid plugin that is not in the automated test environment, so the WPML paths are written against its public API but have not been exercised against a live WPML install in CI.
WPML in plain language: WPML MCP.
In practice
How WPML work goes with an agent.
WPML keeps its own bookkeeping instead of using plain WordPress taxonomies. Every translatable post is a row in WPML's icl_translations table with a language code and a translation group id, called a trid. The pair of facts an agent needs are which language a post is in and which posts share a trid. WP MCP puts four tools over that model: list the site's languages, read a post's translation set, set a post's language and link posts into one group. The caveat that matters is that WPML is a paid plugin and these paths are not run against a live WPML install in the test suite.
Which languages does this WPML site use, and which one is the default?
Runs list-languages, which returns each language code, its name and an is_default flag from WPML. Read only, so nothing is snapshotted.
Show me what is linked to page 21 so I can see which languages it already has.
Runs get-post-translations for post 21 and returns the translated post id and title keyed by language code. Read only.
Post 90 was imported with no language. Set it to German.
Runs set-post-language, which calls WPML's wpml_set_element_language_details action. The call goes through the safety wrapper, but WPML keeps the language in its own table, so the post snapshot does not guarantee a restore of the old language.
Link pages 21 (English) and 22 (German) as translations of each other.
Runs link-post-translations with [{ language: "en", post_id: 21 }, { language: "de", post_id: 22 }], giving both posts the same trid. Only the first post in the list is snapshotted, so an undo is partial.
What your AI can do
Real WPML operations, every write reversible.
- List the site's configured languages
- Read the translation set for any post
- Set a post's language
- Link posts together as translations
Example prompts
Example WPML prompts.
What languages is this WPML site set up for?
Which of the English pages have no German translation yet?
Link the English and German versions of the Contact page.
Under the hood
The WPML calls, under the hood.
list-languages(), WPML languages in the neutral shape
link-post-translations({ translations: [{ language: "en", post_id: 21 }, { language: "de", post_id: 22 }] })
Safety and access
What can be undone on WPML, and what costs what.
Recoverable on WPML
- set-post-language and link-post-translations both run through the snapshot wrapper and return an operation id.
- Do not rely on that for WPML language or link changes: the snapshot covers the post, not WPML's icl_translations row.
- Check the result with get-post-translations after a change, and fix a wrong link by linking again.
WPML limits and opt-ins
- The WPML code paths use its public hooks and are best-effort. WPML is not installed in the automated test environment, so they have not been exercised against a live WPML.
- On WPML, undoing set-post-language is not guaranteed, because the language lives outside what the post snapshot captures.
- link-post-translations snapshots only the first (primary) post in the list, so rolling it back does not restore the other posts.
Free or Pro: The four tools here, list-languages, get-post-translations, set-post-language and link-post-translations, are free and need only edit_posts. Pro adds the translation workflow on top: find-missing-translations, get-page-text, create-translation and apply-page-text, which work with WPML or Polylang. Pro writes are not behind an opt-in filter, but create-translation only makes a draft and apply-page-text is refused on a stale content hash unless force is set.
In the free plugin
The WPML integration is in the free plugin.
The core WPML 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
WPML MCP: questions, answered.
Is WPML support free?
The four tools listed here are free. The page translation workflow on top of them (find-missing-translations, get-page-text, create-translation and apply-page-text) is a Pro operation.
Is WPML support tested?
The mapping logic is unit-tested with fake data, but WPML itself is not installed in CI, so the live paths are best-effort against its public API. Polylang, by contrast, is verified against a live install. We would rather say that plainly.
What does a trid have to do with this?
In WPML a trid is the group id that makes posts translations of each other. link-post-translations gives every post in the list the same trid. You never pass a trid yourself: you give language and post id pairs and WP MCP does the rest.
Should I trust language changes made through WPML?
Verify them. The write calls WPML's own hook, but the paths are not tested against a live WPML, and rollback of a language change is not guaranteed. Read the post back with get-post-translations after each change, and use a staging copy for bulk re-assignments.
Does this translate my pages for me?
Not in the free tools. They organise language and links. Reading page text, drafting a translated copy and writing text back are the Pro operations get-page-text, create-translation and apply-page-text, and the model doing the translating is the one you connect.
Do WPML string translations and WooCommerce multilingual data work?
Not through this integration. It covers post language and translation groups only. WPML's String Translation tables, taxonomy term translations and its WooCommerce add-on are not read or written by these four tools.
Is there an AI agent for WPML?
Yes, through WP MCP rather than WPML itself. An agent you choose, such as Claude or Cursor, can list the site's configured languages. WP MCP is a separate plugin, not a built-in AI feature of WPML. On the undo side: set-post-language and link-post-translations both run through the snapshot wrapper and return an operation id.
Related integrations
More integrations for the same agent.
MCP for Polylang
FreeMultilingual, 4 tools.
MCP for TranslatePress
FreeMultilingual, 2 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 WPML MCP and the WordPress MCP plugin.