The useful distinction
A translation relationship is more than a matching link
Polylang’s language model gives an AI assistant the context to tell a complete relationship from a guessed one.
Start with language identity
Read language status, available languages, translatable types, and site presentation from Polylang before interpreting a post or term relationship.
Read the sibling set
Open post and term Translation Sets, resolve a translation, and look up registered strings so the assistant can distinguish a known relationship from a missing or inconsistent one.
Measure before you repair
Use post and term coverage audits and a translation graph audit to show where the language model is complete, incomplete, or inconsistent.
A focused fit
Choose this when Polylang relationships are the problem
The add-on fits a multilingual WordPress site where the question is the integrity of a translation relationship, not a general content task.
Polylang is already authoritative
The site uses Polylang to define language identity and translation relationships.
The decision needs evidence
You need to know which posts or terms lack siblings, whether coverage is complete, or whether the translation graph contains an inconsistency.
The repair has a defined boundary
A post or term needs a specific language or relationship change while its existing translation siblings remain part of the expected state.
Authority and access
The assistant works inside Polylang’s authority
Polylang remains authoritative for languages and translation relationships. This add-on does not take ownership of content editing, menus, URL migration, SEO, language administration, or generic string editing.
Every ability requires authenticated editorial access. Graph writes also require manage_options and the matching post, term, object, or taxonomy permission.
Recommended operator practice
Turn a translation question into a verified decision
Each registered operation performs only its documented job. Keep the reader’s decision visible from the first state check through the final readback.
1
Confirm the working context
Check that Polylang is active, the MCP and WordPress Abilities components are available, and the authenticated user has the required editorial access.
2
Establish the current state
Review language status, available languages, translatable types, and site presentation. Then inspect posts, terms, Translation Sets, translation resolution, registered-string lookup, coverage, and translation-graph integrity.
3
Plan one relationship
Use post or term translation planning to compare the expected state with the existing siblings and prepare the smallest explicit relationship change.
4
Apply with proof
Start with a dry-run, compare the exact expected state, require exact confirmation, preserve existing siblings, and read back the result. A failed Translation Set verification attempts to restore the prior sets.
What the reader gets
The result is a decision you can defend
An audit should leave the operator with a specific answer: which language a post or term belongs to, which siblings are present, where coverage is incomplete, or whether graph integrity needs attention. That answer is useful even when no write is needed.
Where a relationship is needed, the planned state and readback make the before and after visible. Existing siblings remain part of the decision, and a failed Translation Set verification attempts to restore the prior sets. The assistant returns a defined result instead of a guessed link.
Requirements
Use the documented runtime stack
These named components provide the runtime, authority, ability registration, and authenticated MCP transport the plugin requires.
6.9 or later
WordPress 6.9Provides the WordPress runtime and native language-related content APIs.
8.0 or later
PHP 8.0Provides the minimum PHP runtime for the add-on.
Active and available
WordPress Abilities APIRegisters the authenticated abilities exposed by the add-on.
Available as the language and Translation Set authority
Polylang developer documentationDefines the language and Translation Set authority used by the add-on.
Available for authenticated MCP transport
WordPress MCP AdapterTransports the registered WordPress abilities to authenticated AI clients.
Next step
Put Polylang relationship maintenance within reach
Download MCP Abilities – Polylang if your WordPress site uses Polylang and an AI assistant needs to determine whether translation relationships are complete or maintain a specific post or term relationship. You receive the stable plugin ZIP for that focused WordPress capability.