Kadence
These abilities register when Kadence 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
Kadence registers 5 abilities: 4 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
Read and update Kadence settings, inspect Theme JSON, and discover available Customizer controls with plugin-aware WPPilot Pro tools.
Before you rely on it: Prefer small, scoped setting changes and verify them across desktop and mobile templates.
Typical workflows
- Inspect Theme JSON before changing design tokens
- Compare active settings with intended brand rules
- Update a scoped Customizer setting and verify affected templates
The Kadence 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 Kadence 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/kadence-check-setupCheck Kadence Setup | Diagnostic snapshot of the Kadence theme install: theme active flag + version + minimum supported, the storage type and option name Kadence is using (theme_mod vs option), the activation flag for the Kadence-introduced CPTs the integration touches (kadence_header, kadence_navigation, kadence_form), and the active palette name. Call once at the start of any session that will read or write Kadence theme settings, build a header/footer, or assemble an Advanced Form. Lean by design — does NOT echo the full settings or palette here; call kadence-get-settings / kadence-list-customizer-settings for actual content. |
wppilot/kadence-get-settingsGet Kadence Settings | Reads the current values (defaults merged with any user overrides) for an explicit list of Kadence theme setting keys. Resolves through Kadence's Options Component so the response reflects whatever the user has changed in the Customizer — not just the bare theme_mods. Keys that do not exist on this install (typos, plugin-gated settings) are listed under unknown_keys for surfacing rather than silently dropped. Discover available keys via kadence-list-customizer-settings; settings are also returned with their inferred type so the agent can compose a sound kadence-edit-settings payload without a separate type lookup. |
wppilot/kadence-get-theme-jsonGet Kadence theme.json | Returns the resolved WP theme.json view of the Kadence theme — the contract the block editor reads to populate its color, typography, spacing, layout, and shadow controls. Unlike kadence-get-settings (which surfaces Kadence-specific Customizer keys), this ability surfaces the WP-native global styles + settings tree that core Gutenberg and any block-aware integration consume. Three slices are returned: settings (the per-feature configuration: appearanceTools, color palette, typography, spacing, layout, shadow), styles (the resolved styles: per-block, per-element, root spacing), and presets (a flat catalogue of the named color / gradient / font-size / spacing presets the agent can reference via slug). Read-only — does not write theme.json. To override theme.json values at the user-style layer, use the wp_update_post path on the active wp_global_styles post (out of scope for this ability). |
wppilot/kadence-list-customizer-settingsList Kadence Customizer Settings | Enumerates the Kadence theme settings as a grouped catalogue. Kadence exposes ~1000 individual setting keys (typography, colors, layout, header, footer, page-title, archive, product, mobile menu, etc.); returning every key with its default would overflow most contexts. This ability returns a compact areas[] overview by default — {name, count} per area — and lets the agent drill down by passing area=<name> to get the keys for that area only, optionally with their inferred type and default value via with_defaults=true. The list-only response is safe to call any time; pass area only when you actually need that area's keys. |
Writes
Gated by the active profile and your WordPress capabilities. Rate limited to 120 per minute per credential.
| Ability | What it does |
|---|---|
wppilot/kadence-edit-settingsEdit Kadence Settings | Patches Kadence theme setting values. Partial / merge update — only the keys passed in settings are changed; every other setting keeps its current value. Each pair writes through the storage strategy Kadence is configured for (theme_mod or option — see kadence-check-setup.storage.type). Unknown keys (not in Kadence's defaults map on this install) are NOT written and surface under unknown_keys in the response. Type mismatches between the input value and the registered default (e.g. passing a string where the default is an array) are surfaced under warnings[] and the write still happens — Kadence accepts both shapes for some keys, so the warning is informational. Reads after this call return the new values immediately. |