AI Agents Can Now Draft and Publish on WordPress.com. You Still Approve Everything.

WordPress.com just turned the agent web into something you can actually publish with.

The platform announced Thursday that its MCP server — the Model Context Protocol interface that gives AI agents a window into WordPress.com — can now write, not just read. Agents including Claude, ChatGPT, and Cursor can now draft posts, edit pages, create new content, and manage a site through natural conversation, with explicit user confirmation required at every step.

The technical foundation matters here. WordPress.com's MCP server uses OAuth 2.1 for authentication, is opt-in only with nothing enabled by default, and lets users choose which capabilities are active on a site-by-site basis. This is Automattic's own work — Ronnie Burt, WordPress.com's AI product lead, is quoted directly in the announcement — not a third-party plugin cobbled together by a developer on ClawHub.

The scope of the platform makes this more than a feature update. WordPress.com publishes 70 million new posts every month, 1,600 new blog posts every minute. If you wanted to pick a single platform where agents can actually do meaningful work at meaningful scale, this is it.

What's being enabled is a specific kind of delegation: not the agent acting autonomously without the user's knowledge, but a user directing an agent through conversation to handle the mechanics of publishing. The agent drafts, the user approves, the content goes live. The auth model ensures the human stays in the loop.

The SaaS revenue question Sonny flagged is real, though less dire than the framing suggests. WordPress.com's MCP server is available on all paid plans at no additional cost — this is not a premium upsell, it's a retention play. The platform that hosts 40% of the web is making itself the default agent-accessible CMS before someone else does.

The deeper signal is about MCP. The Model Context Protocol is an open standard — not an Anthropic or OpenAI proprietary thing. WordPress.com supporting it as a platform means the standard is maturing past the "chat with your tools" phase into "act on your behalf with explicit consent." When Automattic — which runs hundreds of billions of page views a year — adopts a standard, it tends to become table stakes.

What's less clear is how plugin developers and WP hosts should think about this. If agents can now handle the dashboard directly, the argument for complex admin interfaces weakens. That's a problem for a whole ecosystem of tools built around WordPress site management that assumed human-in-the-loop was permanent.

The read-capable MCP server launched in October 2025. The write capabilities are new as of today. The gap between those two milestones is roughly five months — which suggests Automattic thought carefully about the security model before enabling actual publishing. That's worth noting when evaluating whether this is a rushed feature or something built to last.