Overview
This was a week where MCP became something WordPress products are actually shipping. Two AI plugin versions landed in under two weeks, the MCP Adapter got a significant architectural update, WordPress.com launched an alpha Telegram bot for managing sites from chat, and Pressable put MCP-based hosting controls into public beta. The pace of movement is real.
🏗️ WordPress Core AI Infrastructure
Two AI Plugin Releases in One Week
Sources: What’s new in AI 0.7.0 | What’s new in AI 0.8.0
WordPress shipped both 0.7.0 and 0.8.0 of the canonical AI plugin in under two weeks, and together they move the needle on what “AI in WordPress editing” means as a practical experience.
0.7.0 added content classification (suggested categories/tags based on post content, restricted to existing taxonomy terms), in-editor meta description generation, and bulk alt-text generation from the Media Library with improved W3C alignment – all useful, editor-surface features that reduce manual work in publishing workflows.
0.8.0 pushed further. The new “Refine from Notes” experiment takes editorial feedback and applies it to post content automatically. New dashboard widgets surface available AI abilities and configured connectors directly in wp-admin. Guidelines integration is new: AI abilities can now inherit site-wide editorial standards (tone, style) defined once in Gutenberg, so generated content respects organizational rules without per-request configuration. Image generation and editing also graduated from experiment to stable feature.
Bottom line: These releases are defining what WordPress users will come to expect from AI in their editing workflows – content tagging, meta descriptions, editorial feedback automation, and image generation as standard building blocks.
MCP Adapter v0.5.0
Source: Release v0.5.0
The WordPress MCP Adapter v0.5.0 landed with a meaningful internal refactor. Responses now use typed DTOs via the wordpress/php-mcp-schema package instead of hand-built arrays, improving spec alignment and making integrations more predictable. It also adds protocol version negotiation, stricter input validation, and fail-closed permission handling – when something is ambiguous, the default is to deny rather than allow.
Bottom line: The adapter is hardening its foundations before broader adoption, and fail-closed permissions as the default is the right posture for infrastructure that agents will increasingly rely on.
🏢 What’s Moving in the Ecosystem
Hosting Goes Agentic
Sources: WordPress.com Changelog | Pressable MCP Integration
Two Automattic properties shipped notable MCP features this week, and together they illustrate how far the agentic layer is reaching into WordPress hosting.
WordPress.com launched an alpha Telegram bot that lets you manage your site from chat – publish posts, check stats, fix typos – without opening the dashboard. They also updated their MCP tooling UI with clearer separation of read vs write operations, tools grouped by site area, and per-site enable/disable controls. That’s MCP permission design being productized for non-technical users, and the patterns they’re using are a useful reference for the ecosystem.
Pressable went deeper into infrastructure: a public beta MCP integration lets customers provision sites, clone production to staging, change PHP versions, and run portfolio-wide operations from Claude Desktop, ChatGPT, and Gemini CLI. Infrastructure-level operations via natural language prompt.
Bottom line: Hosting providers are treating “AI is the interface” as a product feature – and the pace of rollout suggests others will follow quickly.
AI-for-Real-Site-Work Tools
Source: WPVibe
WPVibe is a free plugin + hosted MCP service connecting WordPress sites to Claude.ai, ChatGPT, Cursor, and Claude Desktop. Its differentiator is remote connectivity – the official WordPress MCP adapter is still primarily focused on local clients, so WPVibe fills that gap for users who want to control their site from Claude.ai on the web. Setup is designed to be low-friction: install, copy the server URL, authorize in one click.
Bottom line: Many teams are converging on the same user problem – AI that does real site work, not just generates text – with similar safety patterns (preview before publish, rollback, permissions).
💡 Strategic Signals
The Building Blocks Are Actually Being Built On
Source: AI Across The WP Ecosystem (j.cv)
James LePage published a thorough post cataloging real-world ecosystem adoption of WordPress AI infrastructure, and the list is long. ACF and WooCommerce have already registered abilities. MCP servers, provider plugins, and tutorials are spreading across the ecosystem. The Abilities API + MCP Adapter combination is being treated as the standard tool surface for agents – actions are discoverable, scoped, and executable through a consistent interface.
The provider/plugin architecture is also designed to be model-agnostic: developers build against a stable WordPress interface and can swap model providers underneath. That’s a future-proof approach for a fast-moving space.
Bottom line: WordPress is becoming agent-ready through open standards, and the ecosystem is doing what it always does – extending and innovating on the foundation (actually see my WordCamp Asia talk for more on this).
Agency Clients Are Driving the AI Conversation
Source: WP Engine AI Agency Trends Report
WP Engine surveyed 214 agency professionals. Most are investing in AI, but only a small group consider themselves advanced. The most interesting finding: clients are initiating AI conversations, not agencies. The top challenge isn’t lack of interest – it’s keeping up with the pace of change. The report frames the shift as analogous to the mobile-first transition.
Bottom line: AI adoption in the agency market has moved from “should we explore this” to “our clients are asking for it” – which changes the nature of the demand significantly.
📦 Ecosystem Highlights
Community builds 97 Elementor tools as an MCP server: A developer published msrbuilds/elementor-mcp, exposing Elementor as a 97-tool MCP server via Application Passwords with capability-based permissions. Coverage spans page management, layout and widget editing, templates, dynamic tags, and Pro-only surfaces.
WooCommerce going agentic via MCP: A PublishPress podcast covers WooCommerce’s MCP beta (read/write store operations), AI appearing in contribution attribution (Copilot/Claude as co-authors), and early signals of agentic commerce – product discovery and purchases initiated from AI interfaces. Full autonomous purchasing is still early due to tax/shipping/subscription complexity, but MCP-based store operations are already shipping.
Skills in wp-admin still being defined: An active GitHub discussion is working through whether “skills” in wp-admin should be reusable prompts, full agent capabilities, or a separated combination of both. Command Palette is proposed as the natural discovery surface. The decisions made here will shape how AI capabilities are packaged and distributed in WordPress going forward.
WordPress 7.0 moved to May 20: The release date slipped slightly to allow for more stability and performance work. No feature changes – just more time to get it right before shipping.
Summing up
The throughline this week is infrastructure catching up to ambition. MCP went from spec to shipping product across multiple layers of the WordPress stack – content, admin, and now hosting – in a single week. The ecosystem is moving fast, and it’s moving in a coordinated direction.
You made it to the end 👏 Thanks for reading! 🙂
