Integration · MCP

WPML + MCP: let AI manage multilingual content and translation status

Connect WPML to Claude, Cursor or ChatGPT through NibWP's MCP server. The AI reads languages and translation status across every post type, creates and links translations, and fixes content sitting in the wrong language — the multilingual housekeeping job, by prompt.

Get the Bundle →See pricing
WPML + MCP: AI operating WPML through NibWP

Multilingual sites drift: a new page published in one language only, a product whose German translation is two versions behind, posts assigned to the wrong language, a translation that exists but is not linked. WPML tracks all of it, and almost nobody has time to read the dashboard. NibWP exposes WPML as typed MCP tools — list and read languages and translation status, create translations, update links and assignments — so the gaps are found and filled by prompt.

Ask what is untranslated in French and get a real list. Create the missing translations from the source content as drafts for review. Link a translation that was created by hand. Fix the three posts that were published under the wrong language. Plan first, log after.

WPML is one of the 45+ integrations inside NibWP's WordPress MCP server — 4 typed WPML tools on top of 190+ WordPress tools. The full tool reference lives on the WPML integration page; this page is about what those tools let you do.

What AI can do in WPML

Translation status

Which posts, pages and products are translated into which languages, and which are behind the source.

Create translations

Create the missing translation of a post — drafted from the source, linked to it — for review in WPML as usual.

Link and assign

Link a manually created translation to its original, or move content to the right language.

Audits

Untranslated, outdated or mis-assigned content across every post type, found in one read.

Bulk operations

Create or update translations across a category or post type in one planned run.

Automation

Chain 'find gaps → draft → link' into a repeatable run after every content push.

The WPML tools NibWP exposes

Every WPML capability is a typed MCP tool with a schema the AI client can read, so it calls the right thing with the right arguments instead of guessing at your database. Read tools are free to explore; write tools go through the approval flow.

  • nibwp/wpml-manage — Manage WPML multilingual content.

Example prompts

Plain English is the interface. These are the kinds of requests agencies run against WPML every day:

  • “Which pages have no French translation?”
  • “Create German drafts for every Guide that has none, translated from the English source, for review.”
  • “Link post 4412 as the Spanish translation of post 4401.”
  • “Which products have a translation older than the source?”
  • “Move these three posts from German to Dutch — they were published in the wrong language.”

How it works with WPML

There is no new dashboard to learn. You describe an outcome, NibWP plans it, and you approve before anything is written.

  1. Connect — install NibWP, connect Claude, Cursor, ChatGPT or any MCP client. WPML is detected automatically and its tools appear in the client.
  2. Describe — ask what is missing or describe the change. NibWP reads languages and translation status first and shows the plan — which posts, which languages — before creating anything.
  3. Approve — NibWP shows the plan: which records it will create or change, and what will stay untouched. Nothing happens until you say yes.
  4. Done — it writes real WPML data through the plugin's own APIs and reports back in plain English, with every change in the audit log.

Why not just a generic AI?

A general-purpose assistant can write text about WPML; it cannot safely operate it. The difference is structure, context and control.

A generic assistant

  • Translates text in a chat for you to paste into WPML
  • Cannot see which content is untranslated or outdated
  • Cannot link a translation or fix a language assignment

WPML + NibWP

  • Reads translation status across post types from WPML
  • Creates and links translations through WPML
  • Fixes assignments in bulk with a plan

Safe by default

NibWP is built for agencies running client sites, so control and traceability come first:

  • Nothing is written without your approval — you see the plan first, and you can run in draft mode.
  • Every action is recorded in a full audit trail, per site and per user.
  • It runs on WPML's own functions and APIs — your data stays on your server, nothing is copied to a third-party service.
  • Created translations land as drafts for review; deleting translations is never part of an ordinary connection.

Related integrations

Most sites pair WPML with other plugins NibWP already speaks: TranslatePress + MCP, Weglot + MCP, Yoast + MCP, SEOPress + MCP, WooCommerce + MCP, WordPress + MCP. All of them ship in the same plugin — see pricing for what each plan includes.

FAQ

Questions, answered

Everything about running WPML with NibWP.

Does it need WPML installed?
Yes. Once WPML is active, NibWP detects it and its tools go live in your connected AI client — no configuration needed.
Does it translate the content itself?
It can draft a translation from the source content using your AI client, and creates it in WPML linked to the original as a draft for review. Your existing translators or WPML’s own services can still be used.
Can it fix posts in the wrong language?
Yes. Language assignment and translation links are updated through WPML, so the fix shows up correctly in the admin and on the front end.
Is bulk translation safe?
Runs are planned and shown first, rate-limited, and create drafts rather than publishing — nothing goes live until you approve it.
Do I need a Pro Skill?
No. The WPML integration works on Pro. Pro Skills are for design-to-build builder output.

Close the translation gaps by describing them.

Get the Bundle and let NibWP find, draft and link WPML translations — with an approval step and an audit trail.

Get the Bundle →See pricing