WordPress Training
Elementor

Elementor MCP: Connect Claude & Co. to Elementor (Guide)

Elementor MCP: Claude, Cursor und Codex arbeiten direkt in Elementor
Contents (10)

In short: Elementor MCP is an official interface built into the plugin since Elementor 4.3 (23 September 2026). It connects AI tools such as Claude Code, Claude Desktop, Cursor or Codex directly to your WordPress site. The AI then builds real Elementor pages you can edit in the editor, and always as drafts. The connection itself costs nothing. You only pay for the AI tool you already use.

I set up the MCP on around 30 client sites in the first week. Below you will find how the setup works, where it pays off in day-to-day work and where you are better off leaving it alone.

What is MCP, anyway?

MCP stands for Model Context Protocol. It is an open standard that lets AI assistants access other software. Think of it as a plug: the AI plugs in, sees which tools are available (“create page”, “edit section”, “set colour variable”) and calls them itself.

Until now, AI in Elementor meant the built-in assistant (Elementor AI) or a detour: have code generated, paste it in by hand, hope for the best. The MCP removes that step. The AI works directly in the structure of your page, with containers, widgets, classes and variables, just as you would in the editor.

How Elementor MCP works: AI tool, MCP connection, WordPress site

What the AI can do through Elementor MCP

According to Elementor and my own tests, the MCP covers these tasks:

  • Build pages and layouts: complete pages in one go, with content and design.
  • Rework existing pages: point it at a page and have the layout revised, not just something tacked on.
  • Work with the design system: classes, variables and breakpoints, in other words your global colours and fonts.
  • Create theme parts: header, footer, archives, 404 page, popups.
  • Connect dynamic content: post fields, custom fields, taxonomies.
  • Handle bulk work: check or adjust many pages at once, hunt down errors.

Important: what the AI builds is not a mess of code. It is the same Elementor structure you would build by hand. Afterwards you open the page in the editor as usual and keep working.

Requirements

Before you start, check four things:

  1. Elementor 4.3 or newer. Earlier versions do not have the menu item. How to update safely is covered in Updating Elementor without breaking the layout.
  2. Administrator rights. Only admins can create the connection, and each connection applies to one website.
  3. An MCP-capable AI tool. Officially recommended are Claude Code, Claude Desktop, Codex and Cursor. Other MCP clients work with a manual setup.
  4. The Atomic Editor (Elementor V4) for the full feature set. This is the catch the announcement mentions only in passing. At the moment only layouts built from the new Atomic Elements are fully supported. Classic widget layouts (V3) are due to follow “soon”. Without the Atomic Editor, the MCP reads your pages, posts and widgets and can create and publish documents, but the actual building and reworking is largely off the table.

For some extra functions (custom widgets, changes in the WP admin, bulk actions), Elementor also requires the free Angie plugin from the WordPress directory.

Setting up Elementor MCP: three steps

Setting up Elementor MCP in three steps

Step 1: Open the menu. In the WordPress dashboard, go to Elementor → Elementor MCP and activate the connection.

Step 2: Choose your tool. Select what you work with, for example Claude Code or Cursor. Elementor automatically creates an application password for your user and generates a ready-made setup prompt.

Step 3: Paste the prompt. Copy this prompt into your AI tool. The tool adds the connection itself. In Claude Code and Claude Desktop it is active after restarting the session.

After that, one sentence is enough: “Show me all pages on this website that are built with Elementor.” If a list comes back, the connection works.

Three prompts I use in my daily work

The quality depends heavily on how specific you are. These three patterns have proven themselves for me:

New page from existing material:

“Create a service page ‘Website maintenance’. Take colours, fonts and spacing from the home page. Structure: hero with a one-sentence benefit, three service blocks, a pricing box, an FAQ with four questions, a contact button. Draft only.”

Clean up an existing page:

“Check the ‘About me’ page for nested containers that do nothing and for hard-coded colours instead of global variables. First list what you would change, and don’t change anything yet.”

Fix the mobile view:

“On the home page, the headings are too large on mobile and the spacing between sections is too wide. Only adjust the mobile breakpoint.”

The trick is the same in all three: tell the AI what to stick to (the existing design), what exactly the result should be, and that it should ask first or only create a draft.

Where the limits are

After a week of use, I see five points you should know about:

  • Classic pages are left out. Most existing Elementor websites are still built with sections and widgets (V3). The MCP can currently do little rebuilding there. If you are just switching to containers, you are closer, but Atomic is one step further still.
  • Pro features need Pro. The MCP creates simple sections with Elementor Free too. Forms, Theme Builder, popups and dynamic content require a Pro licence, just like in the editor. What Free can do is covered in Elementor Free or Pro.
  • The AI doesn’t know your taste. Without clear instructions you get solid but interchangeable layouts. The better your design system is maintained, the better the result.
  • The costs run elsewhere. The connection is free, but every request uses up credit in your AI subscription. Large rebuilds across many pages can add up.
  • More tools, more noise. For each connected website, your AI tool gets around 27 additional tools. With several websites at once, the AI slows down and is more likely to mix things up. That is why I only switch the MCP on for the site I am currently working on.

Security: what you should know before switching it on

The MCP works with an administrator’s application password. Anyone who has this password can build on your pages through the interface. A few rules I follow on all client sites:

  • Only switch it on when you need it. If the MCP is deactivated in Elementor, the interface does not respond, not even with a valid password. That is the simplest protection.
  • Check drafts before they go live. Elementor saves AI results as drafts by default. Only publish after a look in the editor and on your phone.
  • Back up first. Before larger rebuilds, make a backup, and ideally work on a staging copy. More on this in my WordPress security measures.
  • Revoke the password when you stop. Under Users → Profile → Application Passwords you see every connection and can revoke each one individually.
  • Keep the GDPR in mind. Page content is sent to the provider of your AI tool. For texts and layouts this is usually unproblematic. If your pages or fields contain personal data (staff profiles, testimonials with names), you need a data processing agreement with the AI provider.

Who is Elementor MCP worth it for?

Worth it if you already work with Claude, Cursor or Codex, build or rebuild your website on the Atomic Editor, and maintain many similar pages, such as service pages, location pages or courses.

Not worth it yet if your site runs entirely on classic widgets and you don’t want to rebuild it, or if you are just learning Elementor. In that case the AI takes over exactly the steps you should actually understand. How Elementor works in principle is explained in What is Elementor?.

Elementor Pro: If you want to use the MCP for Theme Builder, forms or dynamic content, you need the Pro version. View Elementor Pro

Frequently asked questions about Elementor MCP

Does Elementor MCP cost anything?
No. The connection is free, even with Elementor Free. Costs only arise for your AI tool and for Pro features that require a Pro licence.

Which AI tools work with Elementor MCP?
Officially recommended are Claude Code, Claude Desktop, Codex and Cursor. Any other tool that supports MCP can be connected manually.

Does the AI publish pages automatically?
No. Results are saved as drafts by default. You decide what goes live.

Does Elementor MCP work with my old Elementor pages?
Only to a limited extent. Currently, pages built from Atomic Elements (Elementor V4) are fully supported. Classic widget layouts can be read; reworking them is due in a later update.

Is Elementor MCP the same as Elementor AI?
No. Elementor AI is the assistant in the editor and runs on Elementor credits. The MCP is an interface for external AI tools that you choose and pay for yourself.

Can I switch Elementor MCP off again?
Yes, at any time under Elementor → Elementor MCP. The interface is then locked. You should also revoke the application password in your user profile.

My verdict

Elementor MCP is the first AI tool for Elementor that I show clients without a queasy feeling: it builds real Elementor structure, works only with drafts and is switched off again with one click. The biggest catch is the Atomic Editor. For existing sites, it is currently more of an analysis and clean-up tool than a page builder.

If you want to try the MCP on your own website, I will set it up with you in my Elementor training: the connection, secure settings and the first prompts on your real pages. Online via Zoom or Teams, € 109 per hour.

Newsletter

WordPress know-how by email

New guides and practical tips on WordPress, Elementor and WooCommerce. No spam, unsubscribe any time.

You will get a confirmation email first. Details in the privacy policy.

Tags

AnleitungClaudeElementorKIMCP