Beaver Builder MCP that edits one node at a time. Templates and global styles included.

Beaver Builder Lite, the paid plugin and saved rows

Which Beaver Builder you run decides how much of the template work is available. Whole-page layout templates work broadly, but saved rows, columns and modules, and global templates, depend on Beaver Builder's node-templates feature, which the Lite edition does not have. On Lite, beaver-builder-list-templates will not list saved nodes and beaver-builder-create-template cannot save one. Run beaver-builder-check-setup first: it reports the version against the 2.9 minimum, the template mode, whether Beaver Themer is present and whether the connected user may manage the builder.

Global templates and global colours reach further than one page

Saving a row as a global template links every place it is applied. Edit the template and every linked page changes; applying it inserts a linked instance whose root renders from the template. That is the right tool for a footer call to action used on forty pages, and the wrong one for a section the client expects to vary per page, so say which you want in the prompt.

Two side effects are easy to miss. beaver-builder-apply-template regenerates node ids, so any id the agent noted before the apply is stale and the layout has to be read again before the next edit. And beaver-builder-delete-global-color unbinds every node that used the token; those nodes fall back to the plain value they stored, which may be an old colour nobody remembers. Prefer editing a token's value over deleting it unless you are sure nothing uses it.

Why the agent will not reach for the HTML module

An AI asked for a styled section will often produce one block of HTML and CSS, because that is the easiest thing to generate. In Beaver Builder that would land as a raw-code module nobody can edit visually. beaver-builder-add-node and beaver-builder-edit-node reject the HTML module unless the call passes allow_html_module, which the ability reserves for a real snippet the user asked to embed, never for layout or styling. The agent has to use registered modules from beaver-builder-list-modules instead, with keys read from beaver-builder-get-module, so the result opens as ordinary rows and modules in the editor.

A worked plan: a landing page from saved rows

• Read Only: list the saved rows and their global flags, and read the target page's published and draft layouts.
• Ask for a plan that names each saved row to insert, its position, and which text node in each row to change afterwards.
• Switch to Production Safe on staging. Apply the rows with scope=node, then read the layout again to pick up the new node ids.
• Edit only the text and image nodes the plan named, leaving any global row untouched so it stays linked.
• Open the page in the Beaver Builder editor and on the front end at phone width; spacing and responsive settings are the part an agent cannot judge from data.