Manage ElementsKit Elementor Addons with AI

What we learned testing it

Behavior the ability descriptions do not mention.

• ElementsKit 4.0.8 registers its tools with the WordPress Abilities API but keeps them off its REST API, so WPVibe's discover_abilities and run_ability don't see them. WPVibe calls the same tools through ElementsKit's own route, POST /elementskit/v1/mcp-proxy, with rest_api_write. The recipes say so in their prompts.
• ElementsKit shows the oldest header (or footer) that is switched on. A new one switched on while an older one is still on does not appear, though its reply says it was activated site-wide. Switch the old one off first.
• create-header-footer switches the new header or footer on for the whole site by default, and create-page publishes the page at once for anyone who can publish. Neither asks for approval through WPVibe. The recipes create headers switched off and turn them on after your yes.
• On many themes, ElementsKit's header replaces the theme's header.php (on Astra, GeneratePress, OceanWP, Neve and a few others it uses the theme's own header hooks instead, by ElementsKit's code). Anything the theme writes in header.php itself is lost, including stylesheet links written there by hand: on our classic test theme, the classes on the <body> tag that set its font and background. Switching the header off brought them back.
• Mega menus show only inside ElementsKit's Nav Menu widget. Your theme's own menus ignore them, even with the menu assigned to a theme location.
• update-mega-menu-item replaces all of the item's mega menu settings. Send every setting you want kept, not only the one that changes.
• create-mega-menu adds a new item to the menu it is given (a new menu when none is named) and switches mega menu on for that whole menu. Given no panel content, it fills the panel with a demo layout from the library (Mega Menu - Mens Fashion).
• Adding a section or a library layout to a page not built with Elementor replaced the page's content in testing. Use them on Elementor pages only; those carry the class elementor-page on <body>.
• Each change saves a revision of the new version. The version from before is in Elementor's History > Revisions only if the page had a revision already.
• A widget type Elementor doesn't know is dropped from an element tree without an error. list-widgets gives ElementsKit's exact names: the Nav Menu widget is ekit-nav-menu.
• By ElementsKit's code (we tested on a classic theme only): its header never shows on a block theme, pages on Elementor's Canvas template show no ElementsKit header, and mega menu panels show only on top-level menu items.
• On tablets and phones, ElementsKit's Nav Menu opens in a light panel. A light link color set for desktop does not carry over, which keeps the links readable, but the menu button keeps its default dark gray unless you set its color. Check a dark header on a phone.
• Switching mega menu on for a menu shows every panel and badge already saved on its items, not only the new one.
• ElementsKit keeps which header is on and which menus use mega menu in WordPress's object cache. On a host with Redis or Memcached, a change may not show until that cache is flushed (read from ElementsKit's code; our test site has no object cache).
• Headers and footers from the template library bring demo content: a placeholder logo added to your media library, a menu from the demo site, and demo contact and social links. The library list is 1,692 layouts with no filter, and WPVibe shows only the first few of them.
• insert-widget failed with a PHP error on Elementor 4.3.4 in testing and changed nothing, so it isn't listed. Build with an element tree instead.
• create-custom-widget writes a PHP file to your uploads folder. On our test site, which keeps uploads in cloud storage (Infinite Uploads), the widget it made broke every page until we unpublished it, so it isn't listed. Custom widgets built in wp-admin write the same file, so on a site that keeps uploads in cloud storage, try them on a staging copy first.
• The template route that switches a header on or off (GET /elementskit/v1/my-template/update/<id>) overwrites every field it is sent. Read the template first and send its title, type and conditions back with the change.