Elementor’s official MCP, explained

The Elementor MCP, and what it hands an AI agent.

Elementor now ships its own MCP server. It registers 29 abilities through the WordPress Abilities API that build and edit real Elementor layouts. Below is every one of them, the WordPress permission each checks, and how to run them under one governed, audited connection.

See the 29 abilities How the Bridge works

The short version

Elementor’s MCP lets Claude, Codex, Cursor and other MCP clients build Elementor pages as real, editable structure. Agent Abilities does not edit Elementor layouts itself, but it can put Elementor’s abilities behind the same off-by-default, audited connection as the rest of your site.

Made by: Elementor, built into the Elementor plugin. Beta on 15 September 2026, launched 23 September 2026.
Abilities: 29 with Elementor Pro active (27 free, 2 Pro), as registered in Elementor 4.3.2 and Elementor Pro 4.3.0.
Connection: Admin only and per site, over an Application Password Elementor creates for you.
Output: Saved as a draft, Elementor says. Publishing is its own ability.
With Agent Abilities: Bridge the abilities you choose; each is scoped, rate limited and audited.

What the Elementor MCP is

An MCP server inside the Elementor plugin, so an AI tool can build in Elementor’s own format instead of pasting HTML.

Elementor opened a beta of its MCP on 15 September 2026 and launched it on 23 September 2026. The launch post says a connected tool can build and redesign atomic pages and layouts, use the design system’s classes and variables, create headers, footers, archives and popups with display conditions, place and create components, and connect dynamic content.

Everything it generates is saved as a draft rather than published, and it comes back as real Elementor structure you can open in the editor and finish by hand. If you and an agent edit the same page at once, Elementor detects the conflict and asks you to refresh or discard before carrying on.

Under the hood, the beta post says it exposes these capabilities “through WordPress AI Abilities.” That matches the code: Elementor registers each ability with the WordPress 6.9 Abilities API under an elementor/ prefix, marks it public for MCP, and ships its own copy of the official MCP Adapter to serve them.

Some features need more than Elementor. Custom widgets, bulk content work, and acting as a “single WordPress entry point” to every other plugin’s abilities all require Angie to be installed, according to the launch post. The beta also required the Atomic Editor to be switched on, and many abilities still return an error until it is.

The 29 abilities it registers

As registered in Elementor 4.3.2 and Elementor Pro 4.3.0, checked 28 September 2026, grouped by the read-only and destructive flags Elementor itself declares.

Read only

Marked read only by Elementor. They look things up and change nothing.

Ability	Elementor’s label	Who can run it
`elementor/get-page-structure`	Get Elementor Page Structure	edit_posts, and edit_post on that page
`elementor/get-default-styles`Atomic	Get Default Styles	edit_posts
`elementor/get-widget-schema`Atomic	Get Elementor Widget Schema	edit_posts
`elementor/list-widget-schemas`Atomic	List Elementor Widget Schemas	edit_posts
`elementor/list-components`Atomic	List Elementor Components	edit_posts
`elementor/list-assets`	List Media Library Assets	edit_posts
`elementor/list-posts`	List WordPress Posts	Any logged-in user, then read_post per post
`elementor/list-resources`	List Elementor Resources	edit_posts
`elementor/read-resource`	Read Elementor Resource	edit_posts
`elementor/list-site-parts`Pro	List Site Parts	edit_posts

Reference material

Registered as MCP resources rather than tools: schemas, style guides and design-system data the model reads before it builds.

Ability	Elementor’s label	Who can run it
`elementor/global-classes-resource`Atomic	Global Classes	edit_posts
`elementor/global-variables-resource`Atomic	Global Variables	edit_posts
`elementor/interactions-schema-resource`Atomic	Interactions Schema	edit_posts
`elementor/list-dynamic-tags`Atomic	List Elementor Dynamic Tags	edit_posts
`elementor/manage-global-variable-guide`Atomic	Manage Global Variable Guide	manage_options
`elementor/style-best-practices`	Style Best Practices	edit_posts
`elementor/wordpress-best-practices`	WordPress Best Practices	edit_posts

Writes

They change the site, but Elementor does not mark them destructive.

Ability	Elementor’s label	Who can run it
`elementor/create-page`	Create Elementor Page	edit_posts
`elementor/create-preview-link`Atomic	Create Elementor Public Preview Link	edit_post on that page
`elementor/manage-classes`Atomic	Manage Global Classes	Elementor’s own class capability (administrators by default)
`elementor/reorder-classes`Atomic	Reorder Global Classes	Elementor’s own class capability (administrators by default)
`elementor/manage-global-variable`Atomic	Manage Global Variable	manage_options

Destructive writes

Marked destructive by Elementor. These rework layouts, site-wide styles or publish state.

Ability	Elementor’s label	Who can run it
`elementor/build-composition`Atomic	Build Composition	edit_posts, and edit_post on that page
`elementor/manage-elements`Atomic	Manage Elements	edit_posts, and edit_post on that page
`elementor/update-page-settings`	Update Elementor Page Settings	edit_posts
`elementor/publish-document`	Publish Elementor Document	edit_posts, then publish_post on that page
`elementor/manage-component`Atomic	Manage Elementor Component	manage_options
`elementor/manage-default-styles`Atomic	Manage Default Styles (Site-Wide)	manage_options
`elementor/manage-site-parts`Pro	Manage Elementor Site Parts	edit_posts, and edit_post on that part

Pro registered by Elementor Pro. Atomic returns an error until the Atomic Editor is on. “Who can run it” is the WordPress capability the ability checks, read from its source. Elementor’s MCP is in active development, so names and counts may change after 28 September 2026.

Who can connect, and who can run what

There are two separate gates here, and they check different things.

Elementor’s own connection lives on a new “Elementor MCP” page under Elementor in wp-admin. You pick Claude Code, Claude Desktop, Codex, Cursor, or “Other”, copy a setup prompt, and Elementor creates the Application Password in the background. A manual configuration is there too. Elementor says access is limited to site admins, and the connection is per site.

The abilities themselves are gated differently. Each one checks an ordinary WordPress capability, listed in the table above: most need edit_posts, and the site-wide ones need manage_options or Elementor’s own class capability, which only administrators hold by default. So the admin-only rule belongs to Elementor’s connection screen, not to the abilities.

That difference matters when you reach the same abilities through another MCP server. An Editor account, for example, passes the edit_posts checks and is still turned away from the site-wide ones.

Governing Elementor’s abilities with Agent Abilities

Use Elementor for Elementor. Use the Bridge if you want its abilities on the same leash as everything else.

Agent Abilities does not write Elementor layouts. Elementor keeps a page’s layout outside the normal post content, so the plugin’s own content abilities refuse a write to a page Elementor owns rather than report a success that changes nothing. For layout work, Elementor’s own abilities are the right tool.

What the plugin adds is the Bridge. It lists every ability other plugins register, Elementor’s included, on its “Other plugins” screen, grouped by plugin and each one off. Switch one on and it becomes a governed tool under its own name, next to the 179 abilities Agent Abilities ships:

Elementor registerselementor/get-page-structure

The Bridge exposesaafm-bridge/elementor-get-page-structure

Off until you pick it

Nothing Elementor registers reaches an agent until you enable it, one ability at a time. You could allow the read-only ones and leave every destructive one off.

A user you choose, not an admin key

The agent connects as a WordPress account you pick. Each call asks Elementor’s own permission check, live, as that account, so its role decides what it can run.

Audited and rate limited

Every bridged call, denials included, lands in the audit log in your own database, with argument keys and identifiers but never free-text content, and counts against the same rate limit as the rest.

The Bridge only wraps the call. Elementor’s code still does the work, so its draft-first page creation, its editor conflict check, and its Atomic Editor gate all run as they would through Elementor’s own connection. Where an ability declares neither read only nor destructive, the Bridge assumes destructive and asks you to confirm before you enable it.

To be clear about what we have checked: on 28 September 2026 we confirmed these 29 abilities register in the WordPress Abilities registry with Elementor 4.3.2 and Elementor Pro 4.3.0 active, which is what the Bridge reads. We have not yet run an Elementor build end to end through an MCP client over the Bridge. This section describes how the Bridge works, not a tested Elementor workflow.

Not the same as EMCP

Nearly the same name, different makers.

EMCP, short for Elementor MCP, is a third-party toolkit by MSR Builds. It is distributed on GitHub and Freemius rather than WordPress.org, and it predates Elementor’s own server. The Elementor MCP on this page is made by Elementor and ships inside the Elementor plugin.

If you are weighing EMCP, we compare it with Agent Abilities on its own page: Agent Abilities vs EMCP. For the wider field, see the roundup of WordPress MCP servers.

Frequently asked questions

Direct answers about Elementor’s MCP and how it fits with Agent Abilities.

Is the Elementor MCP free?

Connecting is free, according to Elementor’s launch post of 23 September 2026. Basic sections and features can be generated for free, Pro features need an Elementor Pro plan, and the AI tool you connect bills you on its own pricing. In Elementor 4.3.2 and Elementor Pro 4.3.0, 2 of the 29 abilities come from Elementor Pro.

Can a non-admin use the Elementor MCP?

Not through Elementor’s own connection: Elementor says access to it is limited to site admins, and the connection is per site. The abilities underneath check ordinary WordPress capabilities instead, so bridged through Agent Abilities they answer to whichever account the agent connects as. An Editor passes the edit_posts checks; the ones that require manage_options, or Elementor’s class capability, still turn it away.

How is this different from EMCP?

EMCP (Elementor MCP) is a separate, third-party toolkit by MSR Builds, distributed on GitHub and Freemius. The Elementor MCP on this page is Elementor’s own, built into the Elementor plugin and launched in September 2026. They are different products from different makers, and we compare EMCP with Agent Abilities on its own page.

Can I govern Elementor’s abilities with Agent Abilities for MCP?

Yes, through the Bridge. Elementor registers its abilities with the WordPress Abilities API, and the Bridge lists every ability other plugins register, each one off until you switch it on. An enabled one runs as the account you connected, is rate limited, and every call is audited, denials included. The Elementor code itself does the work.

Does Agent Abilities edit Elementor layouts itself?

No. Its own content abilities refuse to write to a page Elementor owns, because Elementor keeps the layout outside the normal post content. For layout work, use Elementor’s own abilities, directly or bridged.

Elementor facts are quoted from Elementor’s blog posts of 15 September 2026 and 23 September 2026, and the ability list was read from Elementor 4.3.2 and Elementor Pro 4.3.0 on 28 September 2026; Elementor’s product may have changed since. Agent Abilities for MCP is not affiliated with, or endorsed by, Elementor.

Let Elementor build. Decide what it can reach.

Install Agent Abilities for MCP, keep everything off, and bridge only the Elementor abilities you trust, under an account you choose.

Get it on WordPress.org Read the bridging docs

Off by default. Scoped to the connected user, gated on every call, logged.