Multilingual integration
MCP for Polylang
Polylang runs multilingual WordPress sites. WP MCP exposes its language and translation model over MCP: list configured languages, read a post's translations, set a post's language, and link posts as translations of each other. It lets an AI agent keep a multilingual site's translation graph consistent while it creates and edits content.
What your AI can do
Real Polylang 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 site configured for?
Set the language of these three new posts to French.
Link the English and French versions of the About page as translations.
Under the hood
The real calls.
get-post-translations({ post_id: 15 }), the translation set
link-post-translations({ translations: { en: 15, fr: 16 } })
Frequently asked
Questions, answered.
Is Polylang support free?
Yes. The four multilingual tools are on the free tier, and the same tools work with WPML when that is the active plugin.
Is Polylang support production-verified?
The Polylang paths are verified against a live Polylang install; CI can't exercise every third-party plugin, and we flag that honestly per release.
More integrations
MCP for TranslatePress
FreeRead and write TranslatePress string translations over MCP, marked human reviewed, every change reversible.
MCP for WPML
FreeList languages, read and link translations, and set a post's language on WPML sites over MCP.
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.