The useful distinction
A translation relationship needs context, not a guessed link
Polylang gives the assistant the language context needed to tell a complete relationship from a missing or inconsistent one.
Start with the Language Registry
Read language status, available languages, translatable types, and site presentation before interpreting a post or term relationship.
Read post and term Translation Sets
List the relevant posts or terms, open their Translation Sets, resolve a translation, and look up registered strings to distinguish a known sibling from a missing or inconsistent relationship.
Measure translation coverage
Run 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 need evidence
This 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
Polylang defines the site’s language identity and translation relationships.
The decision needs evidence
You need to know which posts or terms lack siblings, whether translation coverage is complete, or whether the translation graph contains an inconsistency.
The change has a defined boundary
A post or term needs a specific language or relationship change while its existing Translation Set siblings remain part of the expected state.
Authority and access
Polylang remains the relationship 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 operation requires authenticated editorial access. Changes to the translation graph also require manage_options and the matching post, term, object, or taxonomy permission.
Recommended operator practice
Turn a translation question into a verified decision
Keep the reader’s decision visible from the first state check through the final readback; each operation does only its documented job.
1
Confirm the working context
Check that Polylang is active, WordPress Abilities and the MCP transport are available, and the authenticated user has the required editorial access.
2
Establish the current state
Inspect language status, available languages, translatable types, and site presentation, then list posts and terms and review their Translation Sets, translation resolution, registered-string lookup, coverage, and graph integrity.
3
Plan one relationship
Use post or term translation planning to compare the expected language and sibling state, then prepare the smallest explicit relationship change.
4
Apply with proof
Start with a dry-run, compare the exact expected state, require exact confirmation, and preserve existing siblings when setting a post or term language or saving post or term translations. Read back the result; failed Translation Set verification attempts to restore the prior sets.
What the reader gets
Know what changed, and what still needs attention
An audit can 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 remains useful when no write is needed.
When a relationship change is needed, the planned state and readback show the before and after. Existing siblings remain part of the decision, and failed Translation Set verification attempts to restore the prior sets.
Dependencies
The runtime stack this add-on needs
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
Get a focused answer about one translation relationship
Download MCP Abilities – Polylang when a WordPress site using Polylang needs an authenticated AI assistant to inspect translation coverage or maintain one specific post or term relationship. The stable plugin ZIP gives that assistant the focused WordPress capability for the decision.