Get the plugin
WP MCP/Integrations/Elementor addons

Elementor addons integration

Unlimited Elements for Elementor MCP

Unlimited Elements registers a large library of extra Elementor widgets. WP MCP's Elementor tools handle any registered widget: cataloged core widgets take typed params, and every other registered widget, including Unlimited Elements', inserts through the raw settings escape hatch and reads back through get-elementor-data. No addon-specific integration, and every write is snapshotted first.

list-widgetsget-elementor-dataadd-widgetupdate-element

In practice

How Unlimited Elements for Elementor work goes with an agent.

Unlimited Elements has no dedicated WP MCP pack, so an agent works with its widgets the way it works with any registered Elementor widget: ask Elementor's registry what exists, read the control stack, then write raw settings. That is a real workflow with three distinct steps and different tiers. The widget registry and the control stack are readable on the free plugin. Reading a page's element tree and inserting or editing elements is Pro. Because the settings are raw, nothing checks them against a typed schema, so the agent should read the control stack before it writes.

Which Unlimited Elements widgets are installed here? Search by name.

Runs list-widgets with a search term. It returns each registered widget's name, title, categories, icon, tier and availability, and marks whether it is in WP MCP's curated catalog. Read only, and available on free.

What settings does that widget take?

Runs get-widget-schema for the widget name. For a widget outside the catalog it returns the full introspected control stack. Read only.

Add that widget under the hero container with these settings.

Runs get-elementor-data for the expected_hash, then add-widget with the widget type and raw settings, not typed params. An unknown widget type is refused, a stale hash is refused, and the page is snapshotted before the write.

Change the text setting on element 3f9a2c1 of the homepage.

Runs update-element, which merges the given settings into that element by id and snapshots the page's _elementor_data first. update-widget would refuse this widget, since it is not in the catalog.

What your AI can do

Real Unlimited Elements for Elementor operations, every write reversible.

  • Read a page's element tree including Unlimited Elements widgets
  • Insert an Unlimited Elements widget by type with raw settings
  • Update an existing widget's settings
  • Roll back any change via the post snapshot

Example prompts

Example Unlimited Elements for Elementor prompts.

List the Unlimited Elements widgets on the homepage.

Add an Unlimited Elements widget with these settings under the hero.

Update this Unlimited Elements element id's settings.

Under the hood

The Unlimited Elements for Elementor calls, under the hood.

wpmcp, unlimited-elements

add-widget({ post_id: 20, widget_type: "...", settings: {…}, expected_hash }), raw-settings escape hatch

get-elementor-data({ post_id: 20 })

Safety and access

What can be undone on Unlimited Elements for Elementor, and what costs what.

Recoverable on Unlimited Elements for Elementor

  • add-widget and update-element write the page's _elementor_data inside a snapshot, so rollback-operation restores the page exactly.
  • add-widget verifies the write and rolls it back automatically if verification fails.
  • Per-session rollback reverts every Elementor write of an agent run together.

Unlimited Elements for Elementor limits and opt-ins

  • Raw settings are written as given. Passing typed params for a widget outside the catalog is refused with not_cataloged.
  • WP MCP has no Unlimited Elements module toggle or widget catalog of its own.
  • Reading the element tree and writing are Pro. Only the registry and schema reads are free.

Free or Pro: Reading what Unlimited Elements registers is free: list-widgets finds the widget types and get-widget-schema returns a widget's control stack. Everything that touches a page is Pro: get-elementor-data reads the tree, add-widget inserts, and update-element edits. There is no Unlimited Elements pack on the theme pair, and no Pro toggle for its modules. If you only want to know what the suite offers and how to configure it, the free plugin is enough.

Part of WP MCP Pro

The Unlimited Elements for Elementor integration is part of WP MCP Pro.

One Pro licence unlocks the Unlimited Elements for 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

Unlimited Elements for Elementor MCP: questions, answered.

Why is Unlimited Elements covered without a dedicated integration?

Its widgets are standard registered Elementor widgets, and add-widget's tested raw-settings escape hatch inserts any registered widget while get-elementor-data reads the whole tree. So it is handled like core Elementor widgets.

How does an agent find the right widget type?

list-widgets accepts a search term matched against name, title and catalog keywords, and can filter by category or tier. Each row shows whether the widget is cataloged. The agent then passes that widget name as widget_type to add-widget with raw settings.

What happens if the agent guesses a widget name?

add-widget refuses a type Elementor has not registered, with invalid_widget_type, before anything is written. A guess that happens to be a real widget with wrong setting keys is not caught by a typed schema, which is why the agent should read the control stack first.

Does the free tier let me change an Unlimited Elements widget?

No. Free covers reading the widget registry and control schema. Reading a page's element tree and any write to _elementor_data are Pro tools. Pro also removes the 20-operation history cap, which matters when an agent iterates on widget settings.

Point your AI at Unlimited Elements for Elementor.