A brief becomes a real page.Blocksy Theme & Companion MCP integration
Blocksy MCP: manage theme widths and Companion content.
EMCP Pro connects your AI to three distinct Blocksy workflows: supported theme widths, Companion extension activation, and disabled Content Block drafts. Inspect each surface before making changes. Blocksy Blocks has a separate integration for Gutenberg content, and advanced conditions and complex header/footer layouts remain native-editor tasks.
Pro integrationActive Blocksy Theme & Companion and EMCP Pro
A disabled Companion Content Block draft
| Step | Check |
|---|---|
| Inspect Companion’s document types | Read available Content Block types and existing documents with the native products and permissions in place. |
| Create a disabled draft | Prepare the document with no display conditions. Use the current hash for edits and review its native content. |
| Review publication and activation | Publish only after review, then inspect the native display controls. Publication does not silently enable a disabled block. |
A practical place to start
Prepare a Companion Content Block before making it visible.
- 01
Inspect Companion’s document types
Read available Content Block types and existing documents with the native products and permissions in place.
- 02
Create a disabled draft
Prepare the document with no display conditions. Use the current hash for edits and review its native content.
- 03
Review publication and activation
Publish only after review, then inspect the native display controls. Publication does not silently enable a disabled block.
Built for Blocksy Theme & Companion
Three Blocksy surfaces with different effects
Blocksy theme design, Companion extensions and reusable Content Blocks have separate EMCP Pro tools. Theme settings live in Themes; Companion operations live in Plugins. Blocksy Blocks handles native Gutenberg content through its own integration.
For a theme task, inspect the current schema and settings hash. The verified write keys are maxSiteWidth, narrowContainerWidth and wideOffset. Palette, typography, responsive spacing and complex header/footer placement can be read, but that discovery does not authorize changing every field.
Manage Companion extension activation
The extensions dispatcher lists installed extensions with descriptions, activation state and Pro flags. You can activate or deactivate a supported extension by slug, subject to native permissions. This does not supply a Companion Pro license or expose arbitrary extension configuration.
Keep a width adjustment separate from an extension toggle so the review identifies the effect of each requested change. Theme writes clear native settings caches and refresh CSS; inspect more than one page after a site-wide change.
Author disabled Content Block drafts
Companion Pro Content Block tools discover native types, read documents and create disabled drafts with no conditions. Draft updates require the current hash and preserve unknown native settings. Published documents must be unpublished before draft-only edits.
Publishing is explicit and does not silently enable a disabled block. Use native controls for advanced conditions, popups and code-mode authoring. Ordinary Gutenberg saves retain their immediate-save behavior; the draft isolation of the template tools does not apply to every page edit.
Embed existing content through Gutenberg
Once an appropriate Content Block exists, use the separate Blocksy Blocks tools to embed it in a page. Preserve the saved placeholder markup even though PHP renders the content dynamically. Open Gutenberg to check for validation warnings and inspect the frontend placement.
Requires EMCP Pro and the relevant Blocksy products; Content Blocks require Companion Pro. The recorded fixture used Blocksy and Companion Pro 2.1.57. Read the Blocksy tool reference for permissions, access switches and tested scope.
Get connected
Put Blocksy Theme & Companion in your AI’s toolkit.
- 1
Activate the native dependency
Activate Blocksy and Companion; Content Blocks require Companion Pro. Use EMCP Pro.
- 2
Inspect tool access
Use Themes for theme settings and Plugins for Companion extensions and Content Blocks. Enable only the required writes.
- 3
Keep block editing separate
Enable blocksy-blocks independently in Page Builders when you need its Gutenberg tools.
Then connect Claude Code, Claude Desktop, or Cursor to use the Blocksy Theme & Companion tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about Blocksy Theme & Companion, supported operations, and the workflow on your site.
Which Blocksy theme fields are writable?
The verified theme write scope covers maxSiteWidth, narrowContainerWidth and wideOffset. Palette, typography and complex header/footer placement can be inspected; discovery does not imply write access.
Does publishing a Content Block enable it?
No. Creation produces a disabled draft without conditions, and publication does not silently enable it. Review activation and display conditions in the native controls.
Do the extension tools configure every Companion feature?
No. They list extensions and activate or deactivate them by slug. Premium extensions require the vendor license, and arbitrary extension configuration is outside that dispatcher.
Your tools. Your WordPress site.