An agent can list and inspect the site's configured translation languages, add, update, remove or set the default language, turn automatic translation on, and set the TranslatePress license key, effectively managing the multilingual setup end to end.
View TranslatePress on WordPress.org
Needs WordPress 6.9 or newer with the Abilities API and TranslatePress active. Every ability checks manage_options, so only a connected user with that capability can list, add, update, remove or set languages, or manage the license key and automatic translation setting.
Grouped by what each one can change. Every one starts off until you enable it.
Lists the languages currently configured on the site.
Lists the language codes TranslatePress can add.
Adds a new language to the site's translation configuration.
Sets the TranslatePress license key.
Turns on automatic machine translation for the site.
Removes a language from the site's translation configuration.
Updates settings for an existing translation language.
Sets which configured language is the site's default.
No abilities match that search.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. TranslatePress registers its own abilities; this plugin discovers and governs them.
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Every ability from TranslatePress starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Yes. TranslatePress registers eight abilities through the real wp_register_ability() call, guarded by a function_exists/class_exists check, so the Bridge finds them in the core registry and can wrap any of them once enabled.
Yes, unconditionally, once TranslatePress is active. Nothing else has to be configured for the Bridge to discover them.
Needs WordPress 6.9 or newer with the Abilities API and TranslatePress active. Every ability checks manage_options, so only a connected user with that capability can list, add, update, remove or set languages, or manage the license key and automatic translation setting.
An agent can translate post content, taxonomy terms, ACF options, and Gutenberg blocks into configured languages, check translation status and progress, and drive a client-side translate/apply workflow field by field.
Verified from TranslatePress's own free wordpress.org code on 28 September 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, Cozmoslabs or TranslatePress. Back to the full directory.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.