A brief becomes a real page.Blocksy Blocks MCP integration
Blocksy Blocks MCP: bring reusable content into your page.
Connect your AI to Blocksy’s Gutenberg blocks with EMCP Pro to inspect schemas and embed existing Companion Pro Content Blocks. Enable the block pack separately from the theme and Companion tools. Native dependencies still apply: Blocksy and Companion are required, with Companion Pro for reusable Content Block features.
Pro integrationBlocksy theme and Companion, tested on 2.1.57 with Companion Pro
An existing Content Block embedded in a draft
| Step | Review point |
|---|---|
| Find the native embed schema | Read installed Blocksy block types and identify the existing published Content Block to use. |
| Insert its saved placeholder | Preserve the native embed markup and use the current hash of the destination page. |
| Check both editor and frontend | Validate the block in Gutenberg, then inspect the dynamically rendered content on the page. |
A practical place to start
Embed an existing Companion Content Block in a Gutenberg draft.
- 01
Find the native embed schema
Read installed Blocksy block types and identify the existing published Content Block to use.
- 02
Insert its saved placeholder
Preserve the native embed markup and use the current hash of the destination page.
- 03
Check both editor and frontend
Validate the block in Gutenberg, then inspect the dynamically rendered content on the page.
Built for Blocksy Blocks
Separate the page embed from its source document
Blocksy Blocks discovers the installed block types and schemas and reads mixed Gutenberg pages. Its focused add, update, move and remove tools operate on Blocksy content within that page tree. This keeps a page edit distinct from theme configuration or Companion extension activation.
A reusable Companion Pro Content Block is a source document. Embedding it in a page is a separate job from creating or publishing that document. Use the Blocksy Theme & Companion integration for source-document authoring.
Embed an existing published Content Block
Inspect the native embed schema and the source document you intend to use. Read the destination page, choose the insertion position from its current tree, and use the returned content hash for the write.
The saved block contains placeholder markup even though PHP renders its content dynamically. Preserve that native markup when adding or updating the embed. Replacing it with copied frontend HTML would lose the intended reusable relationship.
Keep the native dependencies in place
Independent tool activation does not make this adapter independent of Blocksy’s products. It requires EMCP Pro, the active Blocksy theme and Companion. Pro Content Block features additionally require Companion Pro. The recorded fixture used Blocksy and Companion Pro 2.1.57.
Enable the pack under EMCP Tools → Page Builders and inspect its own tool switches. Theme widths, extension toggles and reusable-document edits remain in their corresponding theme or Companion tools.
Review both sides of the embed
Open the destination page in Gutenberg and look for validation warnings. Then inspect the frontend where the reusable content is rendered. A valid page block does not establish that the source Content Block has appropriate publication, activation or display settings.
Advanced Content Block conditions and code-mode authoring remain native-editor tasks. The Blocksy Blocks reference lists required inputs, and the Blocksy reference explains source-document scope.
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.
Does independent activation remove the Blocksy dependency?
No. Separate EMCP controls distinguish block tools from theme and Companion tools. The block adapter still requires the active Blocksy theme and Companion, with Companion Pro for Content Block features.
Can these tools create the reusable Content Block itself?
Source-document creation and publication belong to the separate Companion Content Block tools. Use the block adapter to embed an existing document in Gutenberg content.
Why preserve placeholder markup for dynamic content?
PHP renders the reusable content on the frontend, but Gutenberg still expects native saved embed markup. Preserve that contract and inspect the editor for validation warnings.
Your tools. Your WordPress site.