EMCP Tools 3.15.0
Inspect public page HTML, recover stale Elementor styling, and manage native WooCommerce brands through MCP. This release also fixes Navigator labels and makes two common layout pitfalls visible to agents.
Added
- Public front-end HTML inspection with
get-page-html: bounded UTF-8 chunks, a continuation hash, credential-free requests, and same-origin checks on every redirect. Accepts a URL or published post ID and defaults to the front page. Returns server-rendered HTML; it does not execute JavaScript. #132 regenerate-css: invalidate one page's generated CSS, render/asset data, and local atomic styles, or explicitly clear caches site-wide. The tool ships disabled by default. Page scope requires edit permission; site scope requires administrator permission andconfirm:true. Caches rebuild on the next frontend request. CDN and third-party caches are not purged. #136- Pro: native WooCommerce brand list/get/create/update operations inside
woo-readandwoo-write, with no-write dry runs, duplicate checks, and validated image attachment IDs. Responses include term and archive identifiers for the existing media and SEO term-tool workflow. #137
Fixed
- Navigator labels use the correct storage for classic versus atomic Elementor elements. The dedicated label tool reads back the saved value before reporting success; universal and batch updates use the same type-aware mapping. #133
- Layout, widget, batch, and composite-build responses warn when dimensions mix blank and specified sides, which can cause Elementor to omit the whole CSS rule. Values remain unchanged to preserve inheritance. #134
- Grid discovery and creation now explain Elementor's two-row default and the explicit single-row setting:
grid_rows_grid: {"unit":"fr","size":1}insidesettings. #135
Scope and upgrade notes
- Enable
regenerate-cssunder Tools → Page Management when needed. No page content is rewritten by the upgrade. - WooCommerce Brands support targets the native
product_brandtaxonomy and/wc/v3/products/brandsAPI. Third-party brand taxonomies are refused. Use the existing sideload tool for remote logos and the active SEO plugin's term tools for SEO metadata; this is not a single-call SEO/logo importer. - The MCP proxy remains at 1.11.0; no npm release is required.
- Requirements remain WordPress 6.9+, PHP 8.1+, and optional Elementor 3.20+ (4.0+ for atomic tools).
Validation
The release passes the PHP and proxy test suites plus 23 local WooCommerce Brands and Rank Math SEO E2E checks, including HTTPS MCP workflows and rendered archive metadata.