A brief becomes a real page.Kadence MCP integration
Kadence MCP integration
Inspect and update Kadence theme palettes, typography, layout and buttons with AI. Kadence Blocks and Design Library patterns have separate tools.
Free integrationActive Kadence
scoped theme update
| Step | Check |
|---|---|
| Inspect native settings | Read current values and the supported field definitions before changing site-wide design. |
| Update the supported fields | Enable the relevant write tool and submit only the reviewed settings. |
| Verify the rendered theme | Read the saved values and inspect the frontend, including small-screen layout. |
A practical place to start
Inspect settings before changing the theme.
- 01
Inspect native settings
Read current values and the supported field definitions before changing site-wide design.
- 02
Update the supported fields
Enable the relevant write tool and submit only the reviewed settings.
- 03
Verify the rendered theme
Read the saved values and inspect the frontend, including small-screen layout.
Built for Kadence
Theme settings with a defined scope
Kadence theme settings use structured values and references to palette slots. Read the palette and field shapes before changing typography, spacing or button colors. The theme adapter preserves settings outside its allowlist.
Keep block content independent
The kadence-blocks integration has its own tools and toggle. Selecting another standalone builder does not turn theme configuration into builder content, and changing a block does not require rewriting theme options.
Review site-wide changes
Kadence must be the active theme. Block placement and Design Library patterns belong to the independent Kadence Blocks integration. Read back changed values and inspect the frontend. A theme change can affect many pages even when the request changes one setting.
Read the Kadence tool reference for operations, permissions and limitations.
Get connected
Put Kadence in your AI’s toolkit.
- 1
Activate the native dependency
Activate the Kadence theme. Included in free EMCP.
- 2
Inspect tool access
Use Themes for theme settings. Enable only the required writes.
- 3
Keep block editing separate
Enable kadence-blocks independently in Page Builders when you need its Gutenberg tools.
Then connect Claude Code, Claude Desktop, or Cursor to use the Kadence tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about Kadence, supported operations, and the workflow on your site.
Does this include block editing?
Block editing has its own independent integration. Use the linked block-pack tools for page content and these tools for theme configuration.
Can it update every Customizer field?
No. Writes use a curated native setting allowlist. Inspect the live schema and supported scope before proposing changes.
What access is required?
Kadence must be the active theme. Block placement and Design Library patterns belong to the independent Kadence Blocks integration.
Your tools. Your WordPress site.