Skip to content

Your EMCP guide

Answers from our docs

YOUR CHAT, YOUR CHOICE

Before we chat

MSR Builds processes your question and up to four recent messages on our server to answer from the EMCP docs. AI is optional and needs your separate permission.

The chat is kept in this page's memory, not saved as a conversation in our database or browser storage. Our hosting and security services process connection information, such as your IP address, to prevent abuse.

Cloudflare Turnstile checks your browser and connection to prevent automated abuse when you send a question. No login is required.

Please leave out personal, sensitive or confidential information, passwords and API keys.

You can withdraw consent and clear this page's chat at any time. This cannot undo a request already sent or erase provider/security records.

Chat privacy, retention & your rights ↗ · Privacy contact

Starting chat consents to this processing. You can browse our docs without using the chat.

Uncode MCP tools

Available in EMCP 3.22.0. On sites running the Uncode theme, EMCP Pro builds pages and Content Blocks from Uncode’s own elements and Wireframes sections, and reads and changes Uncode’s theme options. Pages go through the WPBakery tools; theme options and Wireframes go through uncode-read and uncode-write.

  1. Check installed versions. Uncode and Uncode Core 2.12.8 or later, or a child of the Uncode theme, with Uncode’s WPBakery Page Builder. Uncode Wireframes is needed for Wireframes sections. EMCP Pro is required.
  2. Select WPBakery. Open EMCP Tools → Page Builders, pick the WPBakery card and choose Save changes. wpbakery-get-context then reports pack: uncode.
  3. Switch on the tools you need. Open EMCP Tools → Tools. uncode-read is on by default; uncode-write and the WPBakery write tools start disabled.
  4. Connect and inspect. Reconnect your MCP client, then call uncode-read with get-context, and wpbakery-get-context, which lists the editable elements.
  1. uncode-read list-wireframes lists sections, filtered by category or search, with whether each is ready to insert on this site.
  2. uncode-read get-wireframe { slug } returns the section’s content with Uncode’s placeholders resolved.
  3. If it answers needs_prepare, the site does not have Uncode’s placeholder images, demo forms or menus yet. uncode-write prepare-wireframes { confirm: true } runs Uncode’s own import once. It needs manage_options and cannot be undone from History, so agents ask first.
  4. Create a draft with wpbakery-create-page, then insert the sections with wpbakery-set-page-content, or one section with wpbakery-replace-fragment. Every write needs the expected_hash from the last read.
  5. Change the text inside each section and keep its attributes. Publish with wpbakery-publish-page.

A Wireframe that lists not_editable elements uses an element the tools cannot write yet and cannot be inserted.

While Uncode is active, the WPBakery tools accept the 39 elements Uncode provides and refuse the ones Uncode removes: vc_btn, vc_video, vc_text_separator and the vc_tta_* tabs. Use vc_button, uncode_index and Uncode’s vc_tabs and vc_accordion instead.

  • Root containers are vc_section (optional) holding vc_row, then vc_column, or vc_row_inner and vc_column_inner for nested columns.
  • Text is the shortcode body of vc_custom_heading, vc_column_text, vc_button and similar elements. Headings take inline uncode_hl_text, uncode_rotating_text and uncode_inline_image.
  • uncode_block { id } embeds a published Content Block, except inside another Content Block.
  • Only attributes that Uncode’s element map or its Wireframes use are accepted; wpbakery-get-element-schema lists them.

Content Blocks are edited like pages: create one with wpbakery-create-page and post_type: uncodeblock.

uncode-read list-option-sections lists the sections. get-options with { section } or { ids: [] } returns values with their label, type and allowed values. Colour options also return the site’s palette as palette (id and name) and choices; use those ids in options and in element attributes.

uncode-write update-options { changes: { id: value }, operation_id: "<new UUID>" } changes options:

  • Values are checked by type, and one refused value refuses the whole call.
  • The theme’s CSS is rebuilt and checked after each write. css_unverified means the change was saved but the stylesheets could not be confirmed; css_failed means EMCP put the settings back because the files could not be written.
  • Use a new UUID for each change and the same UUID only to retry it. A retry never writes twice, and answers conflict if an administrator changed those settings since.
  • Every change can be undone from History.

Not written here: .htaccess and portfolio permalink settings, list-type settings and the header layout picker, whose choices exist only in wp-admin. Change those in Uncode’s Theme Options screen. Per-page Uncode settings (page options) are not written either.

All names use the emcp-tools/ namespace. The page tools are listed in the WPBakery tool reference.

ToolAccessOperations
uncode-readReadget-context, list-option-sections, get-options, get-option-schema, list-wireframes, get-wireframe
uncode-writeWriteupdate-options, prepare-wireframes

Pass operations as { operation, arguments }; call either tool with no operation for the list.