A brief becomes a real page.Blocksy Theme & Companion MCP integration
Blocksy Theme & Companion MCP integration
Manage Blocksy theme layout settings and Companion extensions with EMCP Pro. Create scoped Content Block drafts while keeping Gutenberg block editing separate.
Pro integrationActive Blocksy Theme & Companion and EMCP Pro
scoped theme update
| Step | Check |
|---|---|
| Inspect native settings | Read current values and the supported field definitions before changing site-wide design. |
| Choose theme or Companion tools | Keep width changes separate from extension toggles and disabled Content Block drafts. |
| Verify the rendered theme | Read the saved values and inspect the frontend, including small-screen layout. |
A practical place to start
Inspect settings before changing the theme.
- 01
Inspect native settings
Read current values and the supported field definitions before changing site-wide design.
- 02
Choose theme or Companion tools
Keep width changes separate from extension toggles and disabled Content Block drafts.
- 03
Verify the rendered theme
Read the saved values and inspect the frontend, including small-screen layout.
Built for Blocksy Theme & Companion
Theme settings with a defined scope
Blocksy has three distinct EMCP surfaces: theme design in Themes, Companion extensions and Pro Content Blocks in Plugins, and an independently enabled Blocksy Blocks pack. The theme adapter writes three verified layout values and reads palette, typography, spacing and header/footer configuration.
Keep block content independent
The blocksy-blocks integration has its own tools and toggle. Selecting another standalone builder does not turn theme configuration into builder content, and changing a block does not require rewriting theme options.
Review site-wide changes
Theme writes cover maxSiteWidth, narrowContainerWidth and wideOffset. Complex header/footer graphs are read-only. Pro Content Blocks require Companion Pro. Advanced conditions, popups and code-mode authoring remain native-editor tasks. Read back changed values and inspect the frontend. A theme change can affect many pages even when the request changes one setting.
Companion Pro Content Blocks
Create a disabled draft with no display conditions, edit its native document, then publish explicitly. Publication does not silently enable a disabled Content Block. Unpublish before draft-only edits; ordinary Gutenberg saves retain their immediate-save behavior. Advanced conditions and code-mode documents remain native-editor tasks.
Read the Blocksy Theme & Companion tool reference for operations, permissions and limitations.
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.
Does this include block editing?
Block editing has its own independent integration. Use the linked block-pack tools for page content and these tools for theme configuration.
Can it update every Customizer field?
No. Writes use a curated native setting allowlist. Inspect the live schema and supported scope before proposing changes.
What access is required?
Theme writes cover maxSiteWidth, narrowContainerWidth and wideOffset. Complex header/footer graphs are read-only. Pro Content Blocks require Companion Pro. Advanced conditions, popups and code-mode authoring remain native-editor tasks.
Your tools. Your WordPress site.