Multilingual integration
MCP for WPML
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.
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
Just ask.
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 real calls.
list-languages(), WPML languages in the neutral shape
link-post-translations({ translations: { en: 21, de: 22 } })
Frequently asked
Questions, answered.
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.
More integrations
MCP for Polylang
FreeManage multilingual content and translation links over MCP, free.
MCP for TranslatePress
FreeRead and write TranslatePress string translations over MCP, marked human reviewed, every change reversible.
MCP for Elementor
ProDeep Elementor page-building from a curated 44-widget catalog, plus global colors and fonts, validated and reversible.
MCP for Gutenberg
FreeSurgical block-editor editing by index path, free, no page builder required.
MCP for Bricks
ProRead and write Bricks Builder content over MCP, a page builder most MCP tools can't touch.
MCP for Divi
ProRead and write Divi content over MCP, builder-aware, snapshotted, reversible.