TranslatePress

TranslatePress is one of the plugins NIBWP turns into a set of typed, agent-callable tools. Agents understand TranslatePress and can safely operate on it at scale — something no generic AI can do. The moment TranslatePress is active on your site, NIBWP detects it, reads its data model, and exposes it over the same secure MCP endpoint as everything else — no exports, no SQL, no brittle glue scripts. An AI agent connected through NIBWP can then read and operate on TranslatePress data through schema-validated calls that are scoped to your token and recorded in the audit log.

That means the work you used to do by clicking through TranslatePress’s admin — creating records, updating fields, fixing data across hundreds of items — becomes something you can describe in plain language and have an agent carry out, safely and in bulk.

Your i18n layer, programmable

Connecting TranslatePress to your agents changes what is possible with it:

• Structured access — Read and write TranslatePress data through typed, schema-validated calls.
• Bulk operations — Apply changes across hundreds of records in one operation.
• Full management — Create, update and configure TranslatePress — not just read it.
• Dynamic data — Feed TranslatePress values into templates, query loops and other tools.
• Safe by default — Scoped tokens and draft-mode keep large edits under control.
• Zero glue code — No exports, no SQL, no brittle scripts — just protocol.

What it exposes

NIBWP turns TranslatePress into the following typed abilities. Read tools gather context; write tools make changes — always within your token’s scope.

From hours to one prompt

Ask in plain language and the TranslatePress integration turns it into a couple of typed calls — no exports, no SQL, no plugin spelunking.

nibwp/translatepress-manage (run)
✓ applied · 4 tools · 2.1s

You describe the outcome; the agent chooses the right tools, validates each call, and reports what it did. What used to be an afternoon of repetitive admin becomes a single instruction.

What you can build

A few of the things teams do with the TranslatePress integration:

How it stays safe

Capability without control is a liability, so NIBWP wraps every TranslatePress call in the same safety model as the rest of the platform:

• Scoped tokens — grant read-only or write access per agent, and revoke any token independently.
• Draft-mode — keep force-draft on so writes land as drafts you approve before they go live.
• Rate limits — per-token throttling stops a runaway loop from hammering your database.
• Audit log — every call is recorded with status, timing, the calling token and the result.

Getting started

Three steps to put the TranslatePress integration to work:

• Activate TranslatePress — NIBWP only exposes plugins that are active, and detects it automatically.
• Connect an MCP client — Claude, Cursor or your own code, using a scoped application-password token. See the overview.
• Describe the work — ask the agent what you want; it picks the right TranslatePress tools and carries it out under your review.

FAQ