WPML MCP integration

WPML MCP workflows, translated into typed AI tools.

Discover WPML languages and translatable types, read a post's language and translation group, assign a language, join existing posts into one translation group, and resolve a post or term id into another language.

Pro integration profile

WPML

Localization

  • setup health
  • language discovery
  • translatable post types and taxonomies
  • content discovery by language
  • content language and translation group
  • language assignment
  • translation-group linking

Dependency-aware · isolated loading · live schema discovery · licence-gated

Why plugin-aware matters

Use WPML's structure, not a generic shortcut.

A multilingual site combines language configuration, translated routes, exclusions, caches, provider state, canonicals, and hreflang. A localization-aware module makes those related surfaces visible together.

Capability map

What the WPML module can work with

setup healthlanguage discoverytranslatable post types and taxonomiescontent discovery by languagecontent language and translation grouplanguage assignmenttranslation-group linkingcross-language id resolution

This is a human-readable capability map. The live WPPilot ability registry and its input schemas remain authoritative for exact operations and parameters on your installed version.

WPML workflow examples

Three useful ways to put the module to work.

Each example begins with discovery and a read. Writes should follow only after the current structure, dependencies, and review path are clear.

01

Find content that carries no language at all and is therefore invisible to the language switcher

Start by inspecting the relevant setup health state. Ask the agent to show the exact target, intended inputs, affected shared resources, and validation step before it executes.

02

List what exists in one language and see which languages each item is still missing

Start by inspecting the relevant language discovery state. Ask the agent to show the exact target, intended inputs, affected shared resources, and validation step before it executes.

03

Link an existing translation to its source without copying content

Start by inspecting the relevant translatable post types and taxonomies state. Ask the agent to show the exact target, intended inputs, affected shared resources, and validation step before it executes.

A production-minded sequence

From idea to verified WPML change.

The module makes the operation typed. Your workflow still determines whether the outcome is trustworthy.

  1. 1

    Inventory languages and translated URL rules

    Keep the target narrow, record what evidence was checked, and report any external or visual path that remains unverified.

  2. 2

    Review exclusions and switcher settings

    Keep the target narrow, record what evidence was checked, and report any external or visual path that remains unverified.

  3. 3

    Change one configuration layer at a time

    Keep the target narrow, record what evidence was checked, and report any external or visual path that remains unverified.

  4. 4

    Synchronize and inspect cache state

    Keep the target narrow, record what evidence was checked, and report any external or visual path that remains unverified.

  5. 5

    Crawl translated routes and language signals

    Keep the target narrow, record what evidence was checked, and report any external or visual path that remains unverified.

Operating boundary

A module is capability, not blanket permission.

  • The companion plugin or theme must be present where required
  • WPPilot Free and an active Pro licence are required
  • The connected WordPress user's capabilities still apply
  • The safety profile and per-ability status are enforced
  • Critical actions can require confirmation or human approval
  • Live schemas and integration health decide current availability

Specific guardrail

What to watch with WPML

WPML stores language in its own table, so content created without it in mind has no language until one is assigned. The module writes only through WPML's published hooks, does not generate translations, and cannot write string translations because WPML publishes no hook for one. Language and group writes require confirmation.

Where a translation provider is used, keep its keys secret. Validate public translated routes after changes, including exclusions, redirects, canonicals, hreflang, switcher behavior, translation links, and any provider synchronization that applies.

Read the safety checklist →

WPML MCP FAQ

Practical answers before you connect.

Reviewed against the current WPPilot module and client registries on August 10, 2026.

What does the WPML MCP integration do?

Discover WPML languages and translatable types, read a post's language and translation group, assign a language, join existing posts into one translation group, and resolve a post or term id into another language.

Is WPML support included in WPPilot Free?

No. The specialized WPML module is part of WPPilot Pro. WPPilot Free supplies the MCP server, connection, policy, core abilities, diagnostics, and change controls that Pro extends.

Does the WPML module load on every site?

No. WPPilot Pro checks the relevant dependency and licence state. The live integration health and ability registry are the source of truth for the installed site.

Can an AI agent change WPML without review?

Only within the connected WordPress user's capabilities, the active WPPilot safety profile, enabled abilities, and any confirmation or approval requirement. WPML stores language in its own table, so content created without it in mind has no language until one is assigned. The module writes only through WPML's published hooks, does not generate translations, and cannot write string translations because WPML publishes no hook for one. Language and group writes require confirmation.

What should I test after a WPML change?

Where a translation provider is used, keep its keys secret. Validate public translated routes after changes, including exclusions, redirects, canonicals, hreflang, switcher behavior, translation links, and any provider synchronization that applies. A successful tool result is evidence that an operation returned successfully, not proof that every front-end, provider, or production path is correct.

More localization

Explore related WPPilot modules.

Use the category page to compare adjacent workflows, then inspect the dedicated module that matches your installed stack.

Localization

Weglot

Weglot language and translated URL workflows over MCP

Manage Weglot languages, excluded URLs, translated URLs, switcher settings, cache state, cloud synchronization, and core configuration.

language configurationtranslated URLsexcluded URLslanguage switcher settingstranslation cache
Explore Weglot
Localization

Polylang

Polylang content-language and translation linking over MCP

Discover Polylang languages and translated content, inspect or assign a post language, and link translations through confirmation-gated WPPilot Pro abilities.

setup healthlanguage discoverytranslated content discoverycontent language and translation setspost and page language assignment
Explore Polylang

Before the first write

Read first. Change one thing. Then look.

The sequence matters more than the tool. Ask the agent to describe what is already there. Check its answer against the plugin itself. If the description is wrong, stop. Nothing written after that will be right.

Once the description matches, make one small change. Not a batch. One. Then open the plugin and look at the result with your own eyes.

A tool result that says success means the call returned. It does not mean the page is correct. Caches, templates, notifications and front-end styles are all outside what the call can see. WPML stores language in its own table, so content created without it in mind has no language until one is assigned. The module writes only through WPML's published hooks, does not generate translations, and cannot write string translations because WPML publishes no hook for one. Language and group writes require confirmation.

Do the first few sessions on staging. Use a WordPress user created for this connection. Keep the safety profile tight until you have watched a full session in the change ledger. None of that takes long, and it is the difference between a workflow you trust and one you hope about.

Your site · your policy · your AI client

Bring WPML into a controlled AI workflow.

Start with WPPilot Free for the MCP foundation. Add Pro when your work needs WPML-specific structure, plugin-aware skills, memory, or human approvals.