Theme bridge
These abilities register when Theme bridge is detected on the site and a Pro licence is active. If either is missing the module stays absent rather than failing at call time.
At a glance
Theme bridge registers 4 abilities: 3 that only read, 1 that write, and 0 marked destructive. That split is the practical answer to how much of this module can run unattended. Reads cost nothing and are safe to repeat, so discovery is the part to be generous with; the writes are where review belongs, and the destructive calls stop for an explicit confirmation every single time regardless of which profile is active.
What this module is for
Use WPPilot Pro's typed theme bridge to inspect the active block theme, Theme JSON, and Full Site Editing templates, with reviewable queued changes.
Before you rely on it: Theme-file templates and theme.json remain read-only through the generic bridge. Finalize queued database-backed template changes in the Site Editor and review representative routes and breakpoints.
Typical workflows
- Inventory templates and identify whether each comes from the database or theme files
- Inspect Theme JSON and registered settings before planning a design-system change
- Queue a database-backed template edit for native Site Editor review
The WordPress Block Themes integration page covers the same module from the workflow side, with the capability map and the questions worth asking before a first write.
Availability on your site
The Theme bridge module needs three things at once: WPPilot Free as the MCP foundation, an active Pro licence, and the companion plugin detected on the site. Miss any one and the module does not register, which is deliberate: an ability that appears in the tool list but fails at call time is worse than an ability that was never offered. What the connected agent can actually call is then narrowed twice more: by the safety profile active on the site, and by the WordPress capabilities of the user behind the credential. A read that succeeds for an administrator can be absent entirely for an editor.
Every write these abilities perform is recorded in the change ledger, and destructive calls can be routed through the approval queue so a person signs off before anything is applied. A successful tool result means the operation returned, not that the front end, the cache, and every dependent template are correct: that still needs a look.
Reads
Available in every safety profile, including Read Only. Inspection costs nothing and is not rate limited.
| Ability | What it does |
|---|---|
wppilot/theme-bridge-check-setupCheck Theme Bridge Setup | Detects the active block theme, Blocksy, Neve, or WoodMart; reports the exact live Customizer theme_mod and block-template capabilities; and states which vendor-owned premium surfaces remain fail-closed. Call this before every other theme-bridge ability. |
wppilot/theme-bridge-list-block-assetsList Block Theme Assets | Lists database overrides and theme-file templates/template parts for the active block theme without returning their potentially large content. Database-backed rows include wp_id targets that can be inspected and changed through the base WPPilot Gutenberg review queue. |
wppilot/theme-bridge-list-customizer-settingsList Theme Customizer Settings | Returns a bounded, searchable inventory of live theme_mod settings registered by the active theme and WordPress Customizer. Values larger than 8 KiB are omitted, and credential/code/licensing settings are always redacted and read-only. |
Writes
Gated by the active profile and your WordPress capabilities. Rate limited to 120 per minute per credential.
| Ability | What it does |
|---|---|
wppilot/theme-bridge-update-customizer-settingsUpdate Theme Customizer Settings | Partially updates at most 50 live, registered theme_mod settings through each WP_Customize_Setting validation and sanitization contract. Unknown, option-backed, sensitive, oversized, or unauthorized settings are rejected without arbitrary option writes. |