Kirki 6 MCP integration
Kirki 6 MCP integration
Connect AI to Kirki 6 with EMCP Pro. Build native canvas pages, edit responsive styles, inspect local components, and publish staged versions.
Pro integrationKirki 6.3.1 through 6.3.x with the native visual builder
Kirki 6 workflow to review
| Step | Review point |
|---|---|
| Discover graphs and viewports | Inspect starter elements, local styles and native breakpoints. |
| Save a staged canvas | Build native elements and page-local style blocks, then read the latest stage. |
| Publish the reviewed version | Check native editor and frontend output before publishing. |
A practical place to start
Discover graphs and viewports. Then build and review.
- 01
Discover graphs and viewports
Inspect starter elements, local styles and native breakpoints.
- 02
Save a staged canvas
Build native elements and page-local style blocks, then read the latest stage.
- 03
Publish the reviewed version
Check native editor and frontend output before publishing.
Built for Kirki 6
Kirki 6 content your team can keep editing
This integration targets Kirki 6’s visual page builder. EMCP Pro works with its native element graph and separate style blocks, creating canvas drafts and staging changes before explicit publication. It is not a general adapter for older Customizer-only installations.
Work with the native design model
Read the design system and installed viewports before styling. Library discovery covers templates, header and footer symbols, popups and utility pages in their native envelopes. Content Manager collections and fields are discoverable, while CMS schema changes remain outside page authoring.
Connect your AI to the right tools
Open EMCP Tools > Page Builders and select this standalone builder. Gutenberg and enabled block packs remain available. Reconnect your MCP client, read context and schemas, and enable the write tools needed for the task. Start with a draft and inspect the native editor. Available in EMCP 3.17.0. Check compatibility before updating the vendor builder; an unsupported version can prevent its tools from appearing.
Read the Kirki 6 tool reference for operations and tested boundaries. The page-builder setup guide explains selection and Gutenberg coexistence.
Get connected
Put Kirki 6 in your AI’s toolkit.
- 1
Check installed versions
Kirki 6.3.1 through 6.3.x with the native visual builder. EMCP Pro is required.
- 2
Enable the integration
Open EMCP Tools > Page Builders and select this standalone builder. Gutenberg and enabled block packs remain available.
- 3
Connect and inspect
Reconnect your MCP client, read context and schemas, and enable the write tools needed for the task. Start with a draft and inspect the native editor.
Then connect Claude Code, Claude Desktop, or Cursor to use the Kirki 6 tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about Kirki 6, supported operations, and the workflow on your site.
Is this the older Customizer framework?
No. These tools target the Kirki 6 visual builder and its graph, staging and local styles.
Do saves immediately publish?
Content and style changes are staged. publish-page publishes the latest stage and the WordPress page.
Can page tools edit a shared header symbol?
No. Symbols have their own envelope. Library reads do not authorize shared edits or global assignments.
Your tools. Your WordPress site.