Visual Composer MCP integration
Visual Composer MCP integration
Connect Visual Composer to AI with EMCP Pro. Discover elements, stage native layouts with matching HTML and CSS, and publish after editor review.
Pro integrationVisual Composer Website Builder 45.16.2 through 45.16.x
Visual Composer workflow to review
| Step | Review point |
|---|---|
| Inspect local elements | Read installed schemas and existing editable and rendered artifacts. |
| Stage matching artifacts | Prepare a native graph with matching wrappers and page CSS. |
| Review and publish | Check a native editor save and frontend responsive styles before publication. |
A practical place to start
Inspect local elements. Then build and review.
- 01
Inspect local elements
Read installed schemas and existing editable and rendered artifacts.
- 02
Stage matching artifacts
Prepare a native graph with matching wrappers and page CSS.
- 03
Review and publish
Check a native editor save and frontend responsive styles before publication.
Built for Visual Composer
Visual Composer content your team can keep editing
Visual Composer Website Builder stores its editable graph separately from frontend HTML. EMCP Pro treats those as a pair: a staged document needs native elements plus matching rendered HTML and page CSS. Changing the graph alone is not a complete page update.
Work with the native design model
Installed schemas are read from local builder bundles. Tools cover drafts, complete document staging, local library discovery, recovery, discard and explicit publication. The authoring contract does not compile arbitrary React elements on the PHP server.
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 Visual Composer tool reference for operations and tested boundaries. The page-builder setup guide explains selection and Gutenberg coexistence.
Get connected
Put Visual Composer in your AI’s toolkit.
- 1
Check installed versions
Visual Composer Website Builder 45.16.2 through 45.16.x. 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 Visual Composer tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about Visual Composer, supported operations, and the workflow on your site.
Is this WPBakery?
No. Visual Composer Website Builder and WPBakery have separate adapters and storage formats.
Can I save only element JSON?
No. The frontend also needs matching rendered HTML and CSS. Staging keeps those artifacts together.
Does it download Hub elements?
No. Discovery uses installed elements and local libraries. Remote Hub downloads and optional Theme Builder assignments are excluded.
Your tools. Your WordPress site.