Get the plugin
WP MCP/Integrations/Page builders

Page builders integration

Elementor AI agent tool reference

Elementor stores every page as a JSON document in the _elementor_data post meta. WP MCP exposes that document to your AI agent through a curated 44-widget catalog with typed settings schemas, plus a structural suite for containers and layout. It also reads and writes the active kit, so the agent can restyle the whole site by editing global colors and typography. The agent reads the real element tree, then adds, updates, moves, or removes widgets, validated before every write, and snapshotted so any edit is one click from undone.

get-elementor-dataadd-widgetupdate-widgetadd-containerget-global-settingsupdate-global-colorsupdate-global-typographysave-as-templateapply-templateexport-pageimport-templatecreate-theme-templateset-template-conditionslist-theme-templates

In practice

How Elementor work goes with an agent.

Elementor writes a page as a JSON document in the _elementor_data meta row: containers or sections, columns and widgets, each with a short hex id and a settings object. Site-wide design sits elsewhere, in the active kit's _elementor_page_settings. WP MCP edits by element id and always against the hash of the raw JSON, so a stale read is refused instead of merged. When Elementor is fully loaded the write goes through Elementor's own document save; otherwise a raw meta write is followed by cache and CSS invalidation. Either way the stored tree is read back and checked before the call returns.

Every button on the pricing page that links to /old-signup should point to /signup.

Runs find-element by widget_type, which returns each match's element_id, ancestor path and the current data_hash, then batch-update with all the changes. The batch is validated first and applied under one snapshot: one unknown id refuses the whole batch, and one rollback-operation undoes it.

Set the primary color to #0e7490 and switch the heading font to Poppins.

Runs get-global-settings for the kit and its settings_hash, then update-global-colors and update-global-typography with that hash as expected_hash. Colors must be valid hex, the kit's meta is snapshotted first, and setting a font turns custom typography on so the token renders.

Build a site header and show it everywhere except the landing pages.

Runs create-theme-template for the header, then set-template-conditions (snapshot-first, through Elementor Pro's conditions manager when present), then resolve-theme-template to report which template wins for a given page and why. The create step is not snapshotted; delete-theme-template trashes it.

On our Elementor 4 site, create a global class for card shadows.

Runs detect-elementor-version to confirm supports_atomic, list-global-classes for the state_hash, then create-global-class. The styles are validated against Elementor's schema and a property it would drop is refused. The class set is snapshotted, so rollback-operation removes the class again.

What your AI can do

Real Elementor operations, every write reversible.

  • Read a page's parsed Elementor element tree with an expected hash
  • Add and update widgets from a validated 44-widget catalog
  • Build and rearrange flexbox containers with the structural suite
  • Edit the kit's global colors and typography to restyle the whole site
  • Save, apply, export, and import Elementor library templates
  • Build theme parts (header, footer, single, archive) and set display conditions
  • Build Elementor v4 atomic elements (flexbox, div-block, atomic widgets)
  • Create popups, set triggers, and bind dynamic tags
  • Add site-wide custom CSS and manage Elementor code snippets
  • Build custom Elementor widgets from a data spec (no code generation, no eval)
  • Duplicate, reorder, and relabel elements safely
  • Roll back any widget, structural, or global-style change, per edit or per session

Example prompts

Example Elementor prompts.

Build a hero container with a heading, subhead, and a button to /contact.

Add a three-column services section under the hero, each with an icon and text.

Set the primary brand color to #0e7490 and the heading font to Poppins.

Reorder the sections so pricing comes before the FAQ.

Under the hood

The Elementor calls, under the hood.

wpmcp, elementor

get-elementor-data({ post_id: 42 }), returns the element tree + expected_hash

add-widget({ post_id: 42, widget_type: "heading", settings: {…}, expected_hash }), validated, snapshotted, reversible

update-global-colors({ system_colors: [{ _id: "primary", color: "#0e7490" }], expected_hash }), restyles the whole site, snapshotted

Safety and access

What can be undone on Elementor, and what costs what.

Recoverable on Elementor

  • Element, widget, container, page-settings, dynamic-tag and apply-template writes are covered by the post snapshot, so rollback-operation restores the page exactly.
  • Kit colors and typography, global classes and global variables are snapshotted too, and a brand kit apply undoes with rollback-brand-kit or rollback-operation.
  • Template conditions and popup settings are snapshot-first.
  • Deleted code snippets and theme templates go to the WordPress trash and come back with restore-post.
  • After each page write the stored tree is read back; a mismatch restores the snapshot automatically and the page is byte-identical to before.

Elementor limits and opt-ins

  • Create tools are not snapshotted: create-theme-template, create-popup, create-code-snippet, save-as-template and import-template. Remove what they made with delete-theme-template, delete-code-snippet or delete-post.
  • regenerate-elementor-css is not snapshotted because it writes no content. A site-wide purge needs confirm:true and manage_options.
  • compile-custom-widget writes PHP, so it is off unless the wpmcp_enable_widget_compiler filter opts in, needs edit_files and honors DISALLOW_FILE_EDIT. The other custom widget tools only store specs.
  • The four atomic tools register only on Elementor 4.0 or later. delete-global-class and delete-global-variable are dry runs unless confirm:true is passed.

Free or Pro: Four Elementor tools are free: list-widgets, get-widget-schema, get-global-settings and regenerate-elementor-css. Everything that edits a page, the kit, templates, popups, global classes or variables, brand kits or custom widgets is WP MCP Pro. Elementor Pro is separate and optional: it supplies dynamic tags and its conditions manager, which WP MCP uses when they are present, and the dynamic tag list is short or empty without it.

Part of WP MCP Pro

The Elementor integration is part of WP MCP Pro.

One Pro licence unlocks the Elementor tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.

Frequently asked

Elementor MCP: questions, answered.

Do I need Elementor Pro?

No, the tools work with free Elementor, and Pro widgets in the catalog light up when Elementor Pro is active. WP MCP's Elementor deep editing is part of its own Pro tier.

Are Elementor edits reversible?

Yes. _elementor_data is ordinary post meta, so the standard post snapshot captures it, every change is restorable with one click.

What stops an agent overwriting a page I just saved in the editor?

Every mutation needs expected_hash, the sha256 of the raw _elementor_data from the agent's last read. If you saved in the editor afterwards, the hash no longer matches, the write is refused with a stale-hash error and nothing is touched. The agent re-reads and retries.

Which widgets get typed settings?

A curated catalog of 44 widgets has typed, validated parameters, and list-widgets marks which are cataloged. add-widget also accepts other registered widgets with raw settings, but update-widget refuses a non-cataloged widget and points to update-element.

How does it cope with very large pages?

get-elementor-data can return a summary skeleton, cut the tree at max_depth, or return one subtree by element_id. The data_hash always covers the whole page, so a windowed read is still a valid expected_hash for the next write.

Does it support Elementor 4 atomic elements?

Yes on Elementor 4.0 and later: add-flexbox, add-div-block, add-atomic-widget and update-atomic-widget, plus global classes and variables. They register only on a site whose Elementor renders atomic elements, and detect-elementor-version reports whether that is so.

Is there an AI agent for Elementor?

Yes, through WP MCP rather than Elementor itself. An agent you choose, such as Claude or Cursor, can read a page's parsed Elementor element tree with an expected hash. WP MCP is a separate plugin, not a built-in AI feature of Elementor. On the undo side: Element, widget, container, page-settings, dynamic-tag and apply-template writes are covered by the post snapshot, so rollback-operation restores the page exactly.

Point your AI at Elementor.