Releases

Changelog.

What shipped in each version of the plugin and in EMCP Cloud.

v3.22.07 changes

Bricks templates join the Templates library, and EMCP now builds and styles Uncode sites.

  • 01NewProUncode. On sites running the Uncode theme, agents can build pages and Content Blocks from Uncode's own elements and its 900 Wireframes sections, and change Uncode's theme options. The WPBakery tools accept 39 Uncode elements (each checked live against Uncode 2.12.8), and edit Content Blocks. A new pair of tools, uncode-read and uncode-write, lists Wireframes with whether each is ready to insert, prepares Uncode's placeholder images, forms and menus when a section needs them, and reads and changes theme options: values are checked by type, the theme's CSS is rebuilt and checked, and a change made in Theme Options at the same moment is never lost. Every option change and every WPBakery save can be undone from History; preparing Wireframes is the one step that cannot. uncode-write ships switched off. Needs Uncode and Uncode Core 2.12.8 or later.
  • 02ProFixed (Pro): WPBakery page saves on Uncode sites changed the page and then reported an error. Uncode's copy of WPBakery names the optimized-asset step differently, so the save stopped after writing the page: the element CSS was not rebuilt and the result was not checked. Saves now use whichever step this WPBakery has, and if anything fails after the first change, the page, its WPBakery settings and its recovery snapshots are put back exactly. A failed save no longer drops the oldest recovery snapshot.
  • 03NewProBricks templates. Ten Bricks designs join the Templates library, next to the Elementor templates, with a Builder switch to show one or the other. Create page makes a draft page that looks like the demo: the template's global classes and variables are added to the site (classes and variables you already have are never changed), its images are copied into the Media Library, and its fonts and theme style apply to that page only. Add to library puts the layout in Bricks templates instead. Needs Bricks 2.4 or later. Each apply can be undone from History, which removes the page and whatever the apply added, unless another page still uses it.
  • 04FixedElementor content added over MCP to a classic page did not show on the front end (#187). apply-template and the other Elementor write tools saved the elements, but Elementor marks a page as built with Elementor only when its editor opens, so a page never opened there kept rendering as a classic page. Every Elementor save now marks the page as built with Elementor, the same as create-page.
  • 05NewThe widget tools follow Elementor's Element Manager (#188). Elementor does not render a widget switched off in Elementor > Element Manager, yet the tools added one and returned its id. list-widgets and get-widget-schema now mark disabled widgets, list-widgets lists every disabled element (atomic and third-party ones included), and add-free-widget, add-pro-widget and the atomic add tools refuse a disabled widget with an error that says where to switch it back on.
  • 06Fixedsideload-image saved a file from a link without an extension as .jpg, so PDFs and other files were refused (#189). The file is now named from the server's Content-Disposition filename, then the URL, with the extension taken from the file's real type. The tool's description now says it takes any file type WordPress allows and streams large files that are too big for upload-media, and it gains filename and timeout (5 to 300 seconds, default 30) inputs.
  • 07FixedAn empty Screen Options tab covered the top of EMCP screens (user report). A plugin or theme that registers meta boxes on every admin screen made WordPress add the tab over the promo bar. EMCP screens have no screen options and their own help button, so WordPress's Screen Options and Help tabs are now off there; other admin screens keep them.
v3.21.56 changes

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.

  • 01Fixedget-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.
  • 02Fixedget-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).
  • 03FixedPHP 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.
  • 04FixedProupdate-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.
  • 05FixedThe 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.
  • 06FixedPost 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.
v3.21.44 changes

Claude connects on sites where another OAuth plugin owns the shared discovery address, plus three fixes from user reports.

  • 01FixedClaude could not connect on sites where another plugin answers the shared OAuth discovery address (reported in a support ticket; the same cause as earlier Tropk and SiteGround reports). Claude signed in with the other plugin, so EMCP rejected its tokens and the MCP Log showed every request failing with "Sorry, you are not allowed to do that." EMCP's OAuth issuer is now its own REST address (/wp-json/emcp-tools/oauth/v1), so clients look for its settings at addresses only EMCP answers. Sites with plain permalinks keep the old address. Existing connections keep working; a client that failed this way needs to be removed and added again.
  • 02Fixedadd-atomic-paragraph removed inline HTML (#180). Atomic paragraphs, headings and buttons lost every tag, so bold text and links came out as plain text. They now keep the inline tags Elementor accepts for each element (for a paragraph: strong, em, a, span, br, lists and similar) and remove everything else, including scripts and event attributes.
  • 03FixedThe query tool refused a SELECT that used REPLACE() or INSERT() (#181). The read-only check treated the string functions as the write statements of the same name. They are now allowed when followed by an opening parenthesis; REPLACE INTO and INSERT INTO are still refused.
  • 04FixedPHP snippet tools returned empty values right after a write on sites with a persistent object cache (#182). create-php-snippet answered with an empty context and code, and update-php-snippet without code could fail or reset the run context. The snippet's stored values are now read fresh from the database around every write.
v3.21.35 changesRead the blog

Quiet sites stay connected to EMCP Cloud, page builders no longer disappear after a vendor update, and Pro gains Flatsome and Amelia Pro.

  • 01NewProFlatsome. 16 builder tools build pages with Flatsome Site Builder through its own block schemas, serializer and renderer, and separate read and write tools handle the Flatsome Block Theme's global styles, templates and template parts. It needs both Flatsome packages at 1.0.0-beta.7 or later, works with child themes, and its writes start disabled. Writes are recorded in History with conflict-aware undo.
  • 02NewProAmelia Pro 9.9.1 or later is supported. The existing amelia-read and amelia-write tools now run on Amelia Pro as well as Lite, tested through 9.9.2, with extras, galleries, package prices and deletion links covered by undo. Writes that would reach outside WordPress or that undo could not restore are refused: remote calendar and meeting effects, connected people, linked WordPress profiles, and package, resource or ticket bookings.
  • 03FixedQuiet sites needed a reconnect in wp-admin (reported by a customer). A Gateway credential issued for 10 years dropped to 30 days the first time it rotated, so a month without traffic ended it, and the site's Cloud connection only renewed when the site used Cloud. Rotation now keeps the long life, live credentials already cut short get it back once, and a daily background check renews a connection that has not renewed for a week. A site that already lapsed needs one last reconnect. A connection made before 3.19 starts renewing after its next Cloud call. The check runs on WP-Cron, so a site with no visits at all can still lapse.
  • 04FixedProA page builder showed "Not detected" after the vendor released a newer version (Pro) (reported by a customer on Divi 5.18). Builders and block packs now accept their tested version and every later one, across 11 integrations, and get-context reports the tested version. Other plugin integrations with History and undo keep their verified version ranges.
  • 05ImprovedCompact tool mode now reports which tools only read.
v3.21.26 changes

Fixes for pulling settings from EMCP Cloud, for wp-admin errors that non-administrators saw on some sites, and corrected ChatGPT App connection steps.

  • 01FixedEvery wp-admin page showed "There has been a critical error" for users who are not administrators on sites where another plugin adds a menu item with no capability (reported in #174). WordPress passes that empty capability to every permission filter, and four EMCP filters only accepted text, so PHP stopped the page. They now pass anything that is not a capability name through unchanged. Administrators were not affected.
  • 02FixedPulling settings from EMCP Cloud did nothing or failed without saying why. With nothing pushed yet, the Connection screen said "try again or reconnect", which never helps: it now says to push from the site you want to copy first. A pull that applies nothing is reported as an error instead of a success, and a successful pull says how many settings it applied. Every other sync error gets its own message.
  • 03FixedPulling settings pushed from an older version switched on tools that newer versions ship switched off. Pushes now record their source and tool defaults, and a pull keeps the newer default-off tools off (unless new tools are set to turn on after updates).
  • 04ImprovedA settings pull is recorded in History, so one click undoes it.
  • 05FixedThe cloud-config-sync MCP tool returned pulled settings without applying them, and its push stored whatever data the agent sent over the settings shared by every site. For settings it now pushes this site's own settings and applies pulls, like the Connection screen.
  • 06FixedThe ChatGPT App steps on the Connection screen now match the app: Plugins, Add, Add custom MCP server, keep OAuth, Create as a plugin, then Approve on your site. The Application password guide uses Settings, Plugins, MCPs, Add and has no Restart step (#175).

Showing 5 of 92 releases

Your EMCP guide

Answers from our docs

YOUR CHAT, YOUR CHOICE

Before we chat

MSR Builds processes your question and up to four recent messages on our server to answer from the EMCP docs. AI is optional and needs your separate permission.

The chat is kept in this page's memory, not saved as a conversation in our database or browser storage. Our hosting and security services process connection information, such as your IP address, to prevent abuse.

Cloudflare Turnstile checks your browser and connection to prevent automated abuse when you send a question. No login is required.

Please leave out personal, sensitive or confidential information, passwords and API keys.

You can withdraw consent and clear this page's chat at any time. This cannot undo a request already sent or erase provider/security records.

Chat privacy, retention & your rights ↗ · Privacy contact

Starting chat consents to this processing. You can browse our docs without using the chat.