August 2026 Update: AI Templates, MCP Abilities & More

Most builders don’t open WDesignKit’s settings page and read a changelog. They open it because they need a page built by Friday. So instead of a list of what shipped, here’s what actually changes about how you’d use WDesignKit this week, starting with the part most people underuse.

🎨 Why Start From an AI-Compatible Kit Instead of a Blank Page

Every kit in WDesignKit’s template library isn’t just a pre-designed layout, a subset of them are tagged AI Compatible, meaning they’re built to work with WDesignKit’s AI and MCP tooling as that side of the product keeps expanding. That’s a different starting point than picking a theme from scratch.

Here’s what that looks like with four kits from the library this month, each one checked individually on its own page to confirm it actually carries the “AI Compatible” badge:

Zion Template is built for tech and SaaS positioning, the kind of layout you’d reach for if you’re building a landing page for a product launch and need the hero, feature grid, and pricing section to already make sense together. Rome Technology covers similar ground but leans more enterprise, more whitespace, more formal typography, useful when “startup energy” is the wrong tone for the client. Colo Fitness is built around class schedules, trainer bios, and membership CTAs, the actual structure a gym or studio site needs instead of a generic “about us” page reskinned. Taj Bakery handles the local food and bakery use case, menu-forward layout, ordering CTA up top.

Try it yourself: open the AI Template Library, pick one, and import it. The globals (button styles, radius, shadows, animations) now carry over automatically on import, so you’re not manually re-matching your brand styling after the fact, that part shipped this month and is covered below.

🧩 The Widget Builder Works the Same Way, One Component at a Time

Not every job needs a full kit. Sometimes you need one thing, a slider, a menu, a section, that doesn’t exist in the default library yet. That’s what the Widget Builder is for: describe what you need in plain English, and MCP builds it inside your workspace for whichever builder you’re using, Elementor, Gutenberg, or Bricks.

A few from the current library worth pulling into your next build:

🎉 What Actually Shipped in August

Three releases went out this month. Here’s what each one changes in practice, not just what the changelog entry says:

MCP Abilities for WordPress 7.1. If you’re connecting an AI tool to WDesignKit, it can now filter which abilities it discovers by namespace, public exposure, and fields, instead of getting the full list every time. Permissions on rollback, data removal, and dependency install are also tighter, meaning the AI tool can do more without you having to trust it with more than it needs.

Template Abilities, expanded. Saving a full template now carries its globals with it, and you can list templates, repair broken template data, and set cross-builder, demo, and Figma links, all through MCP instead of clicking through the UI for each one.

Globals import flow. This is the one that fixes the annoyance from the section above, button styles, radius, shadows, and animations carry over automatically when you import a template, instead of resetting to defaults.

Widget loading, cached. Widget registration used to scan disk on every request. It’s cached now. You’ll feel this most on sites with a lot of widgets already in use, page loads in the builder itself get noticeably snappier.

New Widget and Snippet Abilities. Sync and pull widget code, set thumbnails, validate widgets, and manage code snippets everywhere they’re used, all newly exposed to MCP.

Full version-by-version detail is in the official changelog if you want the complete list.

🤖 How the MCP Connection Actually Works

If you haven’t connected an AI tool to WDesignKit yet, here’s the mechanism in three steps:

1. You describe what you want to your AI tool of choice (Claude, for example) in plain language, a widget, a template, even a full kit.
2. The AI tool talks to WDesignKit through MCP, using the Abilities exposed this year (and expanded again this month) to actually build the thing inside your workspace, not just describe it back to you.
3. You keep iterating from there. Because the connection is two-way, your AI tool can read what it built, edit it, and re-import changes, rather than a one-shot generation you’re stuck patching manually.

That’s the part that’s different from a typical “AI page builder” pitch, this isn’t a wrapper that generates once and hands you a static export. It’s a live connection to your actual workspace. See the full MCP Workflow →

🛠️ Tool of the Month: Photopea

Not every task is inside WDesignKit. Photopea is a free, browser-based photo and design editor that opens PSD, XD, Sketch, and Figma files directly, no install, no account required. If a client sends you a layered PSD you need to pull assets from, or you need a quick edit and don’t want to open a paid app for it, this covers it.

👀 What’s Next

A few things in motion right now, worth knowing about even though none of it is dated or promised for a specific release:

• The AI Template flow is moving toward something more conversational: describing the site you want in a chat and getting a working, styled page back instead of picking from a static grid.
• That flow is also getting its own sandbox, a space to preview and tweak the AI-generated design before anything touches your live site.
• Live preview will run on the server inside that same sandbox, so what you see while building matches what actually ships.
• Past that, the team’s next stretch of work is aimed at new MCP Abilities, a PHP editor inside the builder itself, and continued MCP-driven AI design improvements.

We’ll cover each of these properly, with real detail, once they actually ship. Keep an eye on wdesignkit.com in the meantime.

🚀 Try It This Week

If you only do one thing from this post, pull an AI-compatible kit into a real project and see how much faster the globals-aware import gets you started compared to a blank canvas. Got a widget you wish existed? That’s exactly what the Widget Builder is for, describe it and see what comes back.