Get the plugin
WP MCP/Integrations/Themes

Themes integration

Blocksy AI agent tool reference

WP MCP Pro covers Blocksy in three places. The theme pack on the theme pair (get-blocksy-settings, set-blocksy-settings) reads and writes the eight palette colors, font, link and heading colors, the root font family and size, the site and narrow container widths, the header logo height and the footer copyright text. It edits the default header and footer builder section and refuses when the placements were never saved, since the builder's default structure only exists inside the theme. Also on the theme pair, list-blocksy-extensions lists every Blocksy Companion extension with its name, description, whether it is a Pro extension, whether this site can switch it on and whether it is on, and set-blocksy-extensions switches extensions on or off through the companion's own extension manager, the same path its dashboard uses. An unknown id, or a Pro extension the site has no code or plan for, refuses the whole batch before anything is written; the companion's blocksy_active_extensions option is snapshotted first, and a rollback rebuilds Blocksy's dynamic CSS as the forward write does. The block suite pair handles the companion's blocks (blocksy/*): schema-checked inserts and updates with correct unique ids, plus browsing and importing the patterns Blocksy registers. Theme writes stay off until the site turns on the wpmcp_enable_theme_write filter.

theme-readtheme-writeblock-suites-readblock-suites-write

In practice

How Blocksy work goes with an agent.

Blocksy keeps its design in theme mods that the theme reads whole: a colorPalette of eight numbered slots, text, link and heading pickers with default and hover states, and a rootTypography array taken as one value. That last detail drives the write rules, because a font family or size write first seeds the whole array from the theme's default base font, so a half-empty array never reaches the theme. WP MCP also covers the companion plugin's blocks, which build their CSS at render time from a uniqueId, so those writes need no stylesheet rebuild.

Make the link color palette color 3 instead of a fixed hex.

Runs set-blocksy-settings with linkColor set to var(--theme-palette-color-3). Palette references are accepted in that exact shape. The theme mods are snapshotted, then Blocksy's cached copy is wiped and its dynamic CSS refresh fires.

Set the base font to Inter at 17px.

Runs set-blocksy-settings with rootFontFamily and rootFontSize. If rootTypography was never stored, the theme's default base font is written first. The size must be a whole number from 8 to 72.

Set the header logo height to 60 and the site width to 1400.

Runs set-blocksy-settings with header_logo_height (0 to 300) and maxSiteWidth (700 to 1900). The logo height edits the default header section, and the write is refused with setting_unavailable if the header placements were never saved.

Update the heading in the Blocksy block on the landing page.

Runs block-suites-write update-block for the blocksy suite. The block's uniqueId cannot change, the attributes are checked against the schema, and the post is snapshotted once.

What your AI can do

Real Blocksy operations, every write reversible.

  • Read and set the Blocksy palette and text, link and heading colors
  • Change the root font family and size and container widths
  • Set the header logo height and footer copyright text
  • List Blocksy Companion extensions with their on or off state and availability
  • Switch companion extensions on or off in one batch (opt-in, undoable)
  • Insert and update Blocksy companion blocks, schema-checked
  • Browse and import Blocksy patterns as one undoable write

Example prompts

Example Blocksy prompts.

Set Blocksy palette color 1 to our brand blue.

Which Blocksy Companion extensions are on, and which could this site turn on?

Turn off every Blocksy Companion extension we are not using.

Under the hood

The Blocksy calls, under the hood.

wpmcp, blocksy

theme-write({ operation: "set-blocksy-settings", args: { settings: { color1: "#1d4ed8" } } }), opt-in; snapshotted

theme-read({ operation: "list-blocksy-extensions" }), id, name, pro, available, active

theme-write({ operation: "set-blocksy-extensions", args: { extensions: { "<id from list>": true } } }), opt-in; option snapshotted; dynamic CSS rebuilt

block-suites-read({ operation: "list-patterns", args: { suite: "blocksy" } })

Safety and access

What can be undone on Blocksy, and what costs what.

Recoverable on Blocksy

  • Every set-blocksy-settings call snapshots the theme mods before writing, and rollback-operation restores them exactly.
  • After an undo, Blocksy's cached theme mods are wiped and its dynamic CSS refresh fires, so the site shows the restored look right away.
  • Companion block writes snapshot the whole post, and rollback restores it.

Blocksy limits and opt-ins

  • Theme settings writes are off until the site turns on the wpmcp_enable_theme_write filter.
  • Only the listed keys are writable. Anything else is refused by name with key_not_allowlisted.
  • Header and footer edits touch only the default section of the builder, and refuse when the placements were never saved.
  • One invalid value refuses the whole batch before anything is written.

Free or Pro: Both Blocksy pieces are Pro. The theme pack, get-blocksy-settings and set-blocksy-settings, sits on the theme-read and theme-write pair and appears only while Blocksy is the active theme and a Pro licence is active. The companion-block support is the block-suites pair, which registers while Blocksy Companion is active. The set operation is a write that stays off until the site opts in with wpmcp_enable_theme_write, and that opt-in is separate from the Pro gate.

Part of WP MCP Pro

The Blocksy integration is part of WP MCP Pro.

One Pro licence unlocks the Blocksy tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.

Frequently asked

Blocksy MCP: questions, answered.

Why can the header or footer write refuse?

Blocksy keeps header and footer layouts as builder placements. Until they are saved once in the customizer, the default structure exists only inside the theme, so there is nothing safe to edit. Save the header or footer once and the write works.

Can the agent switch on a Pro Blocksy extension?

Only when the site has it. list-blocksy-extensions marks each extension available or not: a Pro extension is available only when the companion has its code and the site is not on the free Blocksy plan. Asking for one that is not available refuses the whole batch with extension_unavailable before anything changes.

Is an extension toggle reversible?

Yes. set-blocksy-extensions snapshots the companion's blocksy_active_extensions option before it writes and only touches extensions whose state really changes. rollback-operation puts the previous set back and rebuilds Blocksy's dynamic CSS.

What does it need to be turned on?

Blocksy as the active theme, Blocksy Companion for the extension and block tools, and WP MCP Pro. Writes are off until the site turns on the wpmcp_enable_theme_write filter, and the extension ops need manage_options.

Can I use a palette reference instead of a hex color?

For fontColor, linkColor, linkHoverColor and headingColor, yes: var(--theme-palette-color-N) with a one or two digit N, or hex, rgb or rgba. The eight palette slots themselves, color1 to color8, take hex, rgb or rgba only, so a slot cannot point at another slot.

Is the footer copyright text sanitised?

Yes. footer_copyright_text accepts up to 5000 characters and is passed through WordPress's post content sanitiser, so ordinary markup such as links survives while scripts do not. It edits the copyright item in the default footer section, and refuses if the footer placements were never saved.

Do Blocksy block writes need a stylesheet rebuild like Otter?

No. The Blocksy companion blocks build their CSS while they render, keyed by uniqueId, so there is no stored per-post stylesheet to go stale. WP MCP still generates a correct uniqueId, checks attributes and snapshots the post, and fires a refresh action sites can hook.

Why was my font name refused?

rootFontFamily accepts letters, digits, spaces, commas, quotes and hyphens, up to 200 characters. Anything with other characters, such as semicolons or braces, is refused with invalid_setting_value before any write. That keeps a font value from carrying CSS into the theme.

Is there an AI agent for Blocksy?

Yes, through WP MCP rather than Blocksy itself. An agent you choose, such as Claude or Cursor, can read and set the Blocksy palette and text, link and heading colors. WP MCP is a separate plugin, not a built-in AI feature of Blocksy. On the undo side: Every set-blocksy-settings call snapshots the theme mods before writing, and rollback-operation restores them exactly.

Point your AI at Blocksy.