Blocksy Blocks MCP tools
Available in EMCP 3.17.0. 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.
Requirements and setup
Section titled “Requirements and setup”- Check installed versions. Blocksy theme and Companion, tested on 2.1.57 with Companion Pro. EMCP Pro is required.
- Enable the integration. Open EMCP Tools > Page Builders and enable this Gutenberg pack independently.
- 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.
Native workflow
Section titled “Native workflow”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.
Discover installed blocks
Section titled “Discover installed blocks”Read the catalog, exact attributes and existing mixed Gutenberg content.
Prepare native content
Section titled “Prepare native content”Insert blocks or replace one complete serialized block using the current page hash.
Validate in Gutenberg
Section titled “Validate in Gutenberg”Check saved markup, frontend styles and responsive output in the native editor.
Tool reference
Section titled “Tool reference”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.
| Tool | Access | Purpose | Required inputs |
|---|---|---|---|
blocksy-blocks-get-context | Read | Inspect independent activation state. | None |
blocksy-blocks-list-blocks | Read | Discover installed block types. | None |
blocksy-blocks-get-block-schema | Read | Inspect attributes and examples. | name or names |
blocksy-blocks-get-post-blocks | Read | Read mixed content, markup and hash. | post_id |
blocksy-blocks-add-block | Write | Insert supported native content. | post_id, expected_hash, block |
blocksy-blocks-update-block | Write | Replace one complete serialized block. | post_id, expected_hash, path, markup |
blocksy-blocks-move-block | Write | Move this plugin’s block in the mixed tree. | post_id, expected_hash, path, position |
blocksy-blocks-remove-block | Write | Remove a block and its children. | post_id, expected_hash, path |
The blocksy-blocks-read and blocksy-blocks-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.
Example request
Section titled “Example request”Inspect Blocksy blocks, then add an existing published Companion Pro Content Block to this draft. Preserve native embed markup and check it in Gutenberg.
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.
Supported scope
Section titled “Supported scope”- Requires EMCP Pro, the active Blocksy theme and Companion. Pro Content Block features require Companion Pro.
- Eight individual block tools and two compatibility dispatchers are separate from theme and Companion tools.
- Preserve native saved embed markup and validate in Gutenberg. Advanced Content Block conditions and code mode remain native-editor tasks.
Troubleshooting
Section titled “Troubleshooting”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 Blocksy Blocks integration overview, builder setup guide and agent skills.