> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wpos.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Elementor Ultra — Build Elementor Sites with AI Agents (MCP)
> Open-source tooling that lets AI agents and developers build real Elementor V4 sites as code: JSX in, native editable pages out.
Elementor Ultra is an open-source stack for building Elementor V4 sites as code.
You (or an AI agent) write small typed JSX components, a compiler turns them into
native Elementor V4 atomic JSON, and a one-shot deployer writes them to WordPress
over REST. The result is a normal Elementor page: fully editable in the Elementor
editor, with no lock-in and no proprietary runtime on the site.
It was built agent-first. Typed props fail at build time, an authoritative
server-side validator rejects bad trees before they save, and verification gates
replace hand-written browser scripts. Humans get the same ergonomics; the design
center is the agent.
Elementor Ultra is MIT-licensed open source from the same team, separate from
the WPOS product documented in the other tabs. It is not affiliated with or
endorsed by Elementor Ltd; "Elementor" is their trademark, and this is an
independent toolchain that targets their page format.
## The architecture in one pass
1. **JSX components.** Pages live in an fs-project: `pages/*.page.jsx`, shared
`components/`, design tokens in `theme.mjs`. See [Projects](/ultra/projects).
2. **Compiler.** `exjsx build` compiles JSX to Elementor V4 atomic JSON, dedupes
repeated styles into shared global classes, and writes one reviewable bundle
file. Every change is a git diff, not a 4,000-line JSON blob.
3. **REST deploy.** `exjsx deploy` writes variables, classes, and pages to the
site over REST, idempotently, with drift protection for hand-edited pages.
See [Deploy](/ultra/deploy).
4. **Native Elementor V4 pages.** What lands on the site is standard atomic
Elementor content. Open it in the editor, hand it to a client, or keep
iterating from source.
A site built entirely by an AI agent with this stack, from a written brief to a
verified deploy (scroll-through of the live result):
## The four packages
| Package | Version | Role |
| ---------------------------------------- | ------- | ------------------------------------------------------------------------------------------------ |
| `@algorismus/elementor-jsx` | 1.6.0 | The JSX to Elementor V4 compiler plus the `exjsx` CLI: build, lint, deploy, media, decompile |
| `@algorismus/elementor-ultra-studio` | 0.5.0 | The agent build environment (`eu-studio`): provisioning, verification gates, measurement toolkit |
| `@algorismus/elementor-ultra-playground` | 1.2.0 | Instant local WordPress + Elementor via WASM, booted from a pre-baked snapshot |
| `@algorismus/create-elementor-ultra` | 1.0.0 | Interactive scaffolder: wires the stack into your AI client and your site |
A companion WordPress plugin, **elementor-ultra-mcp**, ships bundled inside the
playground snapshot (and as a zip for real sites). It provides the REST seams the
deployer and gates talk to, plus CSS lifecycle guards that keep agent deploys and
human editor sessions from destroying each other's work. See
[The companion plugin](/ultra/plugin).
## Who it is for
* **AI agents** that need a real API surface for Elementor instead of a blank
file: typed components, build-time errors, one-call verification gates, and
briefs designed for one-shot builds.
* **Developers and agencies** who want Elementor sites in version control:
reviewable diffs, CI-friendly linting, idempotent deploys, and a local
environment that boots in seconds.
## Start here
Local WordPress to a deployed, verified page in a few minutes.
The package matrix, requirements, and using a real WordPress site.
The fs-project layout: pages, components, theme tokens.
The sx vocabulary, the Tailwind subset, and the raw CSS escape hatch.
The post-deploy gate: structural matrix, interaction tests, doctor.
The complete one-page authoring reference.