The Elementor MCP lets you build a complete WordPress website by describing what you want to Claude, which then assembles native Elementor elements for you. In a September 2026 tutorial, creator Ferdy Korpershoek rebuilt a full site, including header, blog templates and contact forms, for about $21 in AI usage. This guide walks through the setup, the workflow and the limits.
What the Elementor MCP Does for WordPress Builders
The Elementor MCP is a Model Context Protocol server built by Elementor that lets an AI assistant such as Claude build and edit a WordPress site using native Elementor elements. Instead of generating static HTML, Claude creates editable headings, flexbox containers, buttons, forms and Theme Builder templates inside your dashboard. You describe a section in plain language, upload a screenshot of a design you like, and Claude assembles it.
In his September 2026 tutorial, Ferdy Korpershoek used the tool to rebuild his own site: an animated hero with counting statistics, a sticky header that changes color on scroll, blog and archive templates, an ACF-driven knowledge base, and a contact form with conditional fields. He reports the total AI usage cost at about $21, a figure from his own Claude account and not an independent benchmark.
The difference from earlier AI page generators is editability. Every section Claude produces opens in the normal Elementor editor, so you can adjust spacing, typography or responsive behavior by hand afterward. Korpershoek calls it the best MCP he has used with WordPress; that is a first-hand opinion from the video, not a measured comparison.
What You Need Before Connecting Elementor MCP
Four components must be in place before the Elementor MCP will run. The tutorial uses a specific stack, and the free tiers of two of them will not work.
- Domain and hosting. Any WordPress-capable host works. Korpershoek demonstrates on Hostinger's Unlimited plan, which includes unlimited sites, NVMe storage and a free domain for the first year.
- Elementor Pro. The free Elementor plugin cannot build headers or footers through the MCP. The tutorial uses the Advanced Solo plan, listed at $7 per month for one site at the time of recording.
- Elementor 4.3 or newer. In Elementor's settings, enable version control and opt into beta testing, then update. The MCP works with Elementor version 3, but version 4 outputs cleaner code and supports more features.
- A paid Claude plan. The free Claude tier cannot handle this workload. Korpershoek uses Claude Pro at $17 per month and runs it through the desktop Claude Code app.
How to Connect Claude to Your WordPress Site
The connection takes one generated setup prompt and about two minutes. Follow these steps in order:
- In WordPress, go to Elementor → Editor Tools → Version Control, enable beta testing, save, then update Elementor from Dashboard → Updates.
2. Open the new Elementor MCP menu item and choose Claude Code. Click the option to generate a setup prompt; it contains your domain, username and application password.
3. Open Claude Code on your desktop, create a new project, and select or create an empty folder named after your site.
4. Paste the setup prompt and press enter. Claude now holds a live link to your WordPress installation through Elementor Pro.
5. Start describing what you want. Claude builds each request as native Elementor elements you can inspect in the editor afterward.
When Claude needs to inject behavior it cannot express in widgets, such as pointer-tracking card animations, it hands you a script to paste into Elementor → Custom Code. Keeping those snippets in named Custom Code entries makes later replacements simple.
Building Pages From Prompts and Screenshots
The core workflow mixes conversation with visual reference. Korpershoek takes full-page screenshots of designs using a Chrome extension, crops sections in Photoshop to 1280 pixels wide, uploads them to the WordPress media library, and asks Claude to recreate them. One prompt might read: recreate this hero, place three counting statistics below it, animate them from zero with 500-millisecond delays, and use the image from the media library.
Precision matters. When he asked for staggered card animations without specifying order and delays, the result ran in the wrong sequence, and he had to resend the prompt with 500, 750 and 1000 millisecond values. Vague requests produce plausible but not exact results, so name colors, sizes, animations and device behavior explicitly.
The same loop covers site-wide pieces. For the header, Claude recreated a reference screenshot, generated a page for every menu item, and switched to a dark variant on scroll. For mobile, a single screenshot plus one sentence, "turn the mobile menu to this," produced a working drawer with a close button. TemplateBuilder pieces, including single post, archive, footer and search-results templates, follow the pattern: create the template shell in WordPress first, then let Claude fill it.
A practical limit surfaced with ACF (Advanced Custom Fields): Claude could not create custom post types itself and said so. Korpershoek installed ACF, defined the tutorials and knowledge post types manually, and Claude then built every template, filter and archive around them.
What Still Requires Manual Work
The Elementor MCP removes most layout labor, but several tasks stayed on the human side of Korpershoek's build. Expect to handle these yourself:
- Creating custom post types and fields in ACF before Claude use them.
Uploading reference images and ad creatives to the WordPress media library.
Fixing content built with the classic editor or another builder; a post made in Elementor looked broken inside an MCP-built template until he switched it back to the WordPress editor.
Completing template shells in Theme Builder (single post, archive, footer, search results) and setting their display conditions.
Importing structured content: a WordPress XML export failed on first import, and Claude to reformat the file to match a working example before it imported cleanly.
Korpershoek notes this manual share may shrink as the tool matures, but in the version he tested, the split was roughly: Claude builds and styles, you supply data, assets and structural decisions.
What the Build Cost and How Model Choice Changes It
The whole demonstration site cost about $21 in Claude usage over the session, per Korpershoek's own cost check, plus roughly $25 once the final homepage and about page were added. He separately notes his original site cost him about €36,000 to produce years earlier; that comparison is anecdotal and covers very different scope.
Model choice moved that number sharply. Running a creative animation request on a heavier configuration with extended thinking, which he describes as Opus with ultra code settings, burned roughly 400,000 tokens for one section, and he advises against it for this kind of work. His recommendation: Opus on high effort for most builds, and switch models only when a task genuinely needs deeper reasoning.
These figures come from a single session on one site with 2026 pricing and should be treated as one data point, not a cost benchmark for Elementor MCP projects in general.
Frequently Asked Questions About Elementor MCP
- Do you need Elementor Pro for the Elementor MCP? Yes for real projects. The free version cannot build headers, footers or Theme Builder templates through the MCP, which are most of what makes the workflow worthwhile. The tutorial uses the Advanced Solo plan.
- Does the Elementor MCP work with any AI client? The demonstrated path uses Claude through Claude Code, where Elementor's own settings generate the setup prompt. Other MCP-compatible clients may connect, but the tutorial covers Claude only.
- Is the output editable in the normal Elementor editor? Yes. Claude builds with native Elementor elements, so every section, header and template opens in the standard editor for manual tweaks, and version 4 output is cleaner code than version 3.
- Can it create custom post types? Not in the version tested. Claude explicitly declined the ACF setup step, so you define post types and fields in ACF yourself before asking for templates that use them.
- How long does a build like this take? Korpershoek's full site took one extended working session plus a few hours of iteration, including screenshots, prompt refinement and manual fixes, for about $21 to $25 in AI costs.
Turn Your Own Walkthroughs Into Written Guides
Ferdy Korpershoek packed a 66-minute video with setup steps, prompt examples and workarounds, and the knowledge in it is exactly the kind that stays buried in a timeline. If you record tutorials, demos or interviews like this one, Gustavo dev doido and other creators face the same problem: the explanation exists only as video.
Skala Blog turns a YouTube URL into a structured written article: paste the link, the video is transcribed, and a publishable guide comes out the other side. If your best teaching lives in your uploads, give it a searchable, quotable written form alongside the video.
Fork this article
Start a new branch from the same video, shaped your way. You keep the credit; the original keeps the attribution.
A fork in another language is filed as a translation of this article, so the two pages point at each other. You can unlink it later from the editor.
0/240
You are creating
- Format
- For
- Language
- Source
- Your angle
You will be asked to sign in before it is generated.
Buy credits