Gutenberg AI is mostly about words. Your design lives somewhere else.
Updated October 31, 2026
Gutenberg AI got real this year. WordPress 7.0 shipped on May 20, 2026 with an AI Client in core, and the official AI plugin from WordPress.org now carries one stable feature and 26 experiments.
Nearly all of them help with words: titles, excerpts, alt text, summaries, translations, type-ahead suggestions. That's useful. But on a block theme, how your site looks isn't in any single post. It's in global styles, template parts and synced patterns, and those are what Kitepod lets Claude or ChatGPT change, staged on a preview first.
What WordPress ships, as of October 2026
WordPress 7.0's release post says the AI Client "lets WordPress communicate with generative AI models," with a Connectors screen to manage those connections in one place. It ships with three presets and room to add your own. Core doesn't add editor features by itself. Plugins use the client to do that.
The official plugin is AI by WordPress.org, version 1.5.0 as of October 30. It needs WordPress 7.0.3 and the block editor (the Classic Editor isn't supported). Image generation and editing is the stable feature. The experiments include title, excerpt, slug, alt text and meta description generation, summaries, translation, editorial notes and type-ahead text. You bring your own key: the FAQ says you "need to provide your own API key for the configured AI Connector plugin."
Two experiments reach outside the editor. MCP Access "controls which abilities AI agents can use over the Model Context Protocol," so an outside agent can call the abilities you allow. WebMCP lets an agent browser work inside the block editor, with every change visible on the page as it happens.
For help writing a single post, that plugin is the right tool, and it comes from the WordPress project itself.
Styles, headers and synced patterns
Make the site's links our green #2F6B3A, and make every H2 a little heavier. Let me see the home page first.
Your assistant reads your global styles and palette, then merges the change in, so the theme stays in control and your other colors aren't touched. Design changes are staged by default. You open the preview, say publish, and Kitepod compares screenshots of the home page from before and after.
Add a "Donate" button to the header on every page, styled like the button in our footer.
The header is a template part. Your assistant reads its block markup, adds a buttons block with the footer button's exact classes and saves it as a template customization. That pins the header: future theme updates to the header file won't reach it, and your assistant should say so before saving.
Our "Volunteer this Saturday" box is a synced pattern. Change the time to 9am and the link to /volunteer.
Editing a synced pattern changes every page that uses it, which here is the point. If you only wanted one page changed, your assistant would swap the pattern reference on that page for its inner blocks instead.
Blocks that still open cleanly
The block editor validates static blocks. If the saved HTML doesn't match what a block expects, you get "This block contains unexpected or invalid content" the next time someone opens the page.
So when your assistant writes blocks, it copies class names and wrappers from blocks already on your site, keeps attributes and HTML in step (a heading's level matches its tag, an image's id matches its class) and falls back to an HTML block when it can't be sure.
| WordPress AI plugin | Kitepod | |
|---|---|---|
| Where it works | Inside the block editor, plus outside agents through MCP Access and WebMCP | Any MCP client: Claude, ChatGPT, Cursor and others |
| Model | Your own API key via a connector | Your Claude or ChatGPT plan, no key |
| Global styles, template parts, patterns | Whatever abilities you allow | Staged with a preview link |
| Status | Most features are experiments | For live sites |
| Undo | Post revisions | Every write, 90 days |
| Cost | Free plugin, plus API usage | Free |
Post revisions cover posts and pages. They don't cover global styles, template parts or menus. Kitepod snapshots each of those before writing, and WordPress revisions explains what core keeps and what it doesn't.
Where a warning or an approval comes first
- Reverting a template to the theme's file, or deleting a custom template, goes live instead of staged and needs a person's sign-off under the default policy. It's still captured, so you can undo it.
- Switching a theme style variation replaces your custom colors and settings. Expect a warning first.
- Classic themes have no theme.json, so there are no global styles to edit. Your assistant uses Customizer settings, widgets and custom CSS there.
- If the connected user lacks
unfiltered_html, WordPress strips scripts and iframes from content, and Kitepod reports what was stripped.
Getting connected
Kitepod's plugin needs WordPress 6.4 or later and PHP 7.4, so you don't need 7.0 for it. Upload the zip, hit Connect in wp-admin and choose the account the AI works under. Then give Claude or ChatGPT the address https://kitepod.com/mcp and approve the sign-in. Claude and WordPress and the WordPress MCP overview have the details for each app.
Finer points
Does WordPress have built-in AI now?
WordPress 7.0 added an AI Client and a Connectors screen to core. To get AI features in the editor you need a plugin, such as the official AI plugin, plus your own API key.
Can Kitepod edit the Site Editor's header and footer?
Yes. They're template parts, and your assistant edits their block markup with a staged preview.
Will AI-written blocks show "invalid content" warnings?
Not if the markup matches what each block saves, which is why your assistant copies from blocks already on your site.
Does it work with Kadence Blocks or GenerateBlocks?
Yes. They're blocks in the post content, and Kitepod's built-in skills tell your assistant where each keeps its settings.
The AI plugin is moving fast, so if MCP Access graduates from experiment, a block site could end up with both: WordPress's abilities for the editor and Kitepod for the parts of the site that aren't posts.