How to Set Up Elementor MCP with Claude, Cursor or Codex

You want Elementor MCP connected so Claude, Cursor, or Codex returns a real editable Elementor draft, not a blog summary of the launch. The wall is usually: wrong product (third-party EMCP Tools), live production as the first connect, or a WAF blocking the application password / REST path.

I am going to walk the setup order I would use on screen. Staging first. Confirm Elementor 4.3.0+ (the official MCP feature in the 4.3 release). Turn on Atomic Editor features. Open the Elementor MCP page. Enable MCP. Pick Claude Code, Claude Desktop, Codex, Cursor, or Other. Generate Prompt (application password created in the background). Paste into the AI client. Ask for a small Atomic section. Open the draft in the Editor and finish by hand. If connect fails, check Wordfence / Cloudflare / REST allowlists before you rebuild anything.

What Elementor MCP is (and is not)

Official Elementor MCP is the dashboard page under Elementor in wp-admin. It uses the Model Context Protocol so external AI tools talk to your Elementor site through WordPress AI Abilities. What comes back is native Elementor structure: Atomic elements, classes, variables, theme parts when your plan supports them. Drafts stay unpublished until you say so. The Editor stays the finish line.

This post is about that official product only.

Third-party EMCP Tools (and similar community connectors) are not the same thing. Different install path. Different support surface. If a tutorial walks you through a separate plugin that is not the Elementor → Elementor MCP screen, you are not following this guide. Name that difference early so you do not debug the wrong stack.

Elementor MCP is optional. You still edit by hand. AI does not replace the Editor. It hands you structure you can open and change.

Elementor documents MCP for the 4.3 release and later. Use its current setup guide alongside this walkthrough because menu names and supported clients can change.

Prerequisites before you click Enable

Make sure these are true before you generate anything:

1. WordPress 6.8+ (Tools → Site Health → Info → WordPress).
2. Elementor Core 4.3.0+. If you use Pro features, Elementor Pro 4.3.0+ as well. Matching major versions keeps you out of odd editor-only failures.
3. An administrator user. Connected AI tools inherit that user’s permissions. The agent cannot do more than the role allows.
4. Atomic Editor / V4 features available for the Atomic drafts you want to generate. If Atomic is off or unavailable on the site, turn the related Editor V4 / Atomic features on before you treat MCP as broken.
5. A staging URL you control (or a disposable clone). Not the only production client site with no rollback plan.

I will not invent a “you must have Angie for every draft” rule. Official docs say Angie is required for some Abilities / Admin extras (custom widgets, admin theming, bulk content / debugging helpers that ride the Abilities API). Basic Atomic page and layout generation through Elementor MCP does not require you to invent extra products. If a prompt asks for Angie-only abilities, install Angie or simplify the request.

Honest staging rule

Do not practice Elementor MCP connect on a client production site you cannot roll back.

Application passwords plus AI write access inherit the logged-in user’s role. On an admin account that means the agent can create and edit within what that admin can do. Staging (or a throwaway clone) lets you learn the prompt flow, revoke a password, and turn MCP off without a live homepage surprise.

Agencies are already testing production workflows after they have a process. A production workflow can be reasonable once you have tested access, review, and rollback. It is not the first place to learn what an AI client can edit.

My rule stays firm: first connect on staging. Production only after you know how to revoke, turn MCP off, and recover a bad draft.

Turn on Atomic Editor, then open Elementor MCP

1. Confirm Editor V4 / Atomic features are available for the site (Elementor settings / experiments for your build). You want Atomic drafts to land somewhere the Editor can open.
2. In wp-admin go to Elementor → Elementor MCP (or Elementor → Editor → Elementor MCP inside the editor submenu, depending on your menu layout).
3. Click Enable MCP access.

If you do not see the Elementor MCP page at all, stop and check versions. Free/Pro below 4.3.0 will not show the official launch page. Update first. Do not install a random third-party “MCP” plugin hoping it is the same product.

Generate the prompt and application password

On the MCP page:

1. Pick the client tab: Claude Code, Claude Desktop, Codex, Cursor, or Other.
2. Check the acknowledgment checkbox. You are agreeing that Generate Prompt will create an application password for this site.
3. Click Generate Prompt.
4. Click Copy prompt (or copy from the text box).

Elementor creates the application password in the background and includes it in the prompt. Admins only. Connection is per site.

If you prefer to wire credentials yourself, use the manual configuration option on the same page. Same outcome. Different control preference.

Connecting MCP itself is free. Usage cost sits with your AI tool’s credits. Elementor’s plan rules still apply: basic sections can generate on free; Pro features still need a Pro plan. MCP does not give you Pro widgets you are not licensed for.

Paste into Claude, Cursor, or Codex

Open your AI client’s MCP / connector settings. Paste the prompt exactly as copied. Complete whatever “add server” or “accept” step that client uses.

What “connected” looks like depends on the client, but you should see the Elementor MCP tools available (or a successful connect state) before you ask for a full homepage. If the client reports an authentication failure, inspect the error and verify the site URL and credentials. Revoke a suspected leaked application password before generating a replacement.

First request: keep it small. Ask for one Atomic section or a simple page, not a full site rebuild. You want a draft you can open and judge. Large first prompts hide whether connect actually worked.

Example shape of a first ask (adapt to your client’s chat):

• “Create a simple hero section as an Atomic Elementor draft: headline, short paragraph, primary button. Do not publish.”

Then open wp-admin and find the new draft.

Open the draft in the Editor and finish by hand

Official behavior: everything generated through Elementor MCP is saved as a draft, not published. Open it with Edit with Elementor (Atomic / V4 path as your site uses). Adjust spacing, copy, classes, and variables yourself. The design system stays yours.

If the Editor and the AI tool try to modify the same page at the same time, Elementor detects the conflict and asks you to refresh or discard before continuing. Do not ignore that notice. Pick one writer at a time.

Theme parts, components, and dynamic connections are available when your Elementor plan and site setup support them. Free vs Pro still matters for Pro-only building blocks. MCP does not bypass that.

Elementor MCP not connecting: what to check

If Generate Prompt works but your AI client can’t talk to the site, don’t reinstall Elementor. Work these checks in order. Most connect failures are the first three.

1. Elementor older than 4.3.4. Older builds could fail without telling you why. 4.3.3 (30 September) tightened access control and made MCP errors clearer. 4.3.4 (5 October) added an error when Application Passwords aren’t available and fixed MCP resources failing with older adapter versions. Update Elementor and Pro, then confirm Enable MCP access is still on under Elementor > Elementor MCP. Elementor changelog.
2. Staging runs on HTTP. WordPress only offers Application Passwords on HTTPS sites or sites set to the local environment type. If Users > Profile has no Application Passwords section, this is usually why. Put staging on HTTPS. Set WP_ENVIRONMENT_TYPE to local only on a real local install. WordPress reference.
3. A security plugin or host turned Application Passwords off. Your profile says they were disabled, or the section is missing on an HTTPS site. Wordfence has a site-wide option for this under its brute force protection settings, and some other security plugins and hosts do the same. Untick it, save, and generate the prompt again.
4. You connected as the wrong user. The AI gets the same permissions as the WordPress user who generated the prompt. If it connects but can’t create or edit what you asked, generate the prompt again while logged in as an administrator on staging.
5. A firewall is blocking the authenticated REST call. The password is right but the client still gets auth errors or a 403. Check your security plugin’s firewall log for the blocked request and allow that access only. Don’t leave the firewall off. Webgate hit this with Wordfence.
6. Cloudflare or a host WAF is answering instead of WordPress. You get a challenge page or 403 instead of JSON. Identify the exact blocked MCP route and the WAF rule in the logs. Exempt only that confirmed request and rule, or ask your host to make the narrow change. Do not bypass protection for all /wp-json/ requests.
7. You also run the separate WordPress MCP Adapter plugin. Elementor’s MCP is built in and creates the Application Password for you. The MCP Adapter is a different plugin you set up by hand. Since 4.3.3, Elementor’s bundled adapter can make the standalone one stand down, even with Elementor MCP off, so its route returns 404 rest_no_route. See Elementor issue #37547 for the reported conflict and its current status. If you need both integrations, test the exact combination on staging.
8. The client connects, then hangs, loops, or drops. Check the current Elementor issue reports for slow requests, a Codex handshake failure, or a reconnect loop. Their status can change. Testing a second client may help isolate a client-specific problem, but it does not prove the root cause.

If the wall looks like a stuck Elementor editor spinner or a REST 403 inside the editor, that’s a different fix order: How To Fix Elementor Not Loading. And don’t cache /wp-json/ or logged-in admin responses. Full-page cache on REST breaks more than MCP.

Revoke access and turn MCP off

When you are done testing, or when a password may have leaked into a chat log:

Revoke one client

1. Users → Profile
2. Scroll to Application Passwords
3. Find the Elementor MCP entry for that client (for example Elementor MCP – Claude Code)
4. Click Revoke

Turn MCP off site-wide

1. Elementor → Elementor MCP
2. Find Turn off MCP access
3. Confirm the turn-off popup

That blocks connected agents from reaching the MCP server on that site. Use it on staging when the test is over. Use it on production if you ever connected and changed your mind.

I treat revoke + turn off as part of the setup lesson, not an afterthought. If you cannot revoke cleanly, you were not ready for production connect.

Before you leave staging

One last check:

1. Staging (or disposable clone), not unprotected production.
2. WordPress 6.8+, Elementor 4.3.0+ (Pro too if you use Pro).
3. Atomic Editor features on. Elementor MCP page visible.
4. Enable MCP → pick client → acknowledge → Generate Prompt → paste into Claude / Cursor / Codex.
5. Small Atomic draft → open in Editor → finish by hand.
6. Revoke or turn MCP off when the test ends.
7. If connect fails, WAF / REST / application password before reinstall.

If MCP still will not connect after that pass, or you need staging / production recovery help, send me a note with the client you used (Claude, Cursor, or Codex) and what the failure message says. I build and fix Elementor systems for a living (about), and a real error string beats a vague “AI will not connect.”

FAQs

Official Elementor MCP vs EMCP Tools: which one is this post about?

Official Elementor MCP only: the Elementor → Elementor MCP page that ships with Elementor 4.3.0+. Third-party EMCP Tools walkthroughs are a different product. Do not mix their install steps into this checklist.

Does MCP publish pages for me?

No. Generated work is saved as a draft. You open it in the Editor and publish when you are ready. That is the control model Elementor documents for MCP.

Free vs Pro: what can the MCP generate without Pro?

Connecting MCP is free. Basic sections and free features can generate without a Pro plan. Pro features still require a Pro plan. MCP does not grant Pro widgets you are not licensed for.

Do I need Angie for basic Atomic drafts?

For basic Atomic page and layout work through Elementor MCP, follow the official connect path without inventing extra requirements. Official launch materials say Angie is required for some Abilities and Admin extras (custom widgets, admin experiences, certain bulk / debugging abilities). If your prompt needs those extras, install Angie or narrow the request.