What's New

13 new MCP tools for Elementor 4.0's atomic element system (110 tools total).

Containers

• add-flexbox — Atomic flexbox container with direction, justify, align, gap
• add-div-block — Atomic div-block container (block flow layout)

Convenience Widgets

• add-atomic-heading, add-atomic-paragraph, add-atomic-button, add-atomic-image
• add-atomic-svg, add-atomic-youtube, add-atomic-video, add-atomic-divider

Universal

• add-atomic-widget — Add any atomic widget by type
• update-atomic-widget — Partial-merge update

Query

• detect-elementor-version — Returns version and atomic support status

Key Details

• Typed props ($$type) handled automatically — AI agents pass simple flat values
• Styles stored in separate styles map matching Elementor 4.0 data model
• All tools self-guard on Elementor >= 4.0 — zero changes to existing 97 legacy tools
• Addresses #28 and #29

Gemini API / Antigravity Compatibility Fix

Fixes HTTP 400 errors when using the plugin with Gemini-based MCP clients (Antigravity, etc.) by sanitizing JSON Schema output.

What changed

• Centralized schema sanitizer — New elementor_mcp_sanitize_schema() function recursively strips empty string values from enum arrays and ensures empty properties objects serialize as {} (not []). Applied to all 44 ability registrations via elementor_mcp_register_ability() wrapper.
• Control mapper hardening — switcher, popover_toggle, select, and choose control types no longer emit empty enum values in get-widget-schema output.
• Container schema fix — get-container-schema input schema now uses stdClass for empty properties (fixes 'allOf' failed - got array, want object error). Runtime enum output also sanitized.
• Import template fix — Added missing items schema to template_json array property (fixes items: missing field error).

Background

Elementor controls often use empty strings as "default/none" option keys. Claude tolerates these, but the Gemini API strictly validates JSON Schema and rejects empty enum values. This affected 80+ properties across dozens of tools.

Closes #21

What's Changed

• Fix: Add missing items property to all array type JSON Schema definitions across 6 ability files (12 instances). VS Code and other strict MCP clients reject tools with invalid schemas, causing "tool parameters array type must have items" errors (#6).

Full Changelog: v1.4.1...v1.4.2

What's Changed

• Fix: Node.js proxy now supports MCP_PROTOCOL_VERSION env var to override the protocol version in initialize responses, working around upstream MCP Adapter hardcoding 2025-06-18 which some clients don't support (#4).
• New: Connection tab now auto-generates Node.js proxy configs (recommended) with auto-detected filesystem path, alongside existing HTTP configs.
• Improved: Proxy now logs server info, protocol version, and discovered tools count for easier diagnostics.
• Improved: Proxy logs full response bodies to file (not stderr) when MCP_LOG_FILE is set.
• Improved: Expanded troubleshooting section in README with protocol version mismatch diagnosis, debug logging instructions, and session management guidance.
• Improved: Added Node.js proxy connection section to README with environment variable documentation.
• Improved: Added proxy config example with MCP_PROTOCOL_VERSION to mcp-config-examples.json.

Full Changelog: v1.4.0...v1.4.1

Latest stable release.

Added 22 new tools, improved admin UI with Changelogs tab and a couple of more enhancements.