ThemesPro
Neve MCP: registered Customizer settings for classic Neve
Start any Neve MCP task by checking which Neve you have. Classic Neve keeps its global, typography, blog, header, footer and WooCommerce design in the Customizer, and GoBuildWP's theme bridge reads and patches those registered settings. Neve FSE is a separate block theme that the bridge handles like any other block theme. Neve Pro's Custom Layouts and hooks are reported as unavailable, never approximated.
Increase the body font size on Neve and switch the blog archive to its boxed card layout, nothing else.
wppilot/theme-bridge-check-setupReadConfirms adapter neve, so this is classic Neve rather than Neve FSE.
wppilot/theme-bridge-list-customizer-settingsReadSearched for typography and then blog to find the exact setting ids and their current values.
wppilot/theme-bridge-update-customizer-settingsWriteSends only those two ids; Neve's sanitiser normalises the responsive size object before it is saved.
wppilot/theme-bridge-list-customizer-settingsReadRe-reads both ids to confirm what Neve stored.
- Edition
- Pro
- Abilities
- 4
- Requires
- WordPress 6.9+, PHP 8.0+
Limits
Know these before asking for a Neve change
- Neve Pro Custom Layouts, hooks and their conditions are a separate product surface; the bridge fails closed on them and the skill lists them as blockers.
- The per-post Neve Options sidebar is not part of the bridge; page-level differences may come from there or from the page's editor.
- Only registered theme_mod settings are written, 50 per call at most; option-backed and sensitive settings such as custom code or licence ids are refused.
- Undo restores the whole theme mods row for the active stylesheet, which reverts every bridge setting written in that call.
Data model
Customizer theme mods, a per-post sidebar, and Pro modules
Themeisle documents three places Neve settings live: the Customizer, with Global, Typography, Blog, Header and Footer Builder and WooCommerce sections; the Neve dashboard; and a per-post Neve Options sidebar. The bridge works on the first, reading every setting Neve registers as a theme mod and writing through that setting's own validator and sanitiser. The Pro plugin's modules, including Header Footer Booster, WooCommerce Booster, Blog Booster and Custom Layouts, have their own screens and storage.
Neve FSE is described on WordPress.org as an experimental sister theme with full site editing. Its folder is neve-fse, and the bridge's adapter matches the theme folder name neve exactly, so a Neve FSE site falls to the generic block-theme path: templates and parts are listed and edited through the Gutenberg queue, and Themeisle notes the classic Customizer does not control a Neve FSE header or footer.
Abilities
Theme bridge calls on classic Neve
| Ability | What it does here | Undo and limits |
|---|---|---|
theme-bridge-check-setup | Returns adapter neve for Neve or a Neve child theme, the count of registered and writable theme_mod settings, and the Custom Layouts boundary notice. | Read-only. On Neve FSE the adapter reads block-theme instead. |
theme-bridge-list-customizer-settings | Pages through Neve's Customizer settings by search term, such as typography or blog, with values, defaults and a writable flag per row. | Values above 8 KiB are withheld with their byte size; redacted rows never show a value. |
theme-bridge-update-customizer-settings | Applies a partial patch to Neve's registered settings and reports which changed, which were already at the target and which were refused. | One ledger entry per call restores the theme mods row; a failed save is reported per setting, not hidden. |
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.
Worked example
Bigger body text and a boxed blog layout on Neve
Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.
Body text and blog cards change wherever those global settings apply. A single post that sets its own options in the Neve Options sidebar may still look different, which the agent reports rather than treating as a failed write.
The four shared theme-bridge names include three applicable classic Neve calls. For FSE use Gutenberg queue prerequisites. Reread the settings and inspect rendered output; whole-row recovery can overwrite newer edits.
theme-bridge-check-setupConfirms adapter neve, so this is classic Neve rather than Neve FSE.
theme-bridge-list-customizer-settingsSearched for typography and then blog to find the exact setting ids and their current values.
theme-bridge-update-customizer-settingsSends only those two ids; Neve's sanitiser normalises the responsive size object before it is saved.
theme-bridge-list-customizer-settingsRe-reads both ids to confirm what Neve stored.
Other plugins
Neve beside builders
- Custom Layouts can be built with Gutenberg, Elementor, Beaver Builder or Brizy, according to Themeisle; the page or layout body stays with that editor's own abilities.
- WooCommerce product and order data never pass through the bridge; only Neve's WooCommerce presentation settings in the Customizer do.
Questions
Neve questions
Does GoBuildWP support Neve FSE?
Yes, as a block theme: its templates and parts are listed and edited through the Gutenberg queue. The Neve Customizer workflow does not apply to it.
Can an AI edit Neve Pro Custom Layouts?
No. They are posts with conditional display rules owned by Neve Pro, and the bridge will not write them or claim a hook condition changed.
Why does one Neve page ignore a global change?
Per-post Neve Options or the page's builder can override the global Customizer layer. Check the page's editor before assuming the setting did not 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.
Neve is a separate product; no partnership or endorsement is implied.