Otter Blocks MCP integration
Otter Blocks MCP integration
Connect Otter Blocks to AI with EMCP Pro. Edit native Gutenberg content, insert local patterns, regenerate styles, and discover installed Pro blocks.
Pro integrationOtter 3.2.5 through 3.2.x; Otter Pro optional
Otter Blocks workflow to review
| Step | Review point |
|---|---|
| Discover installed blocks | Read the catalog, exact attributes and existing mixed Gutenberg content. |
| Prepare native content | Insert blocks or replace one complete serialized block using the current page hash. |
| Validate in Gutenberg | Check saved markup, frontend styles and responsive output in the native editor. |
A practical place to start
Discover installed blocks. Then build and review.
- 01
Discover installed blocks
Read the catalog, exact attributes and existing mixed Gutenberg content.
- 02
Prepare native content
Insert blocks or replace one complete serialized block using the current page hash.
- 03
Validate in Gutenberg
Check saved markup, frontend styles and responsive output in the native editor.
Built for Otter Blocks
Otter Blocks content your team can keep editing
Otter discovery reads the block registry installed on your site. Free and Pro blocks share tools for pages, block editing, local patterns, styles and supported feature settings. The adapter is part of EMCP Pro; Otter Pro is only needed for the vendor’s premium features.
Work with the native design model
Static blocks require attributes and saved HTML. EMCP saves them together and can regenerate Otter CSS after changes. Locally registered patterns are discoverable and insertable. Atomic Wind uses a separate browser CSS compiler, so its utilities require native browser validation.
Connect your AI to the right tools
Open EMCP Tools > Page Builders and enable this Gutenberg pack independently. 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. Available in EMCP 3.17.0. Check compatibility before updating the vendor builder; an unsupported version can prevent its tools from appearing.
Read the Otter Blocks tool reference for operations and tested boundaries. The page-builder setup guide explains selection and Gutenberg coexistence.
Get connected
Put Otter Blocks in your AI’s toolkit.
- 1
Check installed versions
Otter 3.2.5 through 3.2.x; Otter Pro optional. EMCP Pro is required.
- 2
Enable the integration
Open EMCP Tools > Page Builders and enable this Gutenberg pack independently.
- 3
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.
Then connect Claude Code, Claude Desktop, or Cursor to use the Otter Blocks tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about Otter Blocks, supported operations, and the workflow on your site.
Can this run beside another builder?
Yes. Gutenberg packs have independent toggles and can run together alongside the selected standalone builder.
Are attributes enough for every edit?
No. Static blocks need native saved markup as well as attributes. Inspect the schema and validate the result in Gutenberg.
Do I need both EMCP Pro and Otter Pro?
EMCP Pro is required for this adapter. Otter Pro is optional and needed only for Otter premium blocks and features.
Your tools. Your WordPress site.