Themes and blocksPro
GreenShift globals, edited without exposing its keys
GreenShift keeps design tokens and third-party API keys in the same settings option. GoBuildWP lets an agent change the colours and CSS variables in it while the keys are never returned, logged or copied anywhere.
Included since GoBuildWP Pro 1.14.0.
Reads
- GreenShift version and registered block count
- The block manager: which blocks are disabled, and for which roles
- Per-block nesting schema
- Global colours and CSS variables, with API keys left out
Writes, after confirmation
- Add, change or remove global colours, merged or as a full replacement
- Add, update or remove global CSS variables
- Edition
- Pro 1.14.0
- Abilities
- 6
- Requires
- WordPress 6.9+, PHP 8.0+, GreenShift 12.8.5+
- Agent skill
greenshift-integration
Abilities
The 6 GreenShift abilities
Each one is its own MCP ability with its own input schema, and the bundled GreenShift skill tells the agent which to call, when a dry run comes first and what it must show you before confirming.
Inspect4
greenshift-check-setupCheck GreenShift Setupgreenshift-get-block-schemaGet GreenShift Block Schemagreenshift-get-global-settingsGet GreenShift Global Settingsgreenshift-list-blocksList GreenShift Blocks
Create and change0
None in this module.
Destructive2
greenshift-set-colorsSet GreenShift Global Colorsgreenshift-set-variablesSet GreenShift Global Variables
Names are shown without the wppilot/ namespace and grouped by each ability's source annotation. Full descriptions join the ability reference when the release is published.
Safety
How GreenShift changes are confirmed and put back
Not undoable, previous values returned
The settings option also stores API credentials, and GoBuildWP never copies credentials into the change ledger. So both writes are marked not undoable and return the previous colours or variables, which the agent uses to put them back.
Requirements
- WordPress and PHP
- 6.9+ and 8.0+
- GoBuildWP
- Pro 1.14.0 or later
- GreenShift
- 12.8.5+
Out of reach by design
- Stored API keys are never returned or written
- Block trees inside posts go through the base Gutenberg abilities
- Custom CSS is reported as set or not, not edited
- The site's safety profile, the connected user's capabilities and per-ability settings still apply on top of these limits.
Questions
GreenShift and GoBuildWP, answered
GreenShift has its own abilities. Why use these?
The GoBuildWP ones require confirm=true, keep colours in the format GreenShift's frontend prints, and never return the API keys stored in the same option.
How do I undo a GreenShift colour change?
Ask the agent to restore it. The write returned the previous values, so it can set them again. There is no one-click undo for this module.
Is GreenShift support live?
Yes. It is part of GoBuildWP Pro 1.14.0 and later.
GreenShift is a separate product. Listing an integration does not imply a vendor partnership or endorsement.
Get ready before GreenShift support lands
Connect your site with GoBuildWP Free today and check what an agent can already read. The GreenShift abilities arrive with that Pro update and switch on when GreenShift 12.8.5 or later is active.