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.
View SlyTranslate on WordPress.org
Needs WordPress 6.9 or newer with SlyTranslate active. Most abilities are gated by the plugin's own translation-access capability check, while translate-options and configure need manage_options and translate-terms needs manage_categories.
8 abilities (get-languages, get-translation-status, get-untranslated, get-translatable-fields, get-progress, get-available-models, prepare-client-translation, prepare-client-translation-bulk) declare 'readonly' => true and are read. translate-text, translate-blocks, save-additional-prompt, and configure declare only 'idempotent' => true with no destructive key, and set-post-language, translate-content, translate-content-bulk, translate-options, translate-terms, cancel-translation, apply-client-translation, and apply-client-translation-bulk carry no annotations array at all, so per the rule (no explicit destructive:false means destructive) all 12 of those are destructive, including translate-text and translate-content.
Grouped by what each one can change. Every one starts off until you enable it.
Lists the languages configured for AI translation.
Returns whether a post has been translated and into which languages.
Lists content that has not yet been translated.
Lists which meta fields a translate-content call would touch, including ACF-resolved ones.
Reports the current phase of a running translation.
Lists the AI models available for translation.
Splits a post's fields into translation units for a client-side workflow.
Splits multiple posts' fields into translation units.
Sets which language a post is written in.
Translates a plain text string.
Translates a post's content, title, and excerpt.
Translates multiple posts at once.
Translates values on an ACF options page.
Translates the names and descriptions of taxonomy terms.
Translates the text inside Gutenberg blocks.
Cancels a translation in progress.
Saves an extra instruction prompt for the translator.
Sets which meta keys to translate, clear, or exclude.
Writes client-translated units back onto a post.
Writes client-translated units back onto multiple posts.
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. SlyTranslate 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 SlyTranslate 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. Its 20 abilities are registered in the core Abilities API with no mcp.public requirement, so the Bridge can discover and wrap any of them.
set-post-language only registers when the active translation adapter (or no adapter yet, fail-open) supports the CAPABILITY_SET_POST_LANGUAGE mutation capability. translate-options only registers when ACF is active with options pages available (acf_get_options_pages, acf_get_field_groups, acf_get_fields all exist). translate-terms only registers when the active adapter is Polylang and Polylang exposes pll_get_term, pll_set_term_language, and pll_save_term_translations.
Needs WordPress 6.9 or newer with SlyTranslate active. Most abilities are gated by the plugin's own translation-access capability check, while translate-options and configure need manage_options and translate-terms needs manage_categories.
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.
Verified from SlyTranslate'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, Timon or SlyTranslate. 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.