Claude + Elementor = WordPress Sites in 15 Minutes

Summary of the video

The video demonstrates a workflow for generating a WordPress website inside Elementor using Claude, by connecting Claude to WordPress via Elementor MCP and using WordPress MCP tooling. The goal is to move beyond “mock-up-only” Claude work and instead directly build/edit a real Elementor/WordPress site—without constantly rebuilding everything manually.

---

Key setup / prerequisites (guide-style steps)

1. Start with a project folder

   • Use either:
     • a blank HTML project folder, or
     • an existing site project created previously (example mentioned: a site created with “Claude Code”).

2. Install and run Local WordPress

   • The workflow is shown using a local WordPress instance.
   • Example local site name: “Arbor Oaks”
   • Admin testing credentials are set, with a warning not to use insecure passwords for production.

3. Use VS Code terminal + a GitHub repo

   • Open the project in VS Code and run commands from a provided GitHub repo.
   • Purpose: download/install the “Claude Elementor Kit” and set up the MCP/Claude skills for integration.

4. Create a WordPress application password for MCP

   • In WordPress admin → Users/Profile, create an application password.
   • Example label: “Claude MCP”.
   • Provide credentials back to the setup script so it can install required plugins.

5. Auto-install required plugins/themes

   • Installs/configures:
     • Elementor
     • A theme preset: “Hello Elementor”
     • Header/footer support for the Elementor free version via additional plugins
     • Fluent Forms and “essential add-ons” to enable easier development workflows (including workflows on the Elementor free plan)

6. Fix common error: “MCP namespace not yet registered”

   • If MCP tooling doesn’t activate automatically:
     • Go to Plugins
     • Manually activate “MCP tools” (some other parts may already be auto-activated).

7. Verify MCP server connectivity

   • The Claude/MCP connection is validated by running the MCP server (an “auth check” via Elementor MCP).
   • After connectivity is confirmed, the model begins working on the “empty site.”

---

What the automation does (product features / behavior)

Once connected, Claude autonomously:

• Builds the site in Elementor
  • The video notes this typically takes ~5–10 minutes, with later mention of about ~20 minutes of Claude processing in practice.
• Sets brand colors
• Generates page layout elements, such as:
  • containers
  • headings
  • text
  • structured Elementor sections
• Inserts custom HTML where Elementor components can’t be generated cleanly

---

Results and observed limitations (analysis-style findings)

• The generated Elementor site is described as “fully edited in with Elementor”, with most content present and correctly structured.
• Noted issues include:
  • some spacing/layout problems (e.g., a “moving strip” positioned incorrectly)
  • missing or incomplete motion graphics (e.g., “swooping transitions” only partly present)
  • background differences vs the intended design

Background handling

• The site initially uses a gradient background rather than the expected visual.
• The video claims Vimeo embeds can work as native backgrounds via Elementor background video setup (with a link and some “vibing/vibe coding” adjustments).

---

Manual refinement shown (“vibe coding” inside Elementor)

The host iteratively corrects specific Elementor settings to fix issues:

• Locate the relevant Elementor container
• Go to Style → Background → Video
• Paste a Vimeo link into the background video field

They demonstrate that with iterative prompting, the workflow can continue improving:

• spacing alignment
• transitions/motion effects
• background video replacement

---

Review/takeaway positioning

The video frames this as a productivity upgrade for selling or building WordPress/Elementor sites:

• You can produce true Elementor sites rather than only Claude mock-ups.
• It can be used even with the Elementor free plan, leveraging custom HTML and the automation steps.

---

Main speakers / sources (as mentioned in the subtitles)

• Speaker/host: “Hi everybody…” (unnamed in the subtitles)
• Tools/Integration sources: Claude, Elementor, WordPress, and Elementor MCP / WordPress MCP (referred to as “Elementor MCP” in the workflow)
• Repo/source referenced: a GitHub repo provided in the description (unnamed in the subtitles)
• Software mentioned: VS Code, Claude Code, Fluent Forms