An agent can read the site's Greenshift color palette, saved element styles, custom CSS classes, raw Stylebook CSS, and design variables, and can add or replace those values, effectively editing the site's global design system.
View Greenshift on WordPress.org
Greenshift must be installed and active on WordPress 6.9 or newer, since its readme already lists that as the minimum. Reading the color palette, element styles, custom classes, custom CSS, or Stylebook variables needs edit_posts, while changing any of them needs manage_options.
Matches easymcpai's listed count of 10; verified directly from greenshift-animation-and-page-builder-blocks/includes/abilities.php. None of the five write abilities set an explicit annotations array in the evidence, so the Bridge's fail-safe rule classifies them as destructive rather than write.
Grouped by what each one can change. Every one starts off until you enable it.
Returns the site's GreenShift custom color palette.
Returns GreenShift's saved global element style definitions.
Returns the reusable custom CSS classes defined in GreenShift.
Returns the raw custom CSS stored in GreenShift's Stylebook.
Returns GreenShift's Stylebook design variables.
Replaces the site's GreenShift custom color palette.
Replaces GreenShift's saved global element style definitions.
Adds a new reusable custom CSS class to GreenShift's class list.
Replaces the raw custom CSS stored in GreenShift's Stylebook.
Adds a new design variable to GreenShift's Stylebook.
No abilities match that search.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. Greenshift registers its own abilities; this plugin discovers and governs them.
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Every ability from Greenshift starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Yes. Greenshift registers 10 abilities over its global design system with real permission checks, so the Bridge can expose them once an operator turns each one on.
Yes, unconditionally, once Greenshift is active. Nothing else has to be configured for the Bridge to discover them.
Greenshift must be installed and active on WordPress 6.9 or newer, since its readme already lists that as the minimum. Reading the color palette, element styles, custom classes, custom CSS, or Stylebook variables needs edit_posts, while changing any of them needs manage_options.
An agent can read and edit the structure of Elementor-built pages, list and inspect widget and component schemas, manage the site's shared global CSS classes and design-token variables, build whole page layouts from a composition description, and publish or preview documents.
Once enabled, an agent can read and manage HFE header/footer/block templates and Elementor pages end to end: list, create, update, duplicate, delete and restore templates and pages, build and edit Elementor layouts widget by widget, toggle widgets and extensions, set display rules and theme compatibility, read the site's design tokens, and clear the Elementor CSS cache.
An agent can list and insert ElementsKit's widgets and templates into Elementor pages, scaffold new pages, headers, footers and custom widgets, and manage mega menus, all with an unauthenticated caller in mind since the code carries no readonly or destructive annotations.
Verified from Greenshift's own free wordpress.org code on 28 September 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, wpsoul or Greenshift. Back to the full directory.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.