Why this exists. YOOtheme Pro keeps most of what makes a site look the way it does where Joomla's own tools can't read it: the customizer settings sit as one JSON document inside the template style, and a builder page is a layout stored in the article's text. This add-on understands that data, so you can ask in plain language: "Switch the header to the stacked centred layout", "Show me the outline of the About page and change its main headline", or "Why doesn't my colour change show up?"

What the AI can do. 14 tools in 5 groups:

• Status (2): the YOOtheme version, each style and its compiled stylesheet, how many pages and modules use the builder, and a health check.
• Customizer settings (2): read the settings (API keys and passwords come back masked), and change named settings such as header.layout. Everything you don't name stays as it is, a dry run shows the before and after, and the save is refused if someone saved the customizer in the meantime.
• Page builder (5): list the pages built with the builder, read a layout as a short outline or in full, and save a changed layout back to an article or a YOOtheme Builder module.
• Library (3): list YOOtheme's Templates in the order they're tried and switch one on or off, and list My Layouts and saved styles.
• Elements and cache (2): the installed element types with their settings, and clearing YOOtheme's caches.

Saved the way YOOtheme saves. Layouts are written in YOOtheme's own format, with the same check its builder makes that nobody changed the page since it was read. Every element in a layout must be one that's installed, because YOOtheme quietly shows an unknown element as nothing. A setting keeps its shape, and a group of settings is merged into what's stored rather than replacing it.

The health check finds what stops a change from showing: a disabled YOOtheme system plugin, a style with no compiled stylesheet or one older than the installed YOOtheme, page layouts YOOtheme can't read, and layouts close to the size the database column can hold.

Style changes need one click in the customizer. YOOtheme compiles its stylesheet in the browser, inside the customizer. Layout settings show on the next page load, but colours, fonts and other style settings reach visitors only after someone opens the customizer and saves. The tools say when that applies.

Permissions. The tools follow YOOtheme's and Joomla's own rules: settings need edit rights on Templates, and pages and modules need rights on them. In this first version, everything that changes the site (settings, layouts, switching Templates) is for Super Users only; other users can read. Custom scripts and the YOOtheme API key can't be changed over MCP by anyone, Super Users included. Read-only mode in CS MCP for J limits it to the reading tools.

Getting it. You need CS MCP for J and YOOtheme Pro 5, bought from YOOtheme. CS MCP for YOOtheme Pro is a yearly subscription from Cybersalt, or part of MCP for J Pro All Access. Once your Cybersalt account is linked in MCP for J's dashboard, install it from Components → MCP for J → Browse MCP Add-ons. Your subscription covers downloads and updates; the add-on keeps working on your site without it.

Tested on Joomla 6 with YOOtheme Pro 5.0.53: every tool called, with each change checked in the database and on the rendered page. It had a full security review before release. Joomla 5 and busy production sites haven't been tested yet, so take a backup first.

Joomla 6, PHP 8.2+. GPL-2.0-or-later. Not made or endorsed by YOOtheme.

Current release: 1.0.1
Documentation: https://docs.cybersalt.com/extensions/mcp-for-yootheme-pro
Changelog: https://docs.cybersalt.com/extensions/mcp-for-yootheme-pro/changelog