In late September 2026, AI agents gained a sanctioned, built-in way to build directly inside Elementor. The Elementor MCP lets tools like Claude Code, Codex and Cursor create real, editable Elementor pages on a WordPress site. Days later, the WordPress project released its own official bridge for AI agents, the MCP Adapter, as a plugin on WordPress.org.
If you run an agency, this changes the conversation with clients and with your dev team. It also raises a fair question: should an AI agent ever touch a client’s site? This guide covers what each tool actually does (straight from the official docs), what it means for agency work, and a practical safety and QA checklist to use before you connect anything.
MCP stands for Model Context Protocol. It’s an open standard for connecting AI agents to outside systems. A system describes what it can do as “tools”, and any MCP-compatible AI client can discover and use those tools.
For WordPress, that means an agent no longer has to hand you code to paste somewhere. It can call actions on the site itself, such as creating a draft page, applying styles or updating content, within whatever permissions you give it.
There are now two official routes into a WordPress site, and they solve slightly different problems.
The Elementor MCP is built into Elementor itself. According to Elementor’s 4.3.0 changelog, version 4.3.0 introduced it along with a dedicated Elementor MCP page for connecting external AI tools. Elementor’s launch announcement is dated 29 September 2026. Elementor’s own comparison post says you need Elementor 4.3.0 or higher, with no extra plugin to install.
Per the official Elementor MCP page and launch post, a connected AI tool can:
Some capabilities need Angie, Elementor’s agentic AI plugin, which is free on WordPress.org. These include custom widgets, WP Admin customization, bulk content actions across many records, and access to abilities registered by other plugins such as WooCommerce, Yoast and ACF.
Elementor is clear about a few boundaries, and they matter for client work:
The setup is short. In the WordPress dashboard, go to Elementor > Elementor MCP and pick your AI tool. Elementor lists Claude Code, Claude Desktop, Codex and Cursor, plus “Other” for any MCP-compatible client. Elementor generates a setup prompt, creates the required WordPress application password in the background, and includes it in the prompt. You paste that prompt into your AI tool. A manual configuration option exists if you’d rather wire it up yourself.
That convenience has a flip side. The setup prompt contains a live credential, so treat it like a password. Don’t drop it into shared docs, tickets or team chat.
The MCP Adapter is the WordPress project’s canonical plugin for connecting AI agents to any WordPress site, with or without Elementor. Version 0.7.0 landed in the plugin directory on 2 October 2026. The Core AI team announced the public release on 7 October 2026.
The adapter doesn’t add AI features to your site. It’s a bridge. It takes abilities registered through the WordPress Abilities API, which arrived in WordPress 6.9, and exposes them to AI clients as MCP tools.
/wp-json/mcp/mcp-adapter-default-server with three tools: discover abilities, get ability info and execute an ability.The official site-owner guide walks through three steps:
npx, which needs Node.js. Clients that accept a URL and a header, such as Claude Code, can connect over HTTP directly.One gotcha: the guide says the web versions of Claude and ChatGPT connect through OAuth sign-in, which WordPress and the adapter don’t provide. So those web apps can’t connect to the MCP Adapter on their own today.
The WordPress team describes the MCP Adapter as still experimental. They’re working toward a stable 1.0, and the 0.7.0 release included breaking changes. They kept it out of WordPress core because the MCP specification itself is still changing quickly. For agencies, that’s a cue to test on staging and pin versions, not to roll it out across every client site this week.
WordPress 7.0 “Armstrong”, released 20 May 2026, added an AI Client in core and a central Connectors screen for managing AI provider connections. It also added a client-side Abilities package. Together with the MCP Adapter, these are the building blocks the ecosystem is now standardizing on.
| Elementor MCP | WordPress MCP Adapter | |
|---|---|---|
| Install | Built into Elementor 4.3.0+ | Separate plugin from WordPress.org |
| Setup | Guided screen under Elementor > Elementor MCP | Manual: Application Password plus client config |
| What agents can do | Build and edit native Elementor structure; more with Angie and Pro | Whatever public abilities your core and plugins register |
| Publishing | Generations saved as drafts | Abilities act on the site like a wp-admin action |
| Who can connect | Site admins only | Any WordPress user with an Application Password; actions limited to that user’s role |
| Maturity | Official; editing V3 layouts not yet supported | 0.x, described as experimental |
For an Elementor build, the Elementor MCP is the obvious starting point. For non-Elementor sites, or agents that need to reach several plugins, the MCP Adapter is the standard to watch. If you’re deciding between builders in the first place, our Elementor vs Breakdance comparison for agency owners covers the bigger trade-offs.
Elementor published an agency case study from Webgate, who tested the MCP on their own production site with Claude Code and Codex. Their takeaway wasn’t “AI builds the website”. It was that the MCP cuts the mechanical work of turning a design decision into Elementor structure. New atomic sections lived alongside existing V3 pages, without a full rebuild.
That’s the realistic win for agencies: landing pages, campaign pages and repetitive section builds get to a strong first draft faster.
The same case study lists where Webgate still keeps humans in charge: information architecture, UX decisions, visual hierarchy, accessibility, responsive behaviour, browser testing, performance and final publishing. Elementor’s own page says the same thing in fewer words: “The AI tool executes, the expertise directing it is yours.”
When anyone can prompt a layout, clients pay for the parts a prompt can’t guarantee: a site that converts, loads fast, works for every visitor and doesn’t break next month.
Expect clients to ask whether AI built their site, whether it should cost less, and who’s responsible if an agent breaks something. Have answers ready. A clear process, with drafts, human review and documented QA, is a stronger story than either “we don’t use AI” or “AI does it all”. It also keeps your margins tied to outcomes, not hours. We go deeper on that in our guide to white label WordPress development pricing.
Here’s how we’d approach it. Every item maps to something the official docs either require or recommend, plus standard agency hygiene.
The MCP Adapter’s own guide says to try new abilities on a staging copy first and keep regular backups. Abilities change a live site the same way an action in wp-admin does. Start every agent session on staging, then promote reviewed work through your normal deployment.
Before connecting an agent to a client’s site, tell the client which tool, what it can access and how work gets reviewed. Put it in your SOW or maintenance agreement.
For the MCP Adapter, the official guide recommends a separate user with the lowest role that can do the job, for example Editor rather than Administrator. That keeps the agent’s actions easy to identify and easy to switch off. The Elementor MCP requires an admin to connect, which is one more reason to start on staging.
Name each password clearly, for example “Claude Code – staging – Oct 2026”. The guide notes WordPress shows each password’s last-used date under Users > Profile, so you can revoke one instantly without affecting the others. Revoke passwords when a project ends.
Never paste setup prompts or passwords into tickets, shared docs or chat threads. Store them in a password manager. Keep HTTPS enforced.
Take a fresh backup and confirm you can restore it before the agent starts. Drafts reduce the risk, but bulk content actions and ability calls can still change real data.
Open each generated page in the Editor. Check structure, class and variable usage, naming and whether it actually follows the design system. Webgate’s workflow pairs the MCP with browser-based visual QA, comparing the result against the Figma design or screenshot.
Check every breakpoint. Run an accessibility pass against WCAG 2.2: heading order, colour contrast, focus states, alt text, form labels and keyboard navigation. Generated structure isn’t automatically accessible.
Run PageSpeed Insights on the staging URL before and after. Watch for oversized images, extra DOM depth and unused assets.
Every plugin you add for AI is one more thing to update. Elementor’s own comparison post warns that unofficial MCP servers vary in maintenance, permissions and what they expose. Prefer official tools, keep them updated, and check which abilities are public. Our guide to securing WordPress builds for agencies covers the wider hardening basics.
Keep publishing a manual, human step, ideally by someone who didn’t write the prompts.
Record prompts, changed pages and who approved them. If something breaks three weeks later, you’ll know where to look.
We’re a white label WordPress partner for agencies, building Elementor, Breakdance and WooCommerce sites under your brand, with unbranded code and no client contact. AI tools are getting fast, and we’re keen on them. We’ve written about the AI tools for WordPress development that are real versus hype.
But speed without review just moves the risk downstream. The value a dev partner adds now is the QA layer from the checklist above: staging, permissions, accessibility, performance and a human sign-off before anything ships. That’s the work that protects your relationship with your client.
If you’re weighing AI-assisted builds against capacity, or want a second set of experienced hands on agent-built drafts, let’s talk. Book a partner call.
Connecting is free, according to Elementor. Basic sections and features can be generated without a paid plan. Pro elements such as Forms, Popups and Loops need an Elementor Pro plan, and your AI tool’s own usage costs are separate.
No. It’s built into Elementor 4.3.0 and above. Angie, a free Elementor plugin, is only needed for extras like custom widgets, WP Admin customization, bulk actions and abilities from other plugins.
Elementor names Claude Code, Claude Desktop, Codex and Cursor as the best-supported tools. An “Other” option covers any MCP-compatible client. ChatGPT isn’t one of the named options, so check that your ChatGPT setup can connect to a custom MCP server before relying on it.
Install MCP Adapter from WordPress.org and create an Application Password for a dedicated user. Then add your site’s MCP endpoint to Claude Desktop (via the npx helper) or Claude Code (over HTTP). The web version of Claude can’t connect to the adapter on its own today, because it needs OAuth.
Only pages built with atomic (V4) elements and layouts, for now. Elementor says support for older Widget (V3) layouts is coming soon. New atomic sections can sit alongside existing V3 content, as the Webgate case study shows.
It can be, with guardrails: staging first, a dedicated low-privilege user, one revocable Application Password per client, fresh backups, and human review of every draft. Accessibility and performance checks belong before anything is published. Both official tools build in some of this, such as Elementor’s draft-only output and the adapter’s opt-in abilities and role-based permissions. The rest is your process.
L + P
admin@linesandpixels.team
Is WordPress dead now that anyone can vibe code a website? A balanced guide for agency owners: what AI site builders do well, where they break down for client sites, how WordPress is evolving with AI, and a decision table for when to use each.
A practical guide for agency owners on outsourcing and white-labeling WordPress maintenance: what a care plan should include, how to tier and price plans with real margin, a maintenance contract and SLA checklist, and how to choose a partner (plus the red flags).
What does white label WordPress development cost in 2026? Pricing models, sourced industry ranges, hidden costs, a worked margin example, and red flags to watch for when choosing a partner.
Elevate your business with a custom-designed website that captivates and converts. Let our expert team craft a digital experience perfectly tailored to your brand's needs.