Get the plugin
WP MCP/Integrations/Multilingual

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.

list-languagesget-post-translationsset-post-languagelink-post-translations

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.

wpmcp, wpml

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.

Point your AI at WPML.

Release notes, straight to your inbox.

One email per release, what shipped, what's verified, what's production-only. No drip campaigns. Unsubscribe in one click.