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.

GenerateBlocks MCP tools

Available in EMCP 3.17.0. GenerateBlocks V2 pairs a styles object with compiled CSS. EMCP Pro builds both from supported insertion inputs, letting an agent create native containers and text without leaving their styles disconnected from the saved block.

  1. Check installed versions. Active GenerateBlocks V2, verified on 2.4.0. EMCP Pro is required.
  2. Enable the pack. Open EMCP Tools → Page Builders, switch on GenerateBlocks under 2. Gutenberg block plugins and choose Save changes in the save bar. Packs are independent of the standalone builder and of each other. A pack whose requirements are not met shows them and cannot be switched on.
  3. Switch on its tools. Open EMCP Tools → Tools and select the GenerateBlocks tab. Write tools start disabled. On a new EMCP install the read tools start disabled too, as every Pro tool does. Switch on the tools the task needs and choose Save changes.
  4. Connect and inspect. Reconnect your MCP client, then read context and schemas. Start with a draft and inspect the native editor.

GenerateBlocks has its own switch on Page Builders and its own tools tab beside Gutenberg. Read schemas to choose friendly style fields or native raw styles, then use complete serialized markup for updates. GeneratePress configuration remains in Themes and is not required for the block workflow.

Read the catalog, exact attributes and existing mixed Gutenberg content.

Insert blocks or replace one complete serialized block using the current page hash.

Check saved markup, frontend styles and responsive output in the native editor.

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.

ToolAccessPurposeRequired inputs
generateblocks-get-contextReadInspect independent activation state.None
generateblocks-list-blocksReadDiscover installed block types.None
generateblocks-get-block-schemaReadInspect attributes and examples.name or names
generateblocks-get-post-blocksReadRead mixed content, markup and hash.post_id
generateblocks-add-blockWriteInsert supported native content.post_id, expected_hash, block
generateblocks-update-blockWriteReplace one complete serialized block.post_id, expected_hash, path, markup
generateblocks-move-blockWriteMove this plugin’s block in the mixed tree.post_id, expected_hash, path, position
generateblocks-remove-blockWriteRemove a block and its children.post_id, expected_hash, path

The generateblocks-read and generateblocks-write dispatchers remain for compatibility. Prefer individual tools for new workflows. New writes use the hash from get-post-blocks; legacy dispatchers retain their existing contract.

Create a GenerateBlocks V2 feature section using native containers and text. Compile matching CSS from supported inputs and preserve the surrounding Gutenberg content.

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.

  • Requires EMCP Pro and an active compatible GenerateBlocks installation.
  • The verified content model is GenerateBlocks V2, tested on 2.4.0.
  • Update markup must preserve native IDs, styles and compiled CSS. GeneratePress settings are separate.

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 GenerateBlocks integration overview, builder setup guide and agent skills.