SlyTranslate brings practical AI translation to WordPress. It is built for teams that need translation directly in editing workflows and also want the same workflows available through REST and MCP automation.<\/p>\n\n
Why this plugin?<\/strong><\/p>\n\n Use SlyTranslate when you need one consistent translation workflow for:<\/p>\n\n Internal flow (short):<\/strong><\/p>\n\n Abilities:<\/strong><\/p>\n\n MCP Call Flow:<\/strong><\/p>\n\n Requirements:<\/strong><\/p>\n\n Supported plugins:<\/strong><\/p>\n\n Supported model profiles:<\/strong><\/p>\n\n Any LLM available through a WordPress AI connector works out of the box \u2014 no special configuration needed. The following model families additionally have dedicated built-in profiles that tune prompt style, chunking, and retry behavior for better results:<\/p>\n\n Via WordPress Plugin Directory (recommended):<\/strong><\/p>\n\n Manual installation:<\/strong><\/p>\n\n Yes, for text and block translation ( In WordPress Settings > Connectors, not inside SlyTranslate.<\/p><\/dd>\n Yes. Use Yes. On singular pages opened with In the list-table dialog, Overwrite existing translation<\/strong> is off by default. If a translation already exists, you must enable overwrite and confirm before the translation starts.<\/p><\/dd>\n Yes, when the active language plugin supports language mutation (currently Polylang). In that case Use Some external WordPress MCP adapter wrappers expose a flatter Any LLM from a WordPress AI connector works without configuration. Built-in dedicated profiles exist for: TranslateGemma, TowerInstruct, Salamandra, Nvidia Nemotron, Qwen 3.x, GLM-4.6v, Gemma 4, Phi-4, EuroLLM, Llama 3.1-8B, SauerkrautLM, Ministral-3, and Ministral-8B. Additional profiles can be registered via the \n
\n
wp_ai_client_prompt()<\/code>.<\/li>\n\/wp-abilities\/v1\/<\/code>) and MCP discovery.<\/li>\ndirect_api_url<\/code> supports OpenAI-compatible endpoints for model-specific payload needs.<\/li>\nai-translate\/get-languages: List languages exposed by the active language plugin |\nai-translate\/get-translation-status: Show translation status for a content item, including `source_language` and `single_entry_mode` |\nai-translate\/set-post-language: Change the language assignment of an existing content item (only exposed when supported, e.g. Polylang) |\nai-translate\/get-untranslated: Find content still missing a target translation |\nai-translate\/translate-text: Translate arbitrary text |\nai-translate\/translate-blocks: Translate serialized Gutenberg blocks |\nai-translate\/translate-content: Create or update one translated post\/page\/CPT entry (call `get-translation-status` first; optional `source_language` + `overwrite`) |\nai-translate\/translate-content-bulk: Bulk-translate multiple entries (supports optional `source_language` and `overwrite`) |\nai-translate\/get-progress: Return live progress for a running translation |\nai-translate\/cancel-translation: Cancel a running translation |\nai-translate\/get-available-models: List models from configured connectors |\nai-translate\/save-additional-prompt: Save per-user additional instructions |\nai-translate\/configure: Read or update persistent plugin settings |\n<\/code><\/pre>\n\n\n
ai-translate\/get-languages<\/code> first when the correct target language code is unknown.<\/li>\nai-translate\/get-translation-status<\/code> before ai-translate\/translate-content<\/code> to inspect source_language<\/code>, single_entry_mode<\/code>, and whether the target language already exists.<\/li>\nsource_language<\/code> unless you intentionally pin a source variant. In single-entry adapters, reuse get-translation-status.source_language<\/code> when you do pin it.<\/li>\noverwrite=true<\/code> only when status or prior context shows that the target language already exists.<\/li>\ntranslated_post_id<\/code> to equal source_post_id<\/code> in single-entry adapters such as WP Multilang, WPGlobus, and TranslatePress. In multi-post adapters such as Polylang, the translated item uses a sibling post ID.<\/li>\n<\/ul>\n\n\n
\n
\n
chat_template_kwargs<\/code> support through direct_api_url<\/code><\/li>\n\n
\n
slytranslate<\/code> directory to \/wp-content\/plugins\/<\/code>.<\/li>\n\n
Does this work without a language plugin?<\/h3><\/dt>\n
translate-text<\/code>, translate-blocks<\/code>, inline selected-text workflow). Content translation workflows require a supported language plugin (Polylang, WP Multilang, WPGlobus, or TranslatePress Multilingual).<\/p><\/dd>\nWhere are API keys configured?<\/h3><\/dt>\n
Can I use bulk translation from post\/page lists?<\/h3><\/dt>\n
translate-content-bulk<\/code> through abilities or the wp-admin list-table translation UI.<\/p><\/dd>\nDoes this work inside the TranslatePress visual editor?<\/h3><\/dt>\n
?trp-edit-translation=true<\/code>, SlyTranslate adds a sidebar panel in the TranslatePress editor so you can translate the current page with the same model, overwrite, progress, and cancel controls used elsewhere in the plugin.<\/p><\/dd>\nHow does overwriting existing translations work?<\/h3><\/dt>\n
Can I change the language assignment of an existing post without running translation?<\/h3><\/dt>\n
ai-translate\/set-post-language<\/code> is exposed and can be called with post_id<\/code> and target_language<\/code>. By default language conflicts fail with language_conflict<\/code>; use force<\/code> to opt in, and pass relink=true<\/code> when translation relations should be rewritten. In WP Multilang mode this ability is not exposed.<\/p><\/dd>\nHow do I control prompts and style?<\/h3><\/dt>\n
ai-translate\/configure<\/code> for persistent defaults and additional_prompt<\/code> on translate-*<\/code> abilities for per-request instructions.<\/p><\/dd>\nWhy can MCP execute-ability still fail after discovery looks correct?<\/h3><\/dt>\n
execute-ability<\/code> signature than they actually accept. If discover-abilities<\/code> or get-ability-info<\/code> shows the correct SlyTranslate schema but execute-ability<\/code> still errors about a missing parameters<\/code> wrapper, investigate the external adapter layer first. SlyTranslate controls the registered ability names, descriptions, and schemas, not that wrapper surface.<\/p><\/dd>\nWhich model-specific profiles are supported?<\/h3><\/dt>\n
slytranslate_model_profiles<\/code> filter.<\/p><\/dd>\n\n<\/dl>","raw_excerpt":"AI translation abilities for WordPress using native AI Connectors, the AI Client and Abilities API for automated text and content translation.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/301990","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=301990"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/timonf"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=301990"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=301990"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=301990"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=301990"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=301990"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=301990"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}