Spectra MCP tools
Available in EMCP 3.17.0. Spectra has its own integration controls and tools in EMCP 3.17.0. Inspect the installed uagb block catalog and native attribute schemas, then insert or edit Spectra content within a mixed Gutenberg page. Astra is not required.
Requirements and setup
Section titled “Requirements and setup”- Check installed versions. Active Spectra plugin. Included in free EMCP.
- 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”Insertion uses Spectra defaults and generated block IDs. Updates take one complete serialized block, including its native markup and nested content. The surrounding Gutenberg tree is preserved and the current page hash guards against writing over newer content.
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 |
|---|---|---|---|
spectra-get-context | Read | Inspect independent activation state. | None |
spectra-list-blocks | Read | Discover installed block types. | None |
spectra-get-block-schema | Read | Inspect attributes and examples. | name or names |
spectra-get-post-blocks | Read | Read mixed content, markup and hash. | post_id |
spectra-add-block | Write | Insert supported native content. | post_id, expected_hash, block |
spectra-update-block | Write | Replace one complete serialized block. | post_id, expected_hash, path, markup |
spectra-move-block | Write | Move this plugin’s block in the mixed tree. | post_id, expected_hash, path, position |
spectra-remove-block | Write | Remove a block and its children. | post_id, expected_hash, path |
The spectra-read and spectra-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 the Spectra heading and container schemas, then add a feature section to this Gutenberg draft. Preserve the other blocks and check for invalid-content warnings.
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”- Spectra must be active. This integration is included in free EMCP.
- Astra settings stay in Themes. Spectra does not consume the standalone builder selection.
- Static blocks need valid Gutenberg save markup and a native editor check.
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 Spectra integration overview, builder setup guide and agent skills.