Get the plugin
WP MCP/Integrations/Elementor addons

Elementor addons integration

JetElements MCP

Crocoblock JetElements registers extra Elementor widgets and keeps their on or off state in its jet-elements-settings option. WP MCP Pro adds a suite pack on the theme dispatcher pair: list-jetelements-widgets reads the suite's widgets as Elementor has them registered, with their controls for a named widget on request; get-jetelements-modules reads every widget's state, and the section parallax extension's, exactly as the suite resolves it; and set-jetelements-modules switches them by rewriting that option in the suite's own avaliable_widgets format, validated first, only changed keys written, snapshotted so rollback-operation restores it. The suite's own API keys in that option are never read out. The widgets themselves are inserted and edited through WP MCP's Elementor tools via the raw settings escape hatch.

theme-readtheme-writeget-elementor-dataadd-widgetupdate-element

In practice

How JetElements work goes with an agent.

JetElements shares a single jet-elements-settings option with the suite's other settings, API keys included, and stores its widget map under the suite's own avaliable_widgets key with the strings true and false as values. While that map is empty every widget is registered, and once it is saved any missing slug is off. Widgets are keyed by file slug, such as jet-elements-banner, and the section parallax extension lives in a separate map. WP MCP works inside those rules: it validates the batch, writes only the keys that change, keeps every other setting as stored, and never reads the keys out.

Is the section parallax extension on, and which JetElements widgets are off?

Runs get-jetelements-modules, which reports every widget slug and the section_parallax extension as the suite resolves them. An empty saved map shows every widget as on. API keys in the option are never read. Read only.

Turn off section parallax and the jet-elements-banner widget.

Runs set-jetelements-modules with both keys set to false. The extension goes to avaliable_extensions and the widget to avaliable_widgets, each as a 'false' string, and the option is snapshotted first.

Show me the controls of one JetElements widget before I add it.

Runs list-jetelements-widgets with widget set to its name. The suite is recognised by the Elementor\Jet_Elements_ class prefix, and the call returns a control summary. Read only.

Undo the last JetElements toggle.

Runs rollback-operation. The jet-elements-settings option is restored from its snapshot and the suite's cached copy of its settings is dropped, so the suite reads the restored values on the next request.

What your AI can do

Real JetElements operations, every write reversible.

  • List the JetElements widgets that are registered, with their controls on request
  • Read and toggle JetElements widgets and the section parallax extension, each toggle undoable
  • Insert a JetElements widget by type with raw settings
  • Update an existing JetElements widget's settings
  • Roll back any change, since the option and _elementor_data are snapshotted

Example prompts

Example JetElements prompts.

Which JetElements widgets are switched on?

Turn off the JetElements widgets we do not use.

Add a JetElements widget with these settings under the hero container.

Under the hood

The JetElements calls, under the hood.

wpmcp, jetelements

theme-read({ operation: "list-jetelements-widgets" }), controls for a named widget on request

theme-write({ operation: "set-jetelements-modules", args: { modules: {…} } }), suite's own format, snapshotted

Safety and access

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

Recoverable on JetElements

  • set-jetelements-modules snapshots the whole jet-elements-settings option, so rollback-operation restores widgets, extension and every other setting exactly.
  • The suite's cached settings are dropped after both a write and a rollback.
  • Widget edits through the Elementor tools are snapshotted with the page, separately.

JetElements limits and opt-ins

  • The suite's API keys live in the same option. They are never read out, and only widget and extension switches are written.
  • A widget switched off disappears from pages that use it until switched back on.
  • The pack was verified against a licensed JetElements 2.9.2 build.
  • JetElements widgets are recognised by class prefix, not by Elementor category, because that category is shared with other Crocoblock plugins.
  • update-widget refuses widgets outside WP MCP's catalog, so edits go through update-element.

Free or Pro: The JetElements pack is Pro: list-jetelements-widgets, get-jetelements-modules and set-jetelements-modules sit on the theme-read and theme-write pair and register only with a Pro licence. The toggle needs manage_options and has no separate opt-in filter. Placing and editing JetElements widgets uses add-widget, get-elementor-data and update-element, which are Pro too. On free, list-widgets and get-widget-schema still show what Elementor has registered.

Part of WP MCP Pro

The JetElements integration is part of WP MCP Pro.

One Pro licence unlocks the JetElements 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

JetElements MCP: questions, answered.

Does the JetElements integration expose the suite's API keys?

No. JetElements stores other settings, API keys among them, in the same option; only the widget and extension switches are read or written, and the keys are never read out.

What if JetElements is not active?

The ops stay documented in list-operations and answer addon_suite_inactive without touching anything.

Why does the widget map use the strings true and false?

That is how JetElements itself saves them, and the suite reads them back as strings. The pack accepts real booleans from the agent and writes the suite's format, so you never see the difference. It reports effective state back as booleans.

What if I toggle one widget and the widget map was never saved?

Saving only the toggled key would switch every other widget off, because a saved map treats missing slugs as off. So the pack first writes the full map from the current state, then applies your change. The other widgets stay on.

Is section parallax a widget?

No, it is an extension. JetElements keeps extensions in a separate avaliable_extensions map that defaults on while it is unsaved. The read lists section_parallax beside the widgets, and the write sends it to the right map automatically.

Can the agent change JetElements settings other than switches?

No. The option holds other settings, including API keys, but the pack reads and writes only the widget and extension switches. Everything else in the option is kept exactly as stored when a toggle is saved.

Point your AI at JetElements.