Release history for MCP for SP Page Builder. For install and usage instructions see the documentation.

📋 MCP for SP Page Builder - Changelog

v1.0.6 2026-10-30

Security release. Update as soon as you can if anyone other than your Super Users has MCP for J access.

🔐Security

  • The tools now apply SP Page Builder's own permissions. Before, any account with MCP for J's Use or Write permission could read and change SP Page Builder through the AI, even an account SP Page Builder itself doesn't let in. Now every tool needs Access Administration Interface on SP Page Builder; changing a page needs Edit on that page (or Edit Own on a page the account created); creating needs Create; publishing or unpublishing needs Edit State; deleting needs Delete; changing settings, switching addon types on or off, or showing API keys in full needs Configure ACL & Options. A Deny set on one page holds. See Permissions.
  • API keys are no longer shown to read-level accounts: get_sppagebuilder_config with reveal_secrets now needs Configure ACL & Options.

🐛Fixed

  • Colour variables: list_sppagebuilder_colors showed none of the colour variables SP Page Builder 5.7 and later store. They now show.

🔧Changed

  • set_sppagebuilder_page_settings accepts an empty string to remove a setting, and its fields use plain types every AI app can send.
  • write_sppagebuilder_page_content describes content as an array of rows; a JSON string is still accepted.

✅Tested

  • SP Page Builder 6.10.0 Free and 6.10.0 Pro, including the library, media, collections and comments tools against data created through SP Page Builder's own screens, and the permission checks with Super User, Administrator and Manager accounts.

v1.0.5 2026-10-29

🐛Fixed

  • Pages built with add_sppagebuilder_row open in SP Page Builder's editor again. The editor reads each column's width from settings.width, but the add-on wrote it only as a separate width key. The page displayed fine, but opening it in the editor failed with "Cannot read properties of undefined (reading 'xl')". New columns now use the shape the editor builds: an equal share on desktop and tablet, and full width on phones, so a row's columns stack on small screens.
  • Pages made with 1.0.4 or earlier are repaired on their next edit. Every write tool copies a column's width into settings.width when it's missing, which is what SP Page Builder itself does when it displays the page, so nothing changes on the front end.
  • Empty settings no longer break a page. write_sppagebuilder_page_content stored an empty "settings": {} as [], and SP Page Builder then failed on that page with an HTTP 500. Empty settings are now always stored as {}.

🔍Changed

  • Validation: validate_sppagebuilder_content flags columns without settings.width, and no longer warns about columns built by SP Page Builder's own editor.
  • Outline: column widths are read from settings.width first.
  • Name: messages and the plugin description use the core's current name, "CS MCP for J" ("MCP for J" in the Components menu).

📦Packaging

  • The download now includes LICENSE.txt (GPL-2.0-or-later).

✅Tested

  • SP Page Builder 6.10.0 Free and 6.10.0 Pro on Joomla 6: pages built by the add-on render on the front end and open in SP Page Builder's editor with no errors.

v1.0.4 2026-10-20

🧹Changed

  • Code comments: reworded two comments in GetAddonSchemaTool.php and ListAddonsTool.php that contained a placeholder language-key call. JED Checker read the placeholder as a real, missing language key. Only the comment text changed; no tool behaves differently.

v1.0.3 2026-10-20

🏷️Changed

  • New name: shows as "System - MCP for SP Page Builder" in Extensions → Plugins (was "System - MCP for Joomla: SP Page Builder add-on"), following the Joomla Extensions Directory's naming rules. Only the displayed name changed: the plugin's element, folder and update channel are the same, so updates keep working.
  • Licence notice: every PHP file now carries a GPL notice (GNU General Public License version 2 or later).

📦Packaging

  • Manifest: removed the non-standard <php_minimum> element. Joomla never read it from there. The minimum PHP version is still published by the update server, which is where Joomla checks it.
  • No tool behaves differently.

v1.0.2 2026-10-09

🐛Fixed

  • Clears Joomla's caches after install (the PSR-4 autoload map, opcache and Joomla's cache groups). A plugin installed after the autoload map was written is not in it, which could produce an HTTP 500 shortly after installing.
  • Never takes the site down when MCP for Joomla is missing: installed on a site without MCP for Joomla (now MCP for J), the add-on no longer enables itself, and says plainly that nothing is broken and MCP for Joomla is needed. If it is enabled anyway, it stays inert instead of failing every request, admin included. Thanks to Ferenc Füzér (One Online) for reporting this.

v1.0.1 2026-09-03

📦Packaging

  • PHP 8.2 is now declared as the minimum, since the add-on uses constants in traits.

v1.0.0 2026-08-27

🚀New

  • Initial release: 62 tools in 11 groups for SP Page Builder Free and Pro: pages, content, structure, addons, library, media, versions, collections, comments, diagnostics and read-only table access.