Elementor MCP 页面编辑插件

MCP Abilities - Elementor

Inspect an Elementor page, find the widget or shared setting behind a problem, and make a targeted change through an authenticated MCP client. Keep the page editable in Elementor and check the rendered result after saving.

Tested up to: 7.1 (validated with WordPress 7.1-RC3)

Stable tag: 2.3.59

License: GPLv2 or later

Tags: mcp, elementor, page builder, ai, automation

What It Does

The add-on registers 89 Elementor abilities. They cover document inspection and editing, individual widgets and containers, shared templates and Kit settings, design observations, cache control and selected site tools. Elementor Pro supplies the optional Theme Builder, custom-code and form-submission features.

The frontend integration supplies missing JavaScript messages, Swiper arrow labels and native dialog close names from native site translations. Existing translations, customized defaults and individual carousel settings remain authoritative.

For example, a course page may have the wrong booking link and cramped mobile text. Inspect the button for the link problem and its container for the spacing problem. Changing a shared Kit or linked template can affect other pages, so choose that scope deliberately.

The Real Workflow

1. Identify the exact page and read its current Elementor data.
2. Inspect the relevant element, available widget controls and active Kit styles.
3. Decide whether the change belongs to one widget, a container, a shared template or the Kit.
4. Preview a supported operation with dry_run:true before saving. Read the ability schema: dry runs are not available on every operation and must not be assumed to be the default.
5. Save the selected change, read it back and inspect the page on desktop and mobile. Follow its important links and test its intended actions.

Why This Feels Different

The client can inspect real element IDs and native control names before acting. Targeted settings merges keep the change within Elementor data. Shared style references are checked against the active Kit; a copied template and a native linked template remain different choices.

The plugin's structural audits help locate questions worth investigating. Their scores do not prove that a page is clear, attractive, accessible or finished.

Before vs After

Who It Is For

WordPress operators, developers and editorial teams maintaining Elementor sites through an MCP client. It is useful for targeted repairs, repeated layout work and inspection of the site's native design settings. It does not convert another builder's pages into Elementor or supply an Elementor Pro licence.

Requirements

• WordPress 6.9 or later with the native Abilities API, and PHP 8.0 or later.
• Elementor installed and active on the site being edited.
• WordPress MCP Adapter and an ability exposure configuration. MCP Expose Abilities provides discovery for this add-on in the Devenia stack.
• An authenticated account with the permissions required by the selected operation and document.
• Elementor Pro for its Theme Builder conditions, custom-code and form-submission features.

Documentation

• Product page
• WordPress Abilities API
• WordPress MCP Adapter
• MCP Expose Abilities
• Elementor
• Elementor Pro

Start Here

Activate the required stack and this add-on. Confirm that elementor/get-data appears in your MCP client's discovery. Start with a read-only request for a page you are authorised to edit. Describe the visible problem and desired result before selecting a write operation.

Abilities (89)

Page/Post Data

Authoring Primitives

Template Management

Theme Builder

Custom Code (Pro)

Create a native Elementor Pro snippet with elementor/create-custom-code:

{
  "title": "Example script",
  "code": "<script>document.documentElement.dataset.example = 'ready';</script>",
  "status": "draft",
  "location": "elementor_body_end",
  "priority": 1,
  "conditions": ["include/general"]
}

Read it back with elementor/get-custom-code, then use elementor/update-custom-code with its id and status: "publish" to enable it. Use status: "draft" to disable it. An update preserves omitted fields; code: "" clears its code. List results include placement, priority and conditions; request include_code: true for the code.

Locations are elementor_head, elementor_body_start and elementor_body_end. Priority ranges from 1 to 10 and orders snippets within the same insertion location. Conditions use Elementor strings such as include/singular/page/123 and exclude/singular/page/456. An empty conditions list removes restrictions: published Custom Code then applies site-wide, as in native Elementor.

Code uses Elementor's native _elementor_code metadata. Existing native keys in meta remain supported and receive the same validation. Conflicting explicit fields and metadata are rejected; the older code: "" plus meta._elementor_code form is retained. Creating or updating code respects native unfiltered_html restrictions. Custom Code supports HTML, CSS and JavaScript; it does not execute PHP.

Form Submissions (Pro)

Site Tools & Settings

Usage Examples

These examples use illustrative IDs. Inspect the actual target and its current schema first.

Read a page and locate the booking button:

{"ability_name":"elementor/get-data","parameters":{"id":123,"format":"array"}}
{"ability_name":"elementor/find-elements","parameters":{"id":123,"widget_type":"button","include_path":true}}

Inspect the button's native controls, then preview a focused settings merge:

{"ability_name":"elementor/get-widget-controls","parameters":{"widget_type":"button","search":"link"}}
{"ability_name":"elementor/merge-element-settings","parameters":{"id":123,"element_id":"abc1234","settings":{"link":{"url":"https://example.com/courses/drawing/"}},"dry_run":true}}

Use the real element ID from inspection. Review the preview before submitting the intended save. Existing style violations can still block the document; allow_legacy_style_preservation:true permits unchanged legacy style violations, not newly introduced ones.

Inspect shared styles and available templates before authoring repeated content:

{"ability_name":"elementor/get-style-guide","parameters":{}}
{"ability_name":"elementor/find-template-for-pattern","parameters":{"pattern":"custom","search":"course"}}

For a saved page, regenerate its Elementor CSS when needed:

{"ability_name":"elementor/clear-cache","parameters":{"id":123,"scope":"post","regenerate_css":true}}

Safety and Ownership Boundaries

• Page and element operations check editing permissions. Switching the active Kit requires manage_options, permission to edit the selected Kit, a genuine non-trashed Kit document and successful option readback.
• Full or raw document replacement has operation-specific confirmation and destructive-change guards. Inspect each schema; there is no universal confirmation or dry-run contract across all 89 abilities.
• Shared document preparation applies style-reference and structural checks to supported saves and dry runs. It is not a browser rendering test.
• A native template reference can share future changes. Copying template data produces independent content. Confirm where Theme Builder conditions apply before changing them.
• Translation sibling protection depends on a registered language-provider filter. The add-on cannot discover every multilingual system by itself. Verify the other languages after a relevant change.
• Custom code and form submissions use administrative permissions. Form results can contain personal data when values are requested. Permanent deletion operations cannot be undone through a general plugin rollback command.
• Cache invalidation is scoped to the selected operation. Inspect actual frontend output after saving; clearing generated CSS alone does not prove every external cache has refreshed.

Installation

For update notifications in WordPress, install Devenia MCP Updater. The updater is optional. You choose which plugins update automatically through WordPress.

1. Confirm the WordPress, PHP, Elementor and MCP requirements above.
2. Download the stable ZIP.
3. In WordPress, open Plugins → Add New → Upload Plugin, select the ZIP and activate it.
4. Connect your authenticated MCP client and verify ability discovery.
5. Read one existing Elementor page before making changes.

Recent Changes

2.3.59

• Apply the native current-language dialog close name when dialogs load on demand, while preserving custom labels and native popup behavior.

2.3.58

• Use Elementor’s current native close message for dialog close buttons while preserving explicit labels and dialog behavior.

2.3.57

Permanent snippet deletion now removes its native display-condition assignment and refreshes location results while preserving other snippets and templates. Failed or unauthorized deletion leaves assignments intact.

2.3.56

Read and write the code rendered by native Elementor Pro snippets. Expose insertion location, priority and display conditions through the existing abilities, refresh native assignments, preserve code escaping and report metadata save failures.

2.3.54

• Supply missing Swiper arrow accessibility labels from native translations without replacing custom defaults or individual carousel settings.

2.3.53

• Supply missing JavaScript catalog messages from native frontend translations while preserving existing catalog entries and English defaults.

2.3.52

• Include Elementor data and document settings when WordPress checks whether a new revision is needed. Native preview snapshots now retain metadata-only edits without changing older snapshots.

2.3.51

• Keep Theme Builder display conditions aligned with each template's native location, including Single Post templates, while preserving other templates' assignments.
• Read conditions for one template or complete location maps. Empty conditions leave a template unassigned.

2.3.50

• Preserve both language versions during synchronous metadata synchronization and report successful Elementor saves correctly.

2.3.48

• Coordinate translated document protection with compatible Core Content writes. Preserve later explicit body, data and native settings edits without accepting incidental language copies.

2.3.47

Preserve native array values when restoring translated Elementor page settings.

2.3.46

Preserve translated post content when multilingual page builders regenerate it during Elementor saves.

2.3.45

Preserve translated Elementor data and page settings across repeated saves, including intentional edits to another language in the same request.

2.3.44

Add one dismissible Plugins-screen reminder when Devenia MCP Updater is missing or inactive, with persistent install or activate links. Automatic updates remain your choice in WordPress.

2.3.43

• Require site-settings authority and document edit permission before switching the active Kit.
• Reject ordinary templates and trashed Kits; verify the saved active Kit before reporting success.
• Preserve backslashes and escaped quotes when creating or updating Elementor Pro custom code.
• Keep project documentation outside the installable package.

2.3.42

• Apply shared validation and save handling to document, element and template writes, including supported dry runs.
• Validate global color and typography references against the active Kit.
• Expire native document HTML caches after writes and verify native linked-template reuse.

Contributing

Keep changes focused on the public WordPress abilities. Include a reproducible example and a targeted behavior check for a defect. Do not submit credentials or private page or form data.

License

GPLv2 or later.

Author

basicus

Links

• Product page
• Stable download