Why this exists. SP Page Builder checks almost nothing when it saves a page, so anything shaped like JSON goes in. Its renderer is much stricter. Leave out one of five keys it reads without a guard and the page throws a 500. Invalid JSON is stored as the word "null", and the page quietly falls back to an old layout, which looks exactly like a save that never happened. Every write in this add-on checks the content tree first, and refuses rather than saving something that would take the page down.

What the AI can do. 62 tools in 11 groups:

• Pages (9): list, read, create, update, duplicate, publish or unpublish and delete pages, plus their SEO and Open Graph settings.
• Content tree (6): read the JSON or just its outline, validate it, write it, set the page's custom CSS and purge the generated CSS.
• Structure (6): read one node, add a row or an addon, change one node's settings, move it or delete it, leaving the rest of the page alone.
• Addons (5), Libraries (11), Media (3), Versions (5), Collections (6, read-only), Comments (4), Diagnostics (4) and a read-only table viewer (3).

Every tool describes itself to the AI app, so there's nothing to configure. Ask in plain language: "What's on the services page?" returns the outline, not hundreds of lines of JSON.

On the Free edition, most addons render as nothing. SP Page Builder Free renders 17 of its 68 addons, and Heading is one of the 51 it leaves out. A page that uses one of them shows nothing at all, with no error. The component's own edition check reports Pro on every site, so this add-on reads the edition from the installed files instead, and its write tools refuse those addons on Free unless you say you're preparing content for a Pro upgrade.

Things it handles for you. The main page table can't store emoji, so text with one is refused up front instead of being cut off mid-page. Typography presets are referenced by position, so that tool is read-only. Duplicating a page gives the copy its own permissions record and new element ids, which SP Page Builder's own duplicate doesn't. Generated CSS files have no cache-buster, so content writes purge the page's CSS file.

Permissions. The AI can never do more than the Joomla account it acts for could do in SP Page Builder itself. On top of MCP for J's Use and Write permissions, every tool applies SP Page Builder's own: Access Administration Interface to use it at all, Edit (or Edit Own) on the page to change it, Create, Edit State and Delete for those actions, and Configure ACL & Options for settings and API keys. A Deny set on one page holds. Read-only mode in MCP for J limits it to the reading tools.

Getting it. You need CS MCP for J and SP Page Builder (Free or Pro). Buy the add-on on its own, or get it with the MCP for J Pro All Access membership, then install it from Components → MCP for J → Browse MCP Add-ons or with the downloaded ZIP. It has no licence key: the download ID only controls downloads and updates, and it keeps working if a subscription ends.

Tested on the latest SP Page Builder, 6.10.0, in both editions on Joomla 6. Every tool group was driven, 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. Pages built by the add-on render on the front end and open in SP Page Builder's own editor with no errors.

Joomla 5 and 6, PHP 8.2+. GPL-2.0-or-later.

Current release: 1.0.6
Documentation: https://docs.cybersalt.com/extensions/mcp-for-sp-page-builder
Changelog: https://docs.cybersalt.com/extensions/mcp-for-sp-page-builder/changelog