Elementor MCP that edits classic and atomic pages. Free editing for Claude and Cursor, with supported recovery.

Grade how editable an Elementor page is

From GoBuildWP Free 1.18.0, an audit reads a page's saved Elementor tree, classic or atomic, and scores it from 0 to 100 with a fix for each finding. It looks for what makes a page look finished and edit badly: layout written into HTML widgets, scripts in the content, shortcode widgets, widgets whose plugin is no longer active, inline styles and custom CSS, fixed colours where the global palette belongs, containers nested more than six deep, and empty containers.

Each kind of finding is capped, so one problem cannot sink a score on its own. The exception is deliberate: a page that is a single HTML widget holding the whole layout can no longer grade as good. It scores fair at best, with that fix listed first, because it is the page that looks done in the browser and cannot be edited in the panel.

Turn HTML widgets back into Elementor widgets (Pro)

GoBuildWP Pro 1.12.0 repairs the most common finding. It reads simple markup inside an HTML widget and rebuilds it from the widgets a person would have used: headings become Heading widgets, paragraphs and lists one Text Editor, button-styled links Buttons, and images Image widgets, linked to the media library when the file is the site's own. Plain wrapper divs are opened up.

It leaves scripts, styles, iframes, forms, SVG, video and tables where they are and says why for each. Inline styles, classes and IDs are dropped on purpose, so plan to restyle the result from the kit. It runs as a dry run unless told to apply, and an applied repair stores the page's previous Elementor data in the change log, so the Changes screen can put it back.

Older pages built with sections and columns

Pages from before Elementor's containers are built from sections and columns. From Free 1.18.0, a page read with elementor-get-content can be written back with elementor-set-content: sections and columns validate against their own Elementor controls instead of failing as an unknown widget type, and column widths are kept.

Three smaller fixes from the same client reports: the form widget's Reply-To setting accepts a real field ID, rich-text fields such as the Text Editor accept paragraphs and lists, and rewriting a Theme Builder template keeps its template type, so a header stays a header and its display conditions keep placing it.

When the change comes through Elementor's own MCP server

Elementor 4.3 ships an MCP server of its own, and an agent connected to it does not pass through GoBuildWP. From Free 1.18.0, mapped element, composition, settings, publication, class and variable writes can be recorded with supported partial snapshots. Target resolution, retained capture and a matching handler are required; inspect the actual entry and verify the restored document separately. This source mapping is not an executed coexistence or restoration test. A page it creates, a component or a default style is recorded with the reason it cannot be put back; trash a created page to undo it.

On WordPress 7.1 you can go further under Settings, Other MCP servers. With Approvals for their writes switched on, those writes follow the site's safety profile, a destructive one waits for a person to approve it on a one-time wp-admin link, and Pro's approval queue and backup gate apply. It is off by default, because it changes how agents on that server behave; reads are never held.

A site header the AI designs and GoBuildWP builds

From GoBuildWP Free 1.18.0, wppilot/build-site-header handles the part of a header that is plumbing rather than design. There is no built-in layout: the AI reads the site first (title, tagline, logo, the colours and fonts the home page is actually painted with, each language's menu, whether there is a shop) and designs a header for this brand, as it designs the rest of the site.

On Elementor Pro, GoBuildWP saves that design as a Theme Builder header on every page, one per language when Polylang is active, swapped in by language. It fills in each language's menu, a styled language dropdown instead of Polylang's bare list, and the WooCommerce cart icon when there is a shop. Existing conditioned headers are kept with their conditions removed. Inspect the returned change entry and before-image before requesting recovery, because a saved record alone does not establish that the previous header is restorable.

Every design is checked twice. Before saving: a missing menu button for phones, a raw language list, a cart without WooCommerce, an image with no picture, links to nowhere, rows that would wrap on phones, and WCAG AA contrast for the colours the design sets. After saving, selected language home pages are fetched for supported server-side checks. Detected failures can trigger attempted restoration unless keep_on_fail is true; inspect that result. HTTP and stored-state checks do not exercise every responsive menu or interaction. Problems come back against the element that caused them, with what to change, so the AI fixes its own design; GoBuildWP never rewrites it. It also returns short-lived probe links the AI can open in a browser at 1440, 768 and 390 px to see wrapping, overlaps and the menu button opening. Building needs confirmation. wppilot/rollback-change requests supported recovery; verify its result and inspect each affected language page in a browser.