Block suites integration
Spectra AI agent tool reference
Spectra (uagb/* blocks) builds each post's CSS and JS from block attributes once and caches it in post meta, and most of its blocks are registered only in the editor. WP MCP Pro's block suite pair reads Spectra's block schemas from the attribute defaults each block declares, inserts and updates uagb blocks with the same selector settings Spectra's editor gives new blocks, and drops Spectra's cached page assets after every write and rollback so the page rebuilds them. Blocks an agent inserts therefore render with their styles on the front end. list-patterns and import-pattern insert a pattern in one undoable write. The pair also covers Spectra's plugin settings and generated page CSS. get-settings returns an allowlist of Spectra switches and layout numbers, such as file generation, block conditions, animations, local Google fonts, visibility mode, content width and the container gap, each with Spectra's default; update-settings checks every value against the allowed values or number range first, and one bad value refuses the batch. The options it touches are snapshotted as one undo point, and API keys and secrets are never read. get-page-styles returns the CSS Spectra stored for a post, its size, the asset version against the plugin's current one, the Google fonts it loads and its CSS file, and rebuild-page-styles drops that cache, snapshotted, so Spectra builds it again on the next view.
Spectra in plain language: Spectra MCP.
In practice
How Spectra work goes with an agent.
Spectra blocks (uagb/*) do not carry their styling in the saved post content. Spectra generates a stylesheet and script for each post from the block attributes, stores the result in post meta, and reuses it until the post is saved. Many of its blocks are also registered only in the editor, so the server has no schema to read. The Pro block suite pair works around both: it reads each block's declared attribute defaults, assigns the ids and migration flags the editor would, and drops the cached page assets so the next view rebuilds them.
Which Spectra blocks can I use here, and what attributes does the info box take?
Runs block-suites-read with get-block-schemas for the spectra suite, first without a name for the list, then with uagb/info-box for the full attributes. Read only, and the result says unknown attributes are allowed for Spectra.
Add an info box with a heading and a short description under the hero on page 20.
Runs parse-blocks for the content_hash, then block-suites-write insert-block. A block_id is generated, classMigrate is set as Spectra's editor does, the post is snapshotted, and Spectra's cached page assets are deleted.
Change the heading on the call-to-action block at path [2] to "Book a demo".
Runs block-suites-write update-block with inner_html or attrs. Attributes are merged, the block_id cannot change, and the write is one snapshot with the cached CSS and JS dropped afterwards.
Find a free Spectra testimonial block pattern and put it on the About page.
Runs list-patterns with source "spectra", then import-pattern with the chosen spectra:<id> name. Only free, non-premium items are offered. Remote images are sideloaded into the Media Library first, and the post is snapshotted before the write.
What your AI can do
Real Spectra operations, every write reversible.
- Read Spectra block schemas, including editor-only blocks
- Insert and update Spectra blocks that render with their styles
- Give each block the unique id and selectors Spectra's editor would
- Rebuild Spectra's cached page assets after writes and rollbacks
- Browse and import patterns in a single undoable write
- Read and change allowlisted Spectra settings in one validated batch (opt-in)
- Inspect a post's generated CSS and see whether it is stale
- Drop a post's generated CSS so Spectra rebuilds it, snapshotted
- Roll back any block or settings write exactly, per change or per session
Example prompts
Example Spectra prompts.
Add a Spectra info box section under the hero on the homepage.
Why does the Spectra styling on /pricing look old? Check its page CSS and rebuild it.
Turn on Spectra's local Google fonts and set the content width to 1200.
Under the hood
The Spectra calls, under the hood.
block-suites-read({ operation: "list-suites" }), which suites are active
block-suites-write({ operation: "insert-block", args: { suite: "spectra", id: 20, expected_hash, path: [2], markup: "<!-- wp:uagb/info-box ... -->" } }), renders styled, snapshotted
block-suites-read({ operation: "get-page-styles", args: { suite: "spectra", id: 20 } }), stored CSS, version, stale flag, fonts
block-suites-write({ operation: "update-settings", args: { suite: "spectra", settings: { load_gfonts_locally: "enabled", content_width: 1200 } } }), opt-in; allowlist; one undo point
Safety and access
What can be undone on Spectra, and what costs what.
Recoverable on Spectra
- insert-block, update-block and import-pattern each take one snapshot of the whole post.
- rollback-operation restores the post content exactly, and Spectra's cached CSS and JS meta are dropped again so the page rebuilds from the restored blocks.
- Per-session rollback reverts all block writes of an agent run together.
Spectra limits and opt-ins
- Attributes Spectra does not declare are allowed, so a typo in an attribute name is not caught the way it is for Kadence Blocks or GenerateBlocks.
- Images sideloaded for an imported pattern stay in the Media Library after a rollback. Only the post content is restored.
- The Spectra pattern library is contacted only when an agent asks for source "spectra", and only free single-block patterns are offered. Spectra 3 patterns are left out because they use blocks the Spectra release here does not register.
Free or Pro: The dedicated Spectra support is part of WP MCP Pro, as the block-suites-read and block-suites-write pair. It appears only while Spectra or another supported suite is active. The free plugin can still edit uagb blocks as raw markup with the Gutenberg tools, but it does not assign Spectra ids, set the migration flags or clear Spectra's cached assets, so styles may not show.
Part of WP MCP Pro
The Spectra integration is part of WP MCP Pro.
One Pro licence unlocks the Spectra 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
Spectra MCP: questions, answered.
Why did Spectra blocks inserted outside the editor used to render unstyled?
Spectra caches each post's generated CSS and gives new blocks selector settings in its editor. The block suite pair applies the same settings and drops the cache after each write and rollback, so the page regenerates its styles.
Is there a Spectra free path?
Yes. The free Gutenberg block tools edit uagb blocks by raw markup. The dedicated Spectra support is part of WP MCP Pro.
Which Spectra settings can the agent change?
Only the allowlist get-settings returns as writable: Spectra's on and off switches (file generation, templates button, block conditions, masonry gallery, responsive controls, dynamic content, animations, fonts, copy and paste, visibility mode and others) and three layout numbers. Writes are off until the site turns on the wpmcp_enable_block_suite_settings_write filter and need manage_options. API keys and secrets are never read or written.
What does rebuild-page-styles do?
It deletes the CSS and JS Spectra stored for one post, through Spectra's own routine when it is loaded, so Spectra builds fresh assets on the next view. The post is snapshotted first, and it needs permission to edit that post. Large stored CSS is returned up to 200,000 bytes by get-page-styles, with a truncated flag.
Why does Spectra need its cache dropped after a write?
Spectra builds a post's CSS and JS once from the block attributes and keeps the file names in post meta. Until that meta is deleted the old assets keep loading. WP MCP deletes it after every write and rollback, so Spectra rebuilds from the current blocks on the next view.
What is classMigrate and why does WP MCP set it?
When Spectra's editor gives a block a new id it also sets classMigrate, and childMigrate for some blocks. Without classMigrate Spectra keys the CSS on an older id format that the new markup does not contain. WP MCP sets the same flags for the blocks the editor does.
Does it send anything to Spectra's servers?
Only on request. The remote library is read when an agent uses source "spectra" in list-patterns or a spectra:<id> name in import-pattern. The request goes to one checked host with redirects off, a size cap and a day of caching, and it carries no site URL and no license key.
Related integrations
More integrations for the same agent.
MCP for Astra
FreeThemes, 2 tools.
MCP for Astra Pro Custom Layouts
ProThemes, 2 tools.
MCP for Kadence Blocks
ProBlock suites, 5 tools.
MCP for GenerateBlocks
ProBlock suites, 5 tools.
MCP for Gutenberg
FreePage builders, 4 tools.
MCP for Synced Patterns
FreeBlock suites, 2 tools.
Browse the full Integrations hub, or read more on Spectra MCP, Gutenberg MCP and the WordPress MCP plugin.