Elementor MCP: the complete setup guide

What is the Elementor MCP?

It is an MCP server built into Elementor that exposes page-building actions to your AI assistant.

MCP — the Model Context Protocol — is an open standard that lets an assistant call tools in another application instead of only writing text. Elementor 4.3.4 registers 27 of them — Elementor calls them abilities: actions plus reference resources — through the WordPress Abilities API, and publishes them with the official WordPress MCP Adapter at https://your-site.com/wp-json/elementor/mcp/.

Your assistant reads the page tree and your global classes and variables, then writes native Atomic elements through Elementor's own save routine. The result opens in the editor like a page you built by hand. The thinking is done by your AI tool, which is why its own subscription is what you pay for.

Is the Elementor MCP free?

Connecting is free: the MCP ships in free Elementor and costs nothing to switch on.

What you build follows Elementor's usual plans. In Elementor's own words, basic sections and features are free to generate, while Pro elements require a Pro plan. The AI work itself is paid to whoever runs your assistant — Anthropic for Claude, OpenAI for Codex, Cursor for Cursor.

Elementor doesn't say whether MCP use draws on Elementor One credits. In practice the generation runs in your AI tool, so the bill you will notice is that tool's subscription or API usage.

What do you need before you start?

An administrator account on a WordPress 6.9+ site served over HTTPS, with Elementor 4.3+ and the Atomic Editor on.

You can check your WordPress version under Tools > Site Health > Info.

How do you enable the Elementor MCP in WordPress?

Turn on MCP access in Elementor's settings, pick your AI tool, and paste the prompt Elementor generates.

1. Update Elementor to the latest 4.3.x release.
2. Go to Elementor > Elementor MCP and click Enable MCP access. Access is off by default.
3. Read the consent screen — trusted clients can view, edit and run code on the site — and turn on agent access.
4. Pick your client tab: Claude Code, Claude Desktop, Codex, Cursor or Other.
5. Tick the box acknowledging that an application password will be created, then click Generate Prompt, then Copy prompt.
6. Paste the prompt into your AI tool. It contains the server URL, your username and the application password, and asks the agent to add the server to its own configuration file and restart.
7. Back in WordPress, click Copy test prompt, run it in your client and paste the answer into Validate response.

Prefer to edit the file yourself? The Prefer manual configuration? link shows the file path for macOS, Linux and Windows, and a Generate & Copy configuration button. The next section shows what each client receives.

The validation step only checks that you pasted valid JSON; it doesn't prove the tools work. The real test is asking your assistant to read a page. And treat the setup prompt like a password: it contains a working credential in clear text.

How do you connect each AI client to the Elementor MCP?

Every client talks to the same endpoint with an Authorization: Basic … header; only the file and its format change.

In the snippets below, my-site-elementor stands for the server name Elementor generates (your site title plus -elementor), and BASE64 for your username and application password encoded together — copy both from the configuration Elementor generates rather than building them by hand.

{
  "mcpServers": {
    "my-site-elementor": {
      "type": "http",
      "url": "https://your-site.com/wp-json/elementor/mcp/",
      "headers": { "Authorization": "Basic BASE64" }
    }
  }
}

claude mcp add --transport http --scope user my-site-elementor \
  https://your-site.com/wp-json/elementor/mcp/ \
  --header "Authorization: Basic BASE64"

{
  "mcpServers": {
    "my-site-elementor": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://your-site.com/wp-json/elementor/mcp/",
               "--header", "Authorization: Basic BASE64"]
    }
  }
}

{
  "mcpServers": {
    "my-site-elementor": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://your-site.com/wp-json/elementor/mcp/",
               "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Basic BASE64" }
    }
  }
}

[mcp_servers.my-site-elementor]
url = "https://your-site.com/wp-json/elementor/mcp/"

[mcp_servers.my-site-elementor.headers]
Authorization = "Basic BASE64"

[mcp_servers.my-site-elementor]
url = "https://your-site.com/wp-json/elementor/mcp/"
http_headers = { "Authorization" = "Basic BASE64" }

{
  "mcpServers": {
    "my-site-elementor": {
      "url": "https://your-site.com/wp-json/elementor/mcp/",
      "headers": { "Authorization": "Basic BASE64" }
    }
  }
}

{
  "mcpServers": {
    "my-site-elementor": {
      "serverUrl": "https://your-site.com/wp-json/elementor/mcp/",
      "headers": { "Authorization": "Basic BASE64" }
    }
  }
}

What can the Elementor MCP do, and what can't it?

It builds and edits Atomic (V4) structure; it doesn't modify classic widgets or upload new images.

If you and the assistant edit the same page at the same time, Elementor shows a conflict warning: Force Save keeps your version, Reload takes the AI's changes. Close the page in the editor while the assistant works on it.

Does the Elementor MCP work with classic (V3) widgets?

Not for editing: the MCP modifies Atomic (V4) elements only, and Elementor says V3 widget layouts are coming “soon”.

Point it at a classic widget and the tool answers “Legacy V3 element cannot be modified through this MCP. Edit V3 elements directly in the Elementor editor.” The exception is a short list of theme widgets — nav menu, post content, post title, featured image, excerpt and archive title — and styling those goes through custom CSS, which needs Pro.

V3 and V4 can live side by side on the same site, even on the same page: in Elementor's Webgate case study, the agency kept its existing V3 sections and added new V4 sections through the MCP. If most of your site is V3, your options are to rebuild key sections in V4, wait for V3 support, or use a third-party server that edits classic widgets (see the comparison).

Common Elementor MCP errors and how to fix them

Most failures come from the application password, the Authorization header or the host — rarely from Elementor itself.

SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1

fastcgi_param HTTP_AUTHORIZATION $http_authorization;

Is the Elementor MCP safe on a client site?

It is as safe as the account you connect: the assistant gets exactly that user's permissions, and Elementor's consent screen warns that it can run code on a live site.

• Update Elementor. Versions 4.3.0 and 4.3.1 had a cross-site request forgery flaw (CVE-2026-62062) in the Editor Events module — not in the MCP itself — that could let an attacker create an admin account through a logged-in admin. It was fixed in 4.3.2.
• Treat the setup prompt as a password. It contains the application password in clear text: keep it out of shared chats, tickets and screenshots. Pasting it into an assistant also sends it to that AI provider as part of the conversation; the manual configuration keeps it in a local file instead.
• One client, one password. Revoke any of them under Users > Profile > Application Passwords. Turn off MCP access cuts every client at once.
• Start on staging, with a backup. Elementor's own consent screen says changes can't always be undone.
• Watch what the assistant reads. A page, a Figma file or a document can hide instructions aimed at the AI (prompt injection). Review every draft before it goes live.
• Your content goes to your AI provider. On client sites, cover it in your contract and privacy notice.
• Leave Angie's Super Admin Mode off unless you need it: it adds file-system, database and PHP access.

Official Elementor MCP or a third-party server?

Start with the official one if your pages are Atomic (V4) and you use Claude, Codex or Cursor: it's free and maintained by the team that builds the editor.

Third-party servers exist for what it doesn't cover yet: classic V3 widgets, OAuth sign-in (needed by ChatGPT and claude.ai), undo history, other page builders. This site sells one of them — which, to be clear, doesn't edit V3 widgets either: it focuses on turning a client mockup into a faithful page, with a structural SEO audit on every Elementor tree it writes, and since version 3.3 it offers OAuth sign-in for ChatGPT, claude.ai and the Claude mobile app. The whole field, with prices, is in our comparison of Elementor MCP servers.

Elementor MCP: frequently asked questions

Where to go next