> ## 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 + AI Agents: FAQ (Claude Code, Cursor, MCP)

> Short factual answers to the questions people actually ask about building Elementor sites with Claude Code, Cursor, Codex, or any MCP agent.

## Can Claude Code build an Elementor site?

Yes. With [exjsx](https://exjsx.dev), Claude Code writes typed JSX and the
compiler turns it into native, editable Elementor V4 pages over REST — no
copy-pasting JSON, no HTML blobs. The `--gates` dev loop re-verifies every save
at 1200/1920/390 px, so the agent finds layout breakage before you do. The
whole stack is open source and MIT-licensed; start at the
[quickstart](/ultra/quickstart).

## Is there an MCP server for Elementor?

Yes. **elementor-ultra-mcp** exposes roughly 90 MCP tools covering pages,
widgets, global classes, variables, media, forms, and rollback — see the
[install guide](/ultra/install). On top of it sits the **exjsx** compiler and
CLI, which most agents should prefer for authoring whole pages: one typed JSX
file in, a verified Elementor page out.

## Can Cursor or Codex build Elementor pages?

Yes. Nothing in the stack is Claude-specific: any MCP-capable agent (Cursor,
Codex, Claude Code, and others) can drive the same tools and the same
`exjsx` CLI. Setup is a single paste-to-agent prompt or the interactive wizard —
both are on the [install page](/ultra/install).

## Are AI-built Elementor pages editable in the normal editor?

Yes. The output is native Elementor V4 content — real atomic widgets, global
classes, and variables — not shortcodes or raw HTML embeds. A human can open
any agent-built page in the standard Elementor editor and keep working, and the
CSS lifecycle guards in the [companion plugin](/ultra/plugin) keep agent
deploys and editor sessions from stepping on each other. There is no lock-in:
uninstalling the toolchain leaves ordinary Elementor pages behind.

## Is exjsx free?

Yes. Everything is MIT-licensed (the WordPress companion plugin is GPL), runs
entirely on your machine, and needs no cloud service and no API key from us.
You only pay for whatever AI agent you already use.

## How is this different from asking AI to write HTML into an Elementor HTML widget?

An HTML widget gives you one opaque blob: clients can't edit it in the editor,
its inline CSS duplicates rules the theme already ships, and it collides with
plugin stylesheets in ways that are painful to debug. exjsx instead compiles to
the same native widget tree the editor itself produces, so styles go through
Elementor's class and variable system, responsive behavior uses real
breakpoints, and every element stays individually editable. The verification
gates then check the rendered result at three widths — something a pasted HTML
blob never gets.

## Does it work with free Elementor?

Yes. Free Elementor is enough for the whole authoring loop; the stack is
tested against Elementor 4.1.4 and 4.2.0. Elementor Pro is only needed for
Pro features (forms with submissions, popups, theme builder), which the
toolchain also supports when Pro is present.