Multilingual integration
GTranslate MCP
GTranslate keeps its settings in a single GTranslate option. gtranslate-get-settings on the plugin-data pair returns the default language, the widget look, the dropdown language list, the flag language list, the languages the current look actually shows, whether a paid GTranslate plan is set and whether writes are enabled. gtranslate-set-languages replaces the dropdown list, the flag list or both. Every code is checked against GTranslate's own language list, each list must keep the default language the way GTranslate's settings screen requires, and a call that would change nothing is refused. The write is snapshotted on the GTranslate option, so rollback-operation puts the previous lists back exactly, and it returns a reminder to check the switcher on the front end. Writes are off until a site opts in with the wpmcp_enable_translation_settings_write filter or the GTranslate language settings switch in WP MCP's opt-in settings. Both ops run at manage_options. GTranslate has no URL exclusion setting: content is kept untranslated with the notranslate class, and the read says so.
What your AI can do
Real GTranslate operations, every write reversible.
- Read the default language, widget look and both language lists
- See which languages the current switcher look really shows
- Replace the dropdown or flag language list (opt-in)
- Roll a language change back exactly
Example prompts
Example GTranslate prompts.
Which languages does the GTranslate switcher show visitors right now?
Add Portuguese and Japanese to the GTranslate dropdown.
Trim the flag list to English, Spanish and French.
Under the hood
The GTranslate calls, under the hood.
plugin-data-read({ operation: "gtranslate-get-settings" }), Pro; includes the languages the current look shows
plugin-data-write({ operation: "gtranslate-set-languages", args: { dropdown_languages: ["en", "es", "pt", "ja"] } }), Pro; opt-in; option snapshot
Part of WP MCP Pro
The GTranslate integration is part of WP MCP Pro.
One Pro licence unlocks the GTranslate tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.
Frequently asked
GTranslate MCP: questions, answered.
What stops the agent setting a language code GTranslate does not know?
gtranslate-set-languages checks every code against GTranslate's own language list and refuses unknown_language, listing the valid codes. It also refuses a list that leaves out the default language, and a call that changes nothing.
With GTranslate, can the agent exclude pages from translation?
GTranslate has no URL exclusion setting to change. Content inside an element with the notranslate class stays untranslated, and the read reports that.
In GTranslate, how do I turn the write on, and undo it?
Enable it with the wpmcp_enable_translation_settings_write filter or the GTranslate language settings switch in WP MCP's opt-in settings. Each write snapshots the GTranslate option first, so rollback-operation restores the earlier lists.
Related integrations
More integrations for the same agent.
MCP for Weglot
ProMultilingual, 1 tools.
MCP for TranslatePress
FreeMultilingual, 2 tools.
MCP for WPML
FreeMultilingual, 4 tools.
MCP for Polylang
FreeMultilingual, 4 tools.
MCP for Elementor
ProPage builders, 14 tools.
MCP for Gutenberg
FreePage builders, 4 tools.
Browse the full Integrations hub, or read more on the WordPress MCP plugin.