Cowboy MCP 1.6.2: Gutenberg block editing, plus scoped keys for least-privilege agents

Cowboy MCP 1.6.2 teaches your agent the block editor: it can read any post or page as a block tree and make surgical edits — change a heading, move a section, swap a pattern — instead of resending the whole document. It also adds per-credential tool scoping, so each API key or connection gets exactly the access you intend and nothing more. The toolset grows from 153 to 168, and every new write is journaled and undoable like the rest of the plugin.

What this means for you

Until now, asking an agent to tweak one section of a Gutenberg page meant it had to rewrite the page's entire content — slow, token-hungry, and easy to get subtly wrong. This release gives it an editor's hands: it sees the page the way the block editor does and touches only the blocks you asked about. And with scoped keys, you can finally hand a content agent a key that can write posts but can never touch files, users, or the database.

What's new

• Gutenberg block editing. Read any post or page as a block tree, then apply batched surgical edits — update, insert, delete, move, replace — addressed by block path. Conflicting edits in one batch are rejected up front, so a bad request changes nothing.
• Patterns, templates, and global styles. List, create, update, and delete block patterns (synced or unsynced). On block themes, the agent can also edit site editor templates and template parts — editing a theme template creates an override you can undo back to the theme's original — and update global styles like colors, typography, and spacing.
• Per-credential tool scoping. Give each API key or OAuth connection full access, read-only access, or a hand-picked list of tools. Existing credentials keep full access until you change them, and a credential can never widen its own scope — the scope settings are write-protected from the API, even in Power mode.
• A hardened WP-CLI safety gate. The command blocklist now tokenizes commands the way the shell parses them, closing quoting and flag-injection bypasses, and SQL passed through WP-CLI is scanned with MySQL versioned comments unwrapped. Commands that cannot be safely parsed are rejected outright.

Try it

Move the testimonials section above the pricing table on the homepage, and make the hero heading say "Ship faster".

Read the full 1.6.2 changelog on WordPress.org.