msrbuilds/elementor-mcp v3.21.5

3.21.5

on GitHub

Fixes from user reports: MCP clients that check output schemas, snippet tools on W3 Total Cache with Valkey, global typography, Elementor Pro theme widgets and the collapsing admin menu.

• Fixed: get-element-settings failed with "data/settings must be object" on widgets with no settings (#184). A widget added without settings (for example post-info from add-pro-widget) is stored with an empty settings list, and the tool sent it as a JSON list ([]) while its output schema declares an object, so MCP clients that check the schema rejected the answer. Every EMCP tool now sends an empty value as a JSON object ({}) wherever its output schema declares an object, which also covers element previews in find-element, kit settings in get-global-settings and the other tools with object fields.
• Fixed: get-post failed with "data/meta must be object" on posts without custom fields or terms (#185). An empty field list or term list went out as a JSON list ([]) while the tool's output schema declares an object, so MCP clients rejected the whole answer and returned no post. Both now always go out as JSON objects ({} when empty).
• Fixed: PHP snippet tools still showed empty values on sites with W3 Total Cache's object cache on Valkey (#182). The cache kept an empty copy of a new snippet's settings, so create-php-snippet, get-php-snippet and list-php-snippets answered an empty context, hook, priority and code, and update-php-snippet without code failed with "The snippet is empty". The 3.21.4 fix asked the cache to drop that copy, which this cache ignored. The snippet tools now read a snippet's own settings straight from the database (one query for a whole list) and clear the post's cache after every write. An update without code on a snippet that really has no stored code now says to pass code.
• Fixed: update-global-typography added a duplicate global instead of changing an existing one, and still reported success (#186). The tool only writes the kit's custom typography list, so a system slot id such as primary became a second global with the same id while the real system typography stayed unchanged. System typography ids (primary, secondary, text, accent and any other id in the kit's system typography) are now refused with a clear error pointing to replace-system-typography (Pro) or Elementor Site Settings, matching what update-global-colors does for system colors. Existing custom ids are updated in place, an id repeated in one call is stored once, and both tools now return which ids were updated and which were added.
• Fixed: The WordPress admin menu collapsed every time an EMCP screen opened (user report). EMCP screens folded the left menu unless you had expanded it on purpose before, so for most people it shrank to icons. EMCP screens now follow WordPress's own setting: the menu stays open unless you collapse it, and stays collapsed if you did.
• Fixed: Post Title, Post Excerpt and other Elementor Pro theme widgets added with add-pro-widget or build-page showed placeholder text or nothing (#183). Elementor's editor binds these widgets to their dynamic tag (post title, post excerpt, site title and site URL, site logo, featured image, archive and page title, WooCommerce product title and category image) when you drop them on the canvas, but the tools saved them without it, so the front end printed "Add Your Heading Text Here" or left the widget out. New widgets now get the same default tag the editor gives them. A value or dynamic tag you pass for that setting is kept as sent.