MCP for Page Builder CK Pro is a Pro add-on for MCP for J that adds the twelve Page Builder CK capabilities that genuinely don't exist in the free Light build: export and import of pages, saved elements, styles and content-type templates, plus the saved-block library and presets. It's the companion to the free MCP for Page Builder CK add-on, which already covers pages, the block tree, rows, columns, styles and backups. Every tool here refuses unless Page Builder CK Pro is installed on the site โ not because it has to, but because these are Cรฉdric Keiflin's paid features and routing around his licence check isn't ours to do.
Why this exists
Moving a Page Builder CK page between sites is the job that has no good manual answer. The markup is raw HTML with every block's options stored as custom attributes, the site root is stored as a |URIROOT| token that has to be swapped on the way in and out, and every block carries an id that its CSS is scoped to โ so copying a page by hand either breaks the links or silently cross-applies styling between two pages that now share ids. Page Builder CK Pro has export and import screens for exactly this, and this add-on gives your AI client the same operations without the download-and-re-upload round trip.
Two gates, and the second one is the point
There are two independent things standing between you and these tools, and they're worth separating.
The first is ours. This package needs a Cybersalt Pro membership to download, and that's enforced by the catalog.
The second is the vendor's, and it's the interesting one. Page Builder CK's entire Pro licence system is a single line that checks whether a directory called pro exists on disk. There's no key, no download id, nothing that phones home. It's enforced in the component's controllers and toolbars and never at the data layer, and the helper functions these features rely on ship in the free build too. Which means every tool in this package could have been written straight against the database and would have worked perfectly on a Light site.
They weren't. Each one checks for that directory first and refuses with an explanation when it's missing, and the refusal points at where to buy the real thing. Paying us for a membership doesn't entitle anyone to someone else's paid features, and a paywall being easy to step over isn't permission to step over it. If you're on Light, a Cybersalt membership alone won't make these tools run โ you also need Page Builder CK Pro from joomlack.fr.
One tool is deliberately not gated. get_pagebuilderck_pro_status exists to tell you why the other eleven are refusing, so gating it would be a trap. It reports the version, both edition signals โ what the manifest claims and what the filesystem shows, flagging any disagreement โ which Pro files are present, and a per-tool availability list.
What Claude can do
Twelve tools. The free add-on carries the other thirty.
| Area | Tools | What you can do |
|---|---|---|
| Export | 4 | Export a page, a saved element, a style or a content-type template. The output is the same shape as the .pbck snapshots Page Builder CK writes on every save, so the two are interchangeable. |
| Import | 4 | The same four in reverse, with every block id regenerated on the way in so imported content can't cross-apply styling to a page that's already there. |
| Library and presets | 3 | List the saved-block library, install an item from it into your site, and list the available presets. |
| Status | 1 | What this add-on can and can't do on this particular site, and why. Ungated on purpose. |
Installing it
You'll need Joomla 5 or 6, PHP 8.2 or later, MCP for J, the free MCP for Page Builder CK add-on for the base tool surface, and Page Builder CK Pro 3.6.5 or later from joomlack.fr. On Light, every tool here refuses by design.
- Subscribe above, or get this and every other Pro add-on with MCP for J Pro โ All Access.
- Download the ZIP and install it through System โ Install โ Extensions, or paste your download URL into Install from URL.
- That's the whole install. The plugin enables itself, and the tools show up in your connected AI client the next time it lists them.
There's no admin screen for this plugin, by design โ it adds tools to MCP for J rather than a place to click. If the tools come back refusing, run the status tool first; it'll tell you exactly which of the two gates you're standing behind.
Using it
Ask for what you want in plain language. "Export the pricing page so I can drop it on the staging site" gives you the JSON. "Import this page and tell me what ids it had to change" does the import and reports the remapping rather than leaving you to guess. "What's in the block library?" lists it without a trip to the admin.
Two things about the format are worth knowing before you move content around. An export is the whole database row with the site root tokenised, which is why an export from one site imports cleanly into another with a different domain. And import regenerates every block id, seeded from the ids already in use across all your pages, because Page Builder CK scopes every block's CSS to its id โ importing a page whose ids collide with an existing one would silently restyle both. For styles and content types that id rewrite happens in a single pass across the markup and the stylesheet together, since doing them separately would mint two different ids and leave the CSS selecting markup that no longer exists.
Permissions and security
File handling here is deliberately stricter than the component's own. Every path an import or library install touches is fully resolved and checked for containment after symlinks are followed, where the vendor's library controller concatenates raw input into a path. That isn't a hypothetical concern: Page Builder CK's file handling is the subject of CVE-2026-56290, an unauthenticated upload flaw on the CISA Known Exploited Vulnerabilities list with public exploitation tooling. Run 3.6.5 or later, on both editions.
Open source
GPL-2.0-or-later, the same license as Joomla itself. Source lives on GitHub.
Add comment