Get the plugin
WP MCP/Integrations/TranslatePress MCP

TranslatePress MCP · Free

TranslatePress MCP: let an AI agent work through your string dictionary.

A TranslatePress MCP server lets an AI agent see which strings in a language are untranslated or only machine translated, and fill them in. WP MCP reads TranslatePress's dictionary by status and search, writes translations back by row id marked human reviewed, and snapshots every row it changes.

Self-hosted · snapshot before every write · one-click undo

What it is

What a TranslatePress MCP server does.

TranslatePress translates strings, not posts. Every phrase it meets on a rendered page becomes a row in a per-language dictionary, with the original, the translation and a status: not translated, machine translated or human reviewed. A TranslatePress MCP server puts that dictionary in front of an agent, which suits the jobs people put off: checkout and button strings, navigation, and reviewing what automatic translation produced.

WP MCP fills in rows TranslatePress has already created and never inserts new ones, so the dictionary holds nothing the site does not show. Translations are sanitized the way TranslatePress's own editor does it, and access needs the capability TranslatePress gates that editor behind, manage_options unless the site changes it.

Read and change

What WP MCP can read and change in TranslatePress.

It can read

  • TranslatePress's default and translation languages
  • Strings in a language, filtered by status and by a search on the original
  • Each string's id, original, translation and status

It can change

  • Write translations for existing strings, marked human reviewed
  • Clear a translation so the string reads as not translated
  • Up to 100 strings per call, snapshotted as row images
plugin-data-readplugin-data-writetranslatepress-list-languagestranslatepress-get-stringstranslatepress-update-stringsrollback-operation

These are the real ability and operation names the agent calls. TheTranslatePress AI agent tool reference page lists the calls in detail.

Example prompts

Three things to ask first.

How many Spanish strings are still untranslated?

Translate the untranslated French navigation and button strings.

Go through the machine-translated Italian strings and fix the awkward ones.

Safety

Every TranslatePress write has a way back.

Every translatepress-update-strings call is snapshotted as an image of exactly the dictionary rows it names, so rollback-operation puts the previous translation and status back, including a translation that was cleared. After a write TranslatePress's cached lookups are flushed; a full-page cache or CDN in front of the site can still hold old HTML.

Snapshot before every write

No tool that writes can skip it. The before-state is saved first, the change is applied second.

One-click undo

Restore a single change with rollback-operation or a whole agent run with rollback-session, from the agent or from wp-admin.

Only rows TranslatePress made

The write never inserts a string. An unknown id comes back as unknown_string, and the default language, which has no dictionary, cannot be written.

Free or Pro

Free.

TranslatePress support is in the free plugin: listing languages, reading strings and writing translations, with no opt-in to flip. WP MCP Pro adds no TranslatePress operations; it adds unlimited snapshot history with an active licence, where the free plugin keeps the last 20, which matters for long review runs.

The free plugin is GPL and has no trial clock. See pricing for what each tier includes.

How to connect

Connect TranslatePress MCP in four steps.

  1. 01
    Install WP MCP

    Upload the free wpmcp plugin and activate it. It needs WordPress 6.9 or newer and PHP 8.1 or newer, and it runs entirely on your own server.

  2. 02
    Check the requirement

    TranslatePress active, with at least one translation language.

  3. 03
    Connect your client

    Add the site to Claude Code, Claude Desktop, Cursor or any MCP client with a WordPress application password, or the WP-CLI stdio bridge locally. OAuth 2.1 with full or read-only access is there too, once the site owner switches it on.

  4. 04
    Ask for the change

    Describe what you want done in TranslatePress. WP MCP snapshots the target, makes the change, and leaves a Restore button next to it in wp-admin.

Step-by-step guides: Claude,Claude Code andCursor. The docscover the safety model in full.

Frequently asked

TranslatePress MCP: questions, answered.

What is TranslatePress MCP?

It is TranslatePress's string dictionary made readable and writable by AI agents over the Model Context Protocol. WP MCP lets Claude, Cursor or any MCP client find untranslated or machine-translated strings and write translations back, each one reversible.

Is TranslatePress MCP free?

Yes. All three TranslatePress operations and the undo engine are in the free plugin.

Is this TranslatePress AI translation?

Not the built-in kind. TranslatePress has its own automatic translation; here the model you connect, such as Claude, reads strings and writes translations into TranslatePress's dictionary. Those writes are marked human reviewed, so read them over before relying on them, and roll back any that miss.

Can the agent add strings that are missing from the dictionary?

No. TranslatePress creates a dictionary row the first time a page shows a string, so visit the page, then ask again. The write fills in rows that already exist.

How do statuses change when the agent writes?

A non-empty write sets status 2, human reviewed, and an empty one sets status 0, not translated. Machine-translated strings keep status 1 until they are rewritten, so filtering by status 1 shows what is still left to review.

Does TranslatePress MCP work with Claude, Claude Code and Cursor?

Yes. Claude Code and Cursor connect to WP MCP over HTTP with a WordPress application password, and Claude Desktop uses the desktop bundle from the WP MCP Connection screen. Clients that can only sign in with OAuth, such as the claude.ai custom connector, need OAuth switched on first with one line in wp-config.php, because it ships off. Once connected, the TranslatePress tools are available in every client the same way.

Point your AI agent at TranslatePress.