Import block patterns from the WordPress.org Pattern Directory

The WordPress.org Pattern Directory has thousands of ready-made sections. WP MCP Pro lets an agent search it and drop one into a page in a single undoable write.

What you need

• WP MCP Pro, connected to your AI client.
• A supported block suite active (Kadence Blocks, GenerateBlocks, Spectra, Otter Blocks or the Blocksy companion). The pattern tools live on the block suite pair, which only appears while one of those is active.

Privacy first

Nothing is sent to WordPress.org unless you ask for this source. A request carries your search terms, category, paging and locale under a WP MCP user agent, so your site address is not sent, and answers are cached on your site for an hour, so a repeat browse or import sends nothing.

Step 1: Search

› Find a testimonials pattern in the WordPress.org directory.

The agent calls block-suites-read with list-patterns and source: "directory", plus a search or category. Directory patterns use core blocks only, so the suite filter does not apply to this source. Their names look like directory:<id>.

Step 2: Import

› Put that pattern under the hero on /about.

The agent reads the page with parse-blocks for its expected_hash, then calls block-suites-write with import-pattern, the directory:<id> name, the post id and a path. Images from WordPress.org’s pattern image hosts, or your allowlisted media hosts, are sideloaded into the Media Library first; images anywhere else stay at their URLs and are reported. Pass sideload_images: false to keep every image remote.

Step 3: Undo if it is not right

The import is one post snapshot, so rollback-operation restores the page exactly. Images it sideloaded stay in the Media Library.

Registered patterns (core, your theme, and the ones suites such as Otter and Blocksy add) work the same way with list-patterns on the default source; see Build with block suites.