Blocksy Blocks MCP integration
Blocksy Blocks MCP integration
Edit Blocksy blocks with AI through EMCP Pro. Discover native schemas, update Gutenberg layouts, and embed existing Companion Pro Content Blocks.
Pro integrationBlocksy theme and Companion, tested on 2.1.57 with Companion Pro
Blocksy Blocks workflow to review
| Step | Review point |
|---|---|
| Discover installed blocks | Read the catalog, exact attributes and existing mixed Gutenberg content. |
| Prepare native content | Insert blocks or replace one complete serialized block using the current page hash. |
| Validate in Gutenberg | Check saved markup, frontend styles and responsive output in the native editor. |
A practical place to start
Discover installed blocks. Then build and review.
- 01
Discover installed blocks
Read the catalog, exact attributes and existing mixed Gutenberg content.
- 02
Prepare native content
Insert blocks or replace one complete serialized block using the current page hash.
- 03
Validate in Gutenberg
Check saved markup, frontend styles and responsive output in the native editor.
Built for Blocksy Blocks
Blocksy Blocks content your team can keep editing
Blocksy Blocks now sits outside the Themes tools. Its dedicated integration discovers block types and schemas, reads mixed Gutenberg pages and provides focused add, update, move and remove operations for Blocksy content.
Work with the native design model
An existing Companion Pro Content Block can be embedded through its native block. Creating and publishing that reusable document belongs to separate Companion tools. Theme widths and design discovery stay in Themes, keeping a block edit distinct from site-wide layout changes.
Connect your AI to the right tools
Open EMCP Tools > Page Builders and enable this Gutenberg pack independently. 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 Blocksy Blocks tool reference for operations and tested boundaries. The page-builder setup guide explains selection and Gutenberg coexistence.
Get connected
Put Blocksy Blocks in your AI’s toolkit.
- 1
Check installed versions
Blocksy theme and Companion, tested on 2.1.57 with Companion Pro. 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.
Then connect Claude Code, Claude Desktop, or Cursor to use the Blocksy Blocks tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about Blocksy Blocks, supported operations, and the workflow on your site.
Can this run beside another builder?
Yes. Gutenberg packs have independent toggles and can run together alongside the selected standalone builder.
Are attributes enough for every edit?
No. Static blocks need native saved markup as well as attributes. Inspect the schema and validate the result in Gutenberg.
Does Blocksy Blocks still need the Blocksy theme?
Yes. Independent EMCP controls separate tool ownership; they do not remove the native Blocksy theme and Companion requirements.
Your tools. Your WordPress site.