Elementor MCP: the official server, what it can't edit yet, and the alternatives

The Elementor MCP is Elementor's own Model Context Protocol server. It shipped with Elementor 4.3 on 22 September 2026 and lets an AI assistant such as Claude Code, Claude Desktop, Codex or Cursor build and edit pages on your site as native Elementor elements, saved as drafts.

The catch is the editor version. It works on pages built with V4 atomic elements, and Elementor lists classic V3 layouts, which is what most existing Elementor sites use, as coming soon. Below is what the official server does, how to set it up, and what to use on a classic site in the meantime.

We make XeoRank, one of the alternatives on this page. The facts about Elementor's server come from Elementor's own MCP page, help article and launch post, checked on 17 October 2026.

Elementor MCP at a glance

How to set up the official Elementor MCP

1. Check you are on WordPress 6.8 or later (Tools > Site Health > Info) and Elementor 4.3.0 or later.
2. In the WordPress dashboard, go to Elementor > Elementor MCP and click Enable MCP access.
3. Pick your AI tool's tab: Claude Code, Claude Desktop, Codex, Cursor or Other.
4. Tick the box acknowledging that an application password will be created, then click Generate Prompt and Copy prompt.
5. Paste the prompt into your AI tool. It contains the connection details, including the application password Elementor created for you.

To disconnect one tool, revoke its application password under Users > Profile > Application Passwords. To cut off every connected tool at once, use Turn off MCP access on the same Elementor MCP screen.

What it can do

Elementor's launch post and MCP page list these capabilities:

• Build pages and layouts from atomic elements, and redesign existing atomic pages.
• Create and apply global classes and variables, hover states and responsive settings.
• Build theme parts such as headers, footers, archives, popups and 404 pages, with display conditions.
• Place, fill or create components, and connect dynamic content such as post fields, custom fields and taxonomies.
• Turn a Figma design or a Google Drive document into a page, if your AI tool already has that connection.

Three areas need Angie installed as well: custom widgets and admin screens, bulk content work such as updating many posts or fixing SEO gaps, and using abilities other plugins register through the WordPress Abilities API, for example WooCommerce, Yoast or ACF.

What it can't do yet

• Edit classic pages. If your pages were built with Sections and Columns, or with V3 Containers and widgets such as Heading and Text Editor, the official server cannot edit them yet. The FAQ on Elementor's MCP page says V3 support is coming but gives no date. The free Premium Addons for Elementor plugin adds an ability that places classic widgets inside atomic containers through the same connection, which helps on atomic pages but does not edit an existing classic layout.
• Publish. Everything lands as a draft. That is a sensible default, but it means a person still opens each page and publishes it.
• Run on older sites. WordPress below 6.8 or Elementor below 4.3.0 is not supported.

Is my site V3 or V4?

Open a page in the Elementor editor and look at the elements on it. Atomic elements have their own names in the panel: Div Block, Flexbox, Grid, Paragraph and Button, among others. Sections, columns, classic Containers and widgets like Text Editor are V3, and so is any page built before the site moved to the V4 editor.

Elementor MCP options compared

The official server is the obvious choice for a site built on atomic elements. The other options matter if your pages are classic V3, if you want SEO work done in the same conversation, or if you need to undo an AI edit.

AI clients differ too. Elementor's setup screen names Claude Code, Claude Desktop, Codex and Cursor. XeoRank and Respira both also connect to ChatGPT. For SEO fields, XeoRank writes titles and meta descriptions to Yoast, Rank Math or All in One SEO; with the official server, that goes through Angie and the abilities your SEO plugin registers.

Open-source projects change quickly, so check a repository's README and recent commits before you give it an application password for a live site.

Using an MCP on classic Elementor pages with XeoRank

XeoRank edits existing Elementor pages through the free XeoRank Connector plugin, which needs WordPress 5.6 or later and PHP 7.4 or later. The assistant writes native containers and widgets rather than one block of HTML, so the page stays editable in Elementor. On a site without Elementor Pro, Pro widgets such as forms or price tables are rebuilt from free widgets instead of being left broken.

1. Install the XeoRank Connector plugin on the site and create an application password for it.
2. Add the XeoRank MCP server, https://mcp.xeorank.com/mcp, to Claude, ChatGPT, Codex or Cursor. The MCP setup guide covers each client.
3. Connect the site, then turn writes on for it. Writes are off for every site until you do, and your assistant asks before each tool call.

Prompts that work well on a classic page:

• "Read the pricing page and list every heading in order. Fix any level that skips."
• "Replace the FAQ section on /services with an accordion of these five questions, and add FAQPage schema."
• "Rewrite the hero heading and the first paragraph so they answer what the page's top Search Console query is asking."

Each change to a page's content keeps a snapshot first, so "restore the version from before that edit" is one more prompt. SEO meta and site-wide custom code are not snapshotted.

What we learned writing V4 atomic elements

If you are building your own tooling against atomic elements, two details cost us the most time.

First, every prop is typed, including text, and the text type changed between releases. On Elementor 4.0.0 to 4.2.x a heading's title, a paragraph and a button's text use the html-v3 type, with the string nested inside a content object. From 4.3.0 the same props use escaped-html with the string as the value. Written as a bare string, the text still renders on the front end, but the editor's control shows blank and can't edit it. We found this from a customer's tabs element that looked right on the live page and empty in the editor.

Second, atomic widgets are stored with an elType of widget and a widgetType such as e-heading. Containers like e-div-block and e-flexbox use their own type as the elType. An element saved with elType: "e-heading" compiles its CSS and renders nothing.

XeoRank reads the site's Elementor version on each request and writes the matching types. If you use the official server, Elementor handles this for you.

Which should you use?

• Your site is built on atomic elements: start with the official Elementor MCP. It is free and maintained by Elementor, and it covers layouts, theme parts and components.
• Your pages are classic V3: the official server can't edit them yet. Use XeoRank, Respira or an open-source server you have reviewed, or rebuild key pages with atomic elements.
• You want SEO fixes as well as layout edits: XeoRank finds the issues from a site crawl and Search Console, then makes the edits on WordPress in the same conversation. See Elementor SEO with an AI agent for what it changes on a page.

Sources and how we compared

Details about the official server come from Elementor's MCP page, its help article on connecting Elementor to an AI tool using MCP, and the launch post, all checked on 17 October 2026. Where Elementor's pages disagree, as they do on whether redesigning existing pages needs Angie, we followed the FAQ.

Respira and Premium Addons details come from their own pages, also checked on 17 October 2026. XeoRank details come from our own documentation and product. The V4 prop types come from Elementor's atomic widgets source and from fixing that bug on a live site. For open-source servers we describe the general pattern rather than rate individual projects.