Skip to main content

​
Packages

​
Requirements

  • Node.js 18 or newer (the playground needs 18.17+).
  • Playwright for the verification gates (eu-studio check, verify, clicktest, measure): npm i playwright, or point the EXJSX_IT_PLAYWRIGHT environment variable at an existing install’s entry file.
  • python3 with PIL and numpy for the photometric tooling (eu-studio pixeldiff, measure compare). Everything else is pure Node.
  • A WordPress site with Elementor 4.1.4 or newer, V4 atomic experiments on, plus the companion plugin (below). The compiler is certified on Elementor 4.1.4 through 4.2.1; version adapters translate prop-format changes per version. The playground ships all of this pre-baked.

​
Using a real WordPress instead of the playground

The whole pipeline targets any WordPress over plain REST. Three environment variables form the contract everywhere (exjsx deploy, eu-studio, the MCP server):
eu-studio resolves its target in this order: --url/--user/--app-password flags, then the WP_URL/WP_USER/WP_APP_PASSWORD environment, then the local playground’s baked defaults.
1

Create an application password

In wp-admin, open Users, then Profile, then Application Passwords and create one. This is standard WordPress auth; no extra auth plugin is needed.
On non-SSL sites, WordPress only accepts application passwords when WP_ENVIRONMENT_TYPE is set to local in wp-config.php. The doctor names this exact condition when auth fails.
2

Install the companion plugin

The deploy and verification seams live in the elementor-ultra-mcp companion plugin (GPL-2.0-or-later). Get the zip from the GitHub releases of the elementor-ultra-mcp repo, upload it in Plugins, then Add New, and activate it. The playground snapshot already contains it. What it adds is documented in The companion plugin.
3

Turn on the V4 experiments

In Elementor, then Settings, then Features, activate the V4 atomic elements, classes, and variables experiments. The plugin’s site/capabilities endpoint reports their state, and eu-studio status reads it:
4

Deploy

No wp-cli is required for deploys: the deployer detects the Elementor version over REST and writes everything through the plugin’s endpoints. Two optional features degrade gracefully without wp-cli and say so in the deploy report: drift detection (hand-edit protection) and the SEO runtime install.
Setting up an AI agent rather than a human workflow? npx @algorismus/create-elementor-ultra walks all of the above interactively, verifies each step live, writes the MCP config for Claude Desktop, Claude Code, Cursor, Windsurf, or VS Code, and installs a skills knowledge base the agent reads to run itself.

​
Next

Quickstart

The end-to-end local loop.

Provisioning

One-command bench sites with eu-studio newsite.