Elementor Ultra
About
Build Elementor sites with AI agents — ~90 tools for native, editable Elementor V4 pages over REST, with validation, backups, rollback, and a typed JSX compiler. MIT.
Details
- Author
- algorismus-io
- Categories
- Developer Tools
Jump to
Setup
Install Elementor Ultra in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/algorismus-io/elementor-ultra-mcp
Follow the installation instructions in the repository README, then restart your MCP client.
What can you do with Elementor Ultra MCP?
- List pages— Ask to list all Elementor pages and their structure via theelementor.page.tools.
- Build a page— Ask to create a new Elementor page from a layout, with server-side validation and backup.
- Convert HTML— Ask to convert an HTML snippet into an Elementor element tree using the HTML→Elementor converter.
- Refactor live site— Ask to modify widgets, design, or templates on a live site, with automatic backups and rollback.
- Dry-run validation— Ask to validate a proposed element tree without saving, catching errors atomically.
The agent control surface for Elementor.A Model Context Protocol server + companion WordPress plugin that let AI agents read, build, refactor and govern real Elementor sites the way engineers ship software — Editor V4 atomic elements first, V3 classic fallback — with authoritative server-side validation, diffs, backups and rollback on every write.
- packages/server— TypeScript MCP server:91 tools(elementor.page.,widget,design,templates,media,nav,pro., HTML→Elementor convert), stdio + HTTP transports, lean/full tool profiles.
- plugin/elementor-ultra-mcp— WordPress plugin exposing the authoritative REST seam (/wp-json/elementor-ultra/v1/): every write goes through Elementor's ownDocument::save()with backup snapshots, optimistic concurrency (base_hash), idempotency (op_id) replay, the authoritative validator, and mandatory CSS priming.
- packages/shared— the frozen contract surface: REST route registry, error taxonomy, JSON-schema mirrors, golden fixtures. Byte-identical tospec/contracts/schemas(CI-guarded).
- spec/— the full engineering record: contracts, spike verdicts and work packages the system was built against.
{ "mcpServers": { "elementor-ultra": { "command": "node", "args": ["/path/to/elementor-ultra-mcp/packages/server/dist/index.js"], "env": { "WP_URL": "https://your-site.com", "WP_USER": "admin", "WP_APP_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx", "ULTRA_TOOLS": "full", }, }, }, }
- Ask your agent to list pages, dry-run a tree, build a page. Every mutation is validated by Elementor's own parsers server-side before anything saves; invalid trees are rejected atomically with a taxonomy error code.
- TypeScript packages (packages/):MIT© 2026Algorismus
- WordPress plugin (plugin/elementor-ultra-mcp):GPL-2.0-or-later(WordPress convention)
Not affiliated with or endorsed by Elementor Ltd — "Elementor" is their trademark; this is an independent integration that targets their page format.
You donotneed PHP or Composer on the host; the PHP tooling runs inside the wp-env container.
pnpm install # installs all workspace deps; writes/uses pnpm-lock.yaml pnpm build # turbo: compiles packages/shared + packages/server (strict TS) pnpm lint # eslint (typescript-eslint, recommended-type-checked) across the workspace pnpm format:check # prettier --check pnpm test:unit # turbo: vitest run in each package
Running the server bin (no tools wired yet)
Afterpnpm build, the server bin exists atpackages/server/dist/index.js. Withno env setit prints a clear message and exits cleanly (exit code 0):
node packages/server/dist/index.js # -> elementor-ultra-mcp: missing required environment variable(s): WP_URL, WP_USER, WP_APP_PASSWORD. ...
When configured, it reads the following environment variables:
The real transport binding + tool registry are added byWP-T01inpackages/server/src/server.ts. The bin (index.ts) lazilyimport()s./server.jsand prints"server core not yet wired"until that module exists — so the bin compiles and boots standalone on this scaffold.
Where the plugin zips live (and where Pro must be placed)
.wp-env.jsonreferences two local zips under.wp-env-plugins/(agitignoreddirectory):
.wp-env-plugins/ ├─ elementor.4.1.1.zip # Elementor free 4.1.1 └─ elementor-pro.4.1.0.zip # Elementor Pro 4.1.0 (licensed; not on wp.org)
These zips arenot committed(they are licensed binaries and are gitignored). After a fresh clone you must place them yourself:
mkdir -p .wp-env-plugins cp /path/to/elementor.4.1.1.zip .wp-env-plugins/elementor.4.1.1.zip cp /path/to/elementor-pro.4.1.0.zip .wp-env-plugins/elementor-pro.4.1.0.zip
The exact filenames above must match the paths in.wp-env.json.
pnpm wp-env:start # boots WordPress + Elementor 4.1.1 + Pro 4.1.0; mounts the companion plugin pnpm wp-env:stop
.wp-env.jsonalso mounts./plugin/elementor-ultra-mcpas a plugin. That directory's contents (the bootstrap,composer.json,phpcs.xml.dist,readme.txt, andincludes/) are created byWP-P01; once they land the companion plugin is activatable in the wp-env site. The plugin's own Composer/PHPCS configuration is also provided by WP-P01.
elementor-ultra-mcp/ ├─ packages/ │ ├─ server/ # TS MCP server (bin: elementor-ultra-mcp) │ └─ shared/ # shared types + JSON Schemas + fixtures ├─ plugin/ │ └─ elementor-ultra-mcp/ # companion WP plugin (PHP) — populated by WP-P01 ├─ spec/ # frozen architecture + contracts + work packages ├─ .wp-env.json # pins Elementor 4.1.1 + Pro 4.1.0 (local zips) + mounts the plugin └─ (root tooling: pnpm-workspace.yaml, turbo.json, tsconfig.base.json, eslint, prettier)
packages/serverpins@modelcontextprotocol/sdk ^1.29withzodas a required peer. Never add any@modelcontextprotocol/2.xpackage — in 1.x,inputSchema/outputSchemaareZodRawShape mapsand transports are deep.jsimports. CI guards against a 2.x dependency appearing in the lockfile (WP-F07).
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
Create crafted UI components inspired by the best 21st.dev design engineers.
Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server
An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .
MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent
ALAPI MCP Tools,Call hundreds of API interfaces via MCP
AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform
MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.
APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.
One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.
Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
