Elementor Ultra MCP

What elementor-ultra-mcp MCP server does

The elementor-ultra-mcp MCP server is designed to give AI agents an engineering-style interface to real Elementor sites. Its companion WordPress plugin exposes REST endpoints under /wp-json/elementor-ultra/v1/*, while the TypeScript package presents those operations as MCP tools.

The documented tool surface contains 91 tools covering page operations, widgets, design settings, templates, media, navigation, Elementor Pro features, and HTML-to-Elementor conversion. The system targets Elementor V4 atomic elements first and provides a V3 classic fallback. It is intended for tasks such as listing pages, inspecting content trees, planning changes, building pages, and refactoring existing content.

How it works

The MCP server authenticates to WordPress with an application password and sends requests to the companion plugin. The plugin is described as the authoritative write boundary: changes are passed through Elementor's own Document::save() process instead of being written directly by the agent.

Before a mutation is saved, the server-side path validates the proposed Elementor tree. Invalid data is rejected atomically with a taxonomy error code. Write handling also includes backup snapshots, optimistic concurrency through base_hash, replay protection through op_id, diffs, and mandatory CSS priming. These controls make the integration suitable for agents that need to modify existing sites while reducing the risk of overwriting newer content.

The repository describes both stdio and Streamable HTTP transports, along with lean and full tool profiles. However, its setup notes say that the executable currently prints a “server core not yet wired” message until the server module is present, so users should verify the checkout's implementation state before treating the listed tool count as immediately available.

Setup and configuration

The project requires Node.js 20 or newer and pnpm 9.x. Docker is needed for the local WordPress environment managed by @wordpress/env; host PHP and Composer are not required for that environment. The target WordPress site must have the companion plugin installed, and the README specifies Elementor 4.1 or newer for the plugin quickstart.

Set WP_URL, WP_USER, and WP_APP_PASSWORD for the target site. MCP_TRANSPORT selects stdio by default or HTTP when set to http. ULTRA_TOOLS selects the default lean profile or the full profile. After installing dependencies, pnpm build produces the server executable at packages/server/dist/index.js.

For local development, the repository expects Elementor 4.1.1 and Elementor Pro 4.1.0 zip files in .wp-env-plugins/, then uses pnpm wp-env:start to boot the environment.

Tools and capabilities

The documented capabilities include:

• Reading and listing Elementor pages
• Building and modifying Elementor content trees
• Working with widgets, design settings, templates, and media
• Managing navigation and Elementor Pro features
• Converting HTML into Elementor structures
• Validating writes and creating backup snapshots
• Supporting dry runs, diffs, concurrency checks, and rollback-oriented workflows

The project also pairs with elementor-jsx, whose JSX-to-Elementor deployments use the plugin's REST seam.

Limitations and notes

The WordPress plugin and TypeScript packages have different licenses: the packages are MIT, while the plugin is GPL-2.0-or-later. The project is an independent integration and is not endorsed by Elementor Ltd. Elementor Pro binaries are licensed files and are not included in the repository. The README's scaffold notes also indicate that transport binding and tool registration depend on server implementation work being completed.