Skip to content

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 integration. Open EMCP Tools > Page Builders and enable this Gutenberg pack independently.
  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.

GenerateBlocks has its own toggle and tools 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.