MCP Tools for Elementor

A WordPress plugin that extends the WordPress MCP Adapter to expose Elementor data, widgets, and page design tools as MCP (Model Context Protocol) tools. This enables AI agents like Claude, Cursor, and other MCP-compatible clients to create and manipulate Elementor page designs programmatically.

Introducing EMCP Pro! 25% Discount for GitHub Community: MSRGIT

Grab the Deal

Features

• Up to 119 MCP Tools covering the full Elementor page-building workflow. Counts scale with your environment:
  • 62 tools — free Elementor only
  • 76 tools — free Elementor + Elementor 4.0 atomic elements
  • 101 tools — with Elementor Pro
  • 115 tools — with Elementor Pro + Elementor 4.0
  • 120 tools — with Elementor Pro + WooCommerce + Elementor 4.0
• Query & Discovery — List widgets, inspect page structures, read element settings, browse templates, view global design tokens
• Page Management — Create pages, update settings, clear content, import/export templates
• Layout Tools — Add flexbox containers, move/remove/duplicate elements, update containers, find elements, batch update, reorder children, get container schema
• Widget Tools — Universal add/update for any widget, plus 27 free convenience shortcuts, 30 conditional Pro widget tools, and 5 WooCommerce widget tools
• Pro Widget Support — Conditional tools for nav menu, loop grid, loop carousel, media carousel, nested tabs, nested accordion, portfolio, author box, login, code highlight, reviews, off-canvas, progress tracker, search, and more (only register when Elementor Pro is active)
• Atomic Elements (Elementor 4.0+) — 13 dedicated tools for Elementor's atomic system: flexbox, div-block, heading, paragraph, button, image, svg, youtube, video, divider, plus universal add-atomic-widget / update-atomic-widget and detect-elementor-version
• Theme Builder — Create theme templates (header/footer/single/archive), set display conditions (Pro)
• Dynamic Tags — List all available dynamic tags, bind dynamic data to element settings (Pro)
• Popup Builder — Create popup templates, configure triggers/conditions/timing (Pro)
• Template Tools — Save pages or elements as reusable templates, apply templates to pages
• Global Settings — Update site-wide color palettes and typography presets
• Brand Kits — One-click coordinated color + typography kits. Apply a curated brand kit and the whole site re-skins (system tokens + Theme Style defaults); back up and restore any time. 10 kits are free to apply; the full 50-kit library and the apply-brand-kit MCP tool are Pro
• AI Widget Builder (Pro) — Let an AI agent design custom Elementor widgets from a structured spec — no hand-written PHP. The plugin compiles the spec + an HTML template into a sandboxed Widget_Base class (35 control types, optional per-widget CSS/JS) that appears under a "Custom (EMCP)" category in the editor; a runtime safety net keeps a bad widget from breaking the editor
• Composite Tools — Build a complete page from a declarative JSON structure in a single call
• Stock Images — Search Openverse for Creative Commons images, sideload into Media Library, add to pages
• SVG Icons — Upload SVG icons from URL or raw markup for use with Elementor icon widgets
• Custom Code — Add custom CSS (element/page level), inject JavaScript, create site-wide code snippets for head/body injection
• Low-tools Mode — One-click toggle that filters the active tool list to a curated essentials set (~50 tools) so MCP clients with strict tool caps (Antigravity, Gemini API, etc.) stay under their limits
• Admin Dashboard — Dedicated top-level EMCP Tools menu with Tools / Connection / Prompts / Templates / Brand Kits / Skills / Widget Builder / Changelog tabs. Toggle individual tools on/off, view connection configs for all supported MCP clients, and reach the Get Support portal from any tab

Requirements

Installation

1. Install and activate Elementor (version 3.20+).
2. Install and activate the WordPress MCP Adapter plugin.
3. Download the latest release zip from the Releases page.
4. In WordPress, go to Plugins > Add New > Upload Plugin and upload the downloaded zip file.
5. Activate the plugin through the Plugins menu in WordPress.
6. Open the new EMCP Tools top-level menu in the WordPress admin sidebar to configure tools and view connection info.

Connecting to the MCP Server

Connect to your WordPress site from any AI client using HTTP. No proxy or Node.js needed — just a WordPress Application Password.

Prerequisites

1. Create an Application Password at Users > Profile > Application Passwords.
2. Base64-encode your credentials: echo -n "username:app-password" | base64
3. Your MCP endpoint is: https://your-site.com/wp-json/mcp/elementor-mcp-server

Tip: The plugin's EMCP Tools > Connection admin screen can generate all configs automatically — just enter your username and Application Password.

Claude Code

Add as .mcp.json in your project root:

{
    "mcpServers": {
        "elementor-mcp": {
            "type": "http",
            "url": "https://your-site.com/wp-json/mcp/elementor-mcp-server",
            "headers": {
                "Authorization": "Basic BASE64_ENCODED_CREDENTIALS"
            }
        }
    }
}

Claude Desktop

Add to claude_desktop_config.json (%APPDATA%\Claude\ on Windows, ~/Library/Application Support/Claude/ on macOS):

{
    "mcpServers": {
        "elementor-mcp": {
            "type": "http",
            "url": "https://your-site.com/wp-json/mcp/elementor-mcp-server",
            "headers": {
                "Authorization": "Basic BASE64_ENCODED_CREDENTIALS"
            }
        }
    }
}

Cursor

Add to .cursor/mcp.json in your project root, or ~/.cursor/mcp.json for global config:

{
    "mcpServers": {
        "elementor-mcp": {
            "url": "https://your-site.com/wp-json/mcp/elementor-mcp-server",
            "headers": {
                "Authorization": "Basic BASE64_ENCODED_CREDENTIALS"
            }
        }
    }
}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
    "mcpServers": {
        "elementor-mcp": {
            "serverUrl": "https://your-site.com/wp-json/mcp/elementor-mcp-server",
            "headers": {
                "Authorization": "Basic BASE64_ENCODED_CREDENTIALS"
            }
        }
    }
}

Antigravity

Add to ~/.gemini/antigravity/mcp_config.json:

{
    "mcpServers": {
        "elementor-mcp": {
            "serverUrl": "https://your-site.com/wp-json/mcp/elementor-mcp-server",
            "headers": {
                "Authorization": "Basic BASE64_ENCODED_CREDENTIALS"
            }
        }
    }
}

WP-CLI stdio (local development)

For local development with WP-CLI available, you can use the stdio transport (no HTTP auth needed):

{
    "mcpServers": {
        "elementor-mcp": {
            "type": "stdio",
            "command": "wp",
            "args": [
                "mcp-adapter", "serve",
                "--server=elementor-mcp-server",
                "--user=admin",
                "--path=/path/to/wordpress"
            ]
        }
    }
}

Node.js proxy (remote sites or protocol compatibility)

For remote WordPress sites, environments without WP-CLI, or when your AI client needs a different MCP protocol version, use the Node.js proxy. Your AI client launches it as a local subprocess, so it must run on the machine with the client — not on the WordPress server. On shared hosting you have no local access to the plugin directory, so use one of the two methods below.

Recommended — npx runner (nothing to install or keep in sync):

{
    "mcpServers": {
        "elementor-mcp": {
            "type": "stdio",
            "command": "npx",
            "args": ["-y", "@msrbuilds/emcp-proxy@latest"],
            "env": {
                "WP_URL": "https://your-site.com",
                "WP_USERNAME": "admin",
                "WP_APP_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx",
                "MCP_PROTOCOL_VERSION": "2024-11-05"
            }
        }
    }
}

npx fetches the latest proxy on each launch, so there is no local copy to drift from the plugin version. Requires Node.js 18+ on the client machine.

Alternative — local copy of the proxy file:

Extract bin/mcp-proxy.mjs from the plugin ZIP, save it anywhere on the machine running your AI client, and point args at that local path (e.g. ["C:\\local\\path\\to\\mcp-proxy.mjs"]) — not at the copy inside wp-content/plugins/... on the server. Re-extract it after plugin updates to pick up proxy fixes.

Optional environment variables:

Testing with MCP Inspector

npx @modelcontextprotocol/inspector wp mcp-adapter serve \
  --server=elementor-mcp-server --user=admin --path=/path/to/wordpress

Available Tools

Query & Discovery (7 tools)

Page Management (5 tools)

Layout & Structure (10 tools)

Widgets (2 universal + 27 free + 30 Pro + 5 WooCommerce)

Atomic Elements — Elementor 4.0+ (13 tools)

These tools only register when Elementor >= 4.0 is detected. Legacy widget tools continue to work alongside them.

Templates & Theme Builder (8 tools)

Global Settings (2 tools)

Composite (1 tool)

Stock Images (3 tools)

SVG Icons (1 tool)

Custom Code (4 tools)

Widget Builder — Pro (8 tools, off by default)

Design and register custom Elementor widgets from a structured spec — no hand-written PHP. The generator compiles the spec + an HTML template ({{control}}, {{#if}}, {{#each}}) into a sandboxed Widget_Base class, escaping every value by its control type.

PHP Snippets — Sandbox (6 tools, free, off by default)

Let an AI agent author server-side PHP behind a hard human-approval gate. The AI can validate code and create drafts, but a draft never runs until an admin activates it in EMCP Tools → Sandbox — there is deliberately no "activate" tool. Every snippet is statically parse-checked and security-scanned (blocks exec/eval/backticks/file-writes/network/destructive SQL/obfuscation) before it can be saved or activated.

Global Classes — Elementor 4.0+ (1 tool)

All tool names are prefixed with elementor-mcp/ in the MCP namespace (e.g., elementor-mcp/list-widgets). The MCP Adapter converts these to elementor-mcp-list-widgets for transport.

Permission Model

Troubleshooting

Tools not appearing in your AI client

If the MCP server connects but no tools appear in Claude Code, Cursor, or other clients:

1. Verify tools are registered. Test the endpoint directly with curl to confirm the server returns tools:

   hljs language-bash

   Copy

   curl -s -u admin:YOUR_APP_PASSWORD \
     https://your-site.com/wp-json/mcp/elementor-mcp-server \
     -H "Content-Type: application/json" \
     -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}'
   

   If this returns a valid JSON-RPC response with serverInfo, the server is working. The issue is likely a protocol version mismatch between the server and your client.

2. Check for protocol version mismatch. The WordPress MCP Adapter reports protocol version 2025-06-18. Some clients only support 2024-11-05. If using the Node.js proxy, set the MCP_PROTOCOL_VERSION environment variable to override:

   hljs language-json

   Copy

   "env": {
       "MCP_PROTOCOL_VERSION": "2024-11-05"
   }
   

3. Enable debug logging. Add the MCP_LOG_FILE environment variable to your proxy config to capture the full request/response flow:

   hljs language-json

   Copy

   "env": {
       "MCP_LOG_FILE": "/tmp/elementor-mcp-debug.log"
   }
   

   The log will show the protocol version, session IDs, tools count, and response bodies.

4. Use the proxy instead of direct HTTP. If you're using type: "http" to connect directly, your client must handle Mcp-Session-Id headers. Clients that don't support session management should use the Node.js proxy instead, which handles sessions automatically.

Common errors

• "No MCP servers registered" — Ensure the MCP Tools for Elementor plugin is active and all dependencies (Elementor, MCP Adapter, Abilities API) are met.
• HTTP 401 — Check your Application Password is correct and the user has edit_posts capability.
• "Missing Mcp-Session-Id header" — The HTTP endpoint requires an Mcp-Session-Id header on all requests after initialize. Use the Node.js proxy (which handles this automatically) instead of direct HTTP connections.
• Session errors — If connecting via direct HTTP, your client must capture the Mcp-Session-Id response header from initialize and include it on all subsequent requests.
• WP-CLI not found on Windows — Use the full path to php.exe and wp-cli.phar.

Sample Prompts

The prompts/ directory includes ready-to-use landing page prompts that demonstrate the full power of MCP Tools for Elementor tools. Each prompt is a complete blueprint — paste it into your AI client and watch an entire page get built automatically.

Each prompt includes:

• Complete design system (color palette, typography, spacing)
• Image search keywords for stock photo sourcing
• SVG icon specifications
• Full page structure (hero, sections, footer)
• Entrance animations using Elementor's built-in Motion Effects
• Custom CSS for hover states
• Custom JavaScript for scroll animations and counters
• Step-by-step execution order

Want more? A premium collection of 50 industry-specific prompts covering restaurants, med spas, law firms, florists, photography studios, and more is available separately.

Contributing

We welcome contributions from the community! Whether it's bug reports, feature requests, documentation improvements, or code contributions — every bit helps.

See CONTRIBUTING.md for detailed guidelines on how to get started.

Quick start:

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-tool)
3. Make your changes and test locally
4. Submit a Pull Request

Contributors

• @msrbuilds — Original author and maintainer
• @mhamzashafiq — Layout & element tools, widget convenience shortcuts, theme builder, dynamic tags, popup builder, WooCommerce widget tools, motion effects support, settings validator improvements

License

This project is licensed under the GNU General Public License v3.0.