elementor-mcp
elementor-mcp is a WordPress plugin that exposes Elementor page building/editing capabilities as MCP (Model Context Protocol) tools via the WordPress MCP Adapter. It provides many tools to query Elementor structure/widgets/settings and to create/update/delete page content programmatically from MCP-compatible AI clients.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses WordPress Application Passwords with HTTP Basic auth to access the MCP endpoint. This is stronger than unauthenticated access, but the provided docs do not describe fine-grained MCP scopes/permissions—authorization likely follows the WordPress user capabilities. The toolset includes destructive operations, so credential protection and least-privilege user roles are important. No details are provided about TLS enforcement mechanics, logging/redaction of secrets, or dependency/version security posture.
⚡ Reliability
Best When
You have a WordPress site with Elementor and the WordPress MCP Adapter, and you want an MCP client (e.g., Claude Desktop/Cursor) to programmatically create or edit page designs with granular tool access.
Avoid When
You need read-only access, or you require strict guarantees that prompts/tool inputs cannot alter or delete content (the toolset includes destructive actions like clearing content/removing elements).
Use Cases
- • Let an MCP-capable agent generate and update Elementor pages from structured JSON/tool calls
- • Inspect existing Elementor page structure and widget settings for auditing or refactoring
- • Build pages/components via declarative “composite” structures (e.g., build-page)
- • Automate template/theme/popup creation and application
- • Manage global design tokens (colors/typography) through agent workflows
Not For
- • Public-facing use without strong access control (plugin can modify site content)
- • Fully unattended/anonymous automation where application credentials cannot be protected
- • Environments that cannot run WordPress + Elementor + the MCP Adapter (requirements are tightly coupled)
Interface
Authentication
Authentication appears to rely on a WordPress Application Password and HTTP Basic auth for the REST/MCP endpoint. No fine-grained MCP scopes were described in the provided README.
Pricing
README promotes a '50+ Premium Prompts Pack' via Gumroad, but pricing for the plugin itself is not specified in the provided content.
Agent Metadata
Known Gotchas
- ⚠ Mutating tools can change or delete content (e.g., delete-page-content, remove-element). Agents should confirm targets and avoid blind retries.
- ⚠ Element IDs and page structures may shift after operations like move/reorder/duplicate; subsequent tool calls should re-query structure when needed.
- ⚠ Pro/conditional widget tools may depend on Elementor/Pro capabilities; agent may need to detect availability via schemas/discovery tools.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for elementor-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.