Overview
We skipped last week for Pesach, so this is a double issue – and there was plenty to catch up on. The dominant story is Cloudflare’s EmDash, which triggered a full week of ecosystem debate about WordPress’s architecture. Meanwhile, the WordPress AI infrastructure layer keeps advancing ahead of 7.0, and the Abilities API is reaching a tipping point with ACF now on board. A lot happened – let’s get into it.
🏗️ WordPress Core AI Infrastructure
WordPress 7.0 Is Delayed – but the AI Story Is Moving Forward
Sources: Extending the 7.0 Cycle | Pre-releases paused through April 17 | AI Contributor Weekly – April 8
WordPress 7.0 is delayed again. Pre-releases are paused through April 17, with a revised schedule expected by April 22. The issue is real-time collaboration (RTC) – specifically a cache invalidation problem where editor activity triggers broad cache flushes that hurt site performance. A dedicated wp_collaboration table is under active discussion as a potential fix, needing testing in the Gutenberg plugin before committing to core.
The broader AI infrastructure picture is looking good though. The AI Client (WordPress’s provider-agnostic API layer for making AI calls) is being treated as genuine core infrastructure for 7.0. The official AI plugin is pushing toward 1.0 alongside the release. The MCP Adapter is close to 0.5.0, with community debate on packaging – whether it ships as a simple plugin/zip or a composer dependency will significantly affect who can actually use it. There’s also an AI Handbook in the works covering non-technical guidance, opt-out patterns, and data-handling clarity.
Bottom line: The AI infrastructure pieces – AI Client, Connectors, MCP Adapter – are converging into a real foundational layer that developers and plugin authors will build on. The release delay is a setback for RTC specifically, but doesn’t change that trajectory.
🏢 Competitive Landscape
The EmDash Moment: One Week of Ecosystem Self-Examination
Sources: Cloudflare blog | GitHub repo | Matt Mullenweg’s response | Joost de Valk | The Repository roundup | Brian Coords | KrautPress | Search Engine Journal
Cloudflare launched EmDash – a TypeScript CMS built on Astro and Cloudflare Workers – and positioned it as the “spiritual successor to WordPress.” The reaction was loud, and many people wrote about it (including me).
What EmDash actually is: A modern, serverless-first CMS with sandboxed plugin execution (plugins run in isolated Workers with explicit capability declarations), a structured content model (Portable Text JSON rather than serialized HTML), a built-in MCP server, and a developer-first workflow optimized for AI-assisted building. Interesting architecturally, and fast to start with. Also: very Cloudflare-dependent.
What it isn’t: A WordPress replacement any time soon. It’s in developer beta, requires GitHub/CLI workflows, and has essentially no ecosystem – no plugin library, no community, no broad hosting support, limited governance outside Cloudflare.
The more useful part of the conversation was what it revealed about WordPress. Matt Mullenweg pushed back on the “spiritual successor” framing, arguing that EmDash’s security advantages are architecturally tied to Cloudflare’s infrastructure – open source code is not the same thing as “runs anywhere.” Joost de Valk took the more productive angle: the problems EmDash highlights are real, but WordPress needs to refactor rather than be replaced – typed content tables, structured block storage, scoped plugin permissions.
The Gutenberg storage critique is worth understanding. Right now, block structure is serialized as HTML in post_content at save time, meaning any downstream system that needs structured data has to re-parse it via parse_blocks(). It works, but it’s a workaround – and as AI becomes a common way to read and transform content, that matters more.
Bottom line: I don’t think EmDash is a real alternative to WordPress, but it does force us all to take a good look at some of WordPress’s weak spots.
WordPress.com Launches an Agent Bot on Telegram
Source: WordPress.com on X
WordPress.com launched @wordpressagentbot, a Telegram bot in alpha for managing WordPress.com sites through a messaging app. It handles creating and editing posts and pages, generating and uploading images, checking site stats, domain availability, and switching between sites – no dashboard needed. It respects WordPress role permissions and has metered daily message limits by plan.
Bottom line: Agent-based site management is moving from developer tools into mainstream consumer surfaces in WordPress too.
💡 Strategic Insights
ACF Ships Abilities API Support
Source: ACF Abilities API documentation
ACF 6.8 added Abilities API integration, exposing its field groups, custom post types, and taxonomies as machine-readable “abilities” – standardized, MCP-compatible interfaces that AI tools can discover and call, with JSON Schema describing inputs and outputs. Access is opt-in per item, governed by WordPress user permissions, and destructive actions require explicit confirmation.
ACF is the de facto standard for structured content on WordPress. By adopting the Abilities API, a large chunk of the WordPress content architecture is now accessible to AI agents in a standardized, safe way. When ACF sets a pattern, the ecosystem tends to follow.
Bottom line: This is probably one of the strongest signals yet that the Abilities API is becoming the expected integration pattern for AI tool access across WordPress.
Self-Hosted AI Is Becoming a Real Conversation
Sources: WP Private AI (GitHub) | Varun Dubey’s write-up
Two pieces this week documented an open-source proof of concept for running a WordPress AI assistant fully on your own infrastructure using Ollama – prompts and site data never leave the server. It uses the WordPress Abilities API with server-side permission callbacks, injects verified site facts to reduce hallucinations, and proposes multi-site deployment patterns for agencies and hosts.
The interesting signal is the framing. “Privacy by architecture, not policy” is emerging as a distinct positioning in the WordPress AI space – and it’s likely to resonate more as AI becomes a standard part of site operations, especially in EU/GDPR-sensitive markets.
Bottom line: The question of where your data goes when you use AI tools on your site is becoming a mainstream concern, not just an enterprise one.
📦 Ecosystem Innovation Highlights
Pressable MCP is live: Automattic’s managed WordPress hosting now offers an MCP control plane letting AI assistants manage Pressable-hosted sites – provisioning, PHP/WP version changes, domain management, plugins, users, logs. Supported clients include Claude Desktop, Claude Code, ChatGPT, and Gemini CLI. Hosting-level AI control is becoming a real product category. Read more →
Claudaborative Editing 0.2: Gary Pendergast’s demo MCP server for Claude Code + Gutenberg now covers all block types including plugin blocks, handles media uploads, edits post metadata, and has a smoother connect flow on WordPress 7.0. The “review then apply” loop – AI leaves Gutenberg Notes, you approve before changes are applied – is a practical model for keeping humans in control. Read more →
WP-Agentic-Admin: An open-source plugin concept bringing an agentic admin experience into wp-admin for site reliability tasks – log reading, site health, plugin management. The standout detail: LLM inference runs locally in the browser via WebGPU, so no site data leaves to external services. Uses the Abilities API with explicit confirmation for destructive actions. Read more →
WP-MCP: A Node.js MCP server connecting AI assistants to WordPress via the REST API, with no WordPress-side plugin required. Uses Application Passwords for auth and auto-discovers plugin REST namespaces – so WooCommerce, ACF, and other plugin endpoints become available as MCP tools automatically. Read more →
Grumpy AI Gate: A new plugin adding visibility and optional control over outbound AI API requests site-wide – logs which plugin initiated which AI calls, tracks usage and spend, and can block AI Client generations per plugin. All logs stay local. Read more →
It was a busy two weeks. The EmDash conversation was noisy, but underneath it there’s something useful: the WordPress ecosystem is being pushed to articulate what makes it worth choosing in an AI-first world, and the answers – portability, ecosystem depth, active improvement – are pretty good ones. The Abilities API reaching critical mass, hosting providers shipping MCP layers, and Core treating AI infrastructure as a first-class concern all point in the same direction of WordPress being a leading platform for enabling AI creativity.
You made it to the end 👏 Thanks for reading! 🙂
