Visual Composer MCP tools
Available in EMCP 3.17.0. 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.
Requirements and setup
Section titled “Requirements and setup”- Check installed versions. Visual Composer Website Builder 45.16.2 through 45.16.x. EMCP Pro is required.
- Enable the integration. Open EMCP Tools > Page Builders and select this standalone builder. Gutenberg and enabled block packs remain available.
- 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.
Native workflow
Section titled “Native workflow”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.
Inspect local elements
Section titled “Inspect local elements”Read installed schemas and existing editable and rendered artifacts.
Stage matching artifacts
Section titled “Stage matching artifacts”Prepare a native graph with matching wrappers and page CSS.
Review and publish
Section titled “Review and publish”Check a native editor save and frontend responsive styles before publication.
Tool reference
Section titled “Tool reference”All names use the emcp-tools/ namespace. Read the live input schema for optional fields, enums, limits and confirmation requirements; this table lists required inputs only.
| Tool | Access | Purpose | Required inputs |
|---|---|---|---|
visual-composer-get-context | Read | Read installed version, native access and optional feature availability. | None |
visual-composer-list-elements | Read | Discover installed elements without downloading Hub assets. | None |
visual-composer-get-element-schema | Read | Read the installed element attribute schema and native defaults. | tag |
visual-composer-list-pages | Read | List accessible native pages. | None |
visual-composer-get-page | Read | Read native published content, staged document, editor URL and current hash. | post_id |
visual-composer-create-page | Write | Create an empty native draft page. | title |
visual-composer-stage-document | Write | Stage paired native elements, rendered HTML and page CSS. All three artifacts are required. Does not change the live page. Read the skill and schemas first. | post_id, expected_hash, elements, html, css |
visual-composer-get-page-styles | Read | Read staged and published page CSS. | post_id |
visual-composer-get-design-settings | Read | Read global custom CSS. Global settings remain read-only. | None |
visual-composer-list-library | Read | List accessible local templates and available optional theme documents. | None |
visual-composer-get-library-item | Read | Read an accessible local template or optional theme document. | post_id |
visual-composer-apply-template | Write | Copy a local custom template and its rendered artifacts into a draft. Hub downloads and linked/global templates are not changed. | post_id, expected_hash, template_id |
visual-composer-list-revisions | Read | Read the latest ten staged document snapshots. | post_id |
visual-composer-restore-revision | Write | Restore a complete paired document snapshot into staging. | post_id, expected_hash, revision_id |
visual-composer-discard-draft | Write | Discard EMCP staging and retain the native published document. | post_id, expected_hash, confirm |
visual-composer-publish-page | Write | Publish the staged element document, HTML and CSS together. Requires confirmation and native publication permission. | post_id, expected_hash, confirm |
Example request
Section titled “Example request”Inspect this Visual Composer draft and prepare a matching native graph, HTML and CSS. Stage the document and verify the native editor before publication.
Read current state before editing and re-read after each save. If a hash is stale, inspect the changed document before rebuilding the request. A successful save is not proof of correct visual output: inspect the native editor and frontend.
Supported scope
Section titled “Supported scope”- Requires EMCP Pro and supported Visual Composer Website Builder. This is separate from WPBakery.
- Native data and rendered HTML/CSS must match; arbitrary server-side element rendering is not provided.
- Global design writes, remote Hub downloads, linked template edits and optional Theme Builder assignments are excluded.
Troubleshooting
Section titled “Troubleshooting”If tools are missing, check versions, dependencies, integration selection, tool switches and user capabilities. Reconnect long-lived MCP clients after plugin updates or selection changes. If output differs after saving, inspect the native document and styles before retrying; do not bypass the adapter with direct metadata writes.
See the Visual Composer integration overview, builder setup guide and agent skills.