ThemesPro
Blocksy MCP: change registered Customizer settings, validated by Blocksy
Blocksy is a Customizer-first classic theme, so Blocksy MCP access means working with the settings it registers there. GoBuildWP asks WordPress's Customizer for Blocksy's live schema, returns values and defaults, and writes only settings marked writable, each passed through Blocksy's own validation and sanitising callbacks. Content Blocks, display conditions and other Companion Pro features are reported as out of scope rather than approximated.
Make the Blocksy footer background our navy and widen the site container slightly, then show me exactly what changed.
wppilot/theme-bridge-check-setupReadReturns adapter blocksy and whether this is a child theme, which decides which theme_mods row is being edited.
wppilot/theme-bridge-list-customizer-settingsReadQueried for footer and then container, with writable_only true, to get the real setting ids and current values.
wppilot/theme-bridge-update-customizer-settingsWritePatches the two ids; any id Blocksy did not register comes back in rejected with a reason.
wppilot/theme-bridge-list-customizer-settingsReadRe-read for the same ids to confirm the stored, sanitised values.
- Edition
- Pro
- Abilities
- 4
- Requires
- WordPress 6.9+, PHP 8.0+
Abilities
The bridge, as it behaves on Blocksy
| Ability | What it does here | Undo and limits |
|---|---|---|
theme-bridge-check-setup | Matches the active or parent theme folder to blocksy and returns the adapter, child-theme state, how many theme_mod settings Blocksy registered and how many are writable. | Read-only. Its boundary notice names Blocksy Content Blocks and Conditions as surfaces it will not write. |
theme-bridge-list-customizer-settings | Searches Blocksy's registered settings by term, such as colour, header or woocommerce, with current value, default, transport and capability for each row. | Values over 8 KiB come back as truncated with their size; sensitive ids are redacted. |
theme-bridge-update-customizer-settings | Sets up to 50 Blocksy settings in one call, skipping ones already at the target value, and returns changed, unchanged and rejected lists. | Undo restores the theme_mods row of the active stylesheet. Unregistered or option-backed ids are rejected, not guessed. |
Reference: /docs/reference/theme-bridge
Shared theme bridge; do not add this count across themes. Edition and effect labels describe the source catalogue. The installed schema, dependency versions, licence, WordPress capability, safety profile and per-ability policy determine availability; labels alone do not prove confirmation or recovery.
Data model
Per-stylesheet theme mods, with a child-theme trap
Settings Blocksy registers as theme mods are stored in the theme_mods row named after the active stylesheet. Blocksy's own documentation points out the consequence: WordPress keeps Customizer settings separately for the parent and the child theme, so switching to a child theme makes a configured site look reset. Blocksy's answer is its Copy Options tool, which, like export and import, needs the Blocksy Companion plugin.
The bridge writes the same row the Customizer does, holding a per-site lock so two writes cannot interleave, and calls each setting's save so Blocksy's own hooks run. Everything Companion Pro adds on top, such as Content Blocks for hooks, pop-ups and templates with display conditions, custom fonts and conditional headers, uses Blocksy's own storage, which this bridge does not touch.
Limits
Blocksy surfaces left alone
- Content Blocks, their display conditions and conditional headers are not created or edited; the skill reports them as unavailable instead of claiming a change.
- Settings whose id reads as custom code, CSS, scripts, tracking, analytics, licence or credentials are read-only and redacted.
- Values are limited to 8 KiB, 100 items per array and four nesting levels; a NUL byte in a string is refused.
- A value Blocksy's sanitiser returns as null is rejected with theme_bridge_sanitize_rejected rather than stored.
Other plugins
Blocksy with builders and WooCommerce
- Blocksy supports Gutenberg, Elementor, Brizy and Beaver Builder for page bodies. The skill hands the body to the editor that owns it and keeps the bridge to site chrome.
- Products and store data go through WooCommerce abilities; the bridge only changes Blocksy's presentation settings for shop templates.
Worked example
A darker footer and wider container on Blocksy
Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.
The footer and container change across the site with one restorable ledger entry. A footer built as a Content Block rather than in the Customizer would not change, and the report would say so.
Four shared bridge names cover three applicable classic Blocksy calls. Check whether the rendered footer comes from the Customizer or a Content Block before editing. Whole-row undo may overwrite newer settings.
theme-bridge-check-setupReturns adapter blocksy and whether this is a child theme, which decides which theme_mods row is being edited.
theme-bridge-list-customizer-settingsQueried for footer and then container, with writable_only true, to get the real setting ids and current values.
theme-bridge-update-customizer-settingsPatches the two ids; any id Blocksy did not register comes back in rejected with a reason.
theme-bridge-list-customizer-settingsRe-read for the same ids to confirm the stored, sanitised values.
Questions
Blocksy questions
Why did my Blocksy settings vanish after activating a child theme?
Customizer settings are stored per stylesheet, so the child starts empty. Blocksy's Copy Options, part of Companion, copies them across; the bridge edits whichever theme is active.
Can an AI create Blocksy Content Blocks?
Not through GoBuildWP today. They are a Companion Pro surface with their own storage and conditions, and the bridge declines rather than guessing.
What happens if the agent sends a colour Blocksy doesn't accept?
Blocksy's own validation or sanitiser runs first; a failing value is listed as rejected with its reason and the other settings in the call still save.
Where these facts come from
GoBuildWP behaviour is taken from the plugin source and the ability reference; third-party details from the vendor documentation below, checked by the GoBuildWP team.
Blocksy is a separate product; no partnership or endorsement is implied.