WordPress builds AI plumbing

For years, adding artificial intelligence to a WordPress site usually meant every plugin building its own private pipe to a model company, its own settings screen, and its own permissions logic. WordPress 7.0 changes that by putting shared artificial intelligence infrastructure into the core software itself. (wordpress.com) The first piece is the Abilities Application Programming Interface, which WordPress 6.9 introduced in 2025. It lets a plugin describe an action in a standard way, like “create a post” or “update stock,” so other software can discover that action without custom glue code. (make.wordpress.org) WordPress 7.0 adds a client-side version of that same system in JavaScript, the language browsers run. That means an assistant working inside the editor can trigger on-screen actions like navigating pages or inserting blocks, not just server-side tasks in the background. (make.wordpress.org) The second piece is the Artificial Intelligence Client, which works like a universal power adapter for model providers. A plugin can ask for text generation through one consistent interface, and WordPress routes the request to whatever provider the site owner has configured. (make.wordpress.org) That Artificial Intelligence Client is deliberately provider-agnostic, which means WordPress core does not hardwire one model company into the platform. The merge proposal said it handles transport, caching, credentials, events, and a browser-friendly application programming layer, but does not ship with providers turned on by default. (make.wordpress.org) The third piece is the Model Context Protocol adapter. Model Context Protocol is an open standard that lets an artificial intelligence assistant discover tools and call them, and the WordPress adapter exposes WordPress abilities in that format. (developer.wordpress.org) In plain terms, that means a tool like Claude Desktop, Cursor, Visual Studio Code, or Claude Code can ask a WordPress site what it is allowed to do, then use those actions directly. The adapter post says those tools can discover and call WordPress abilities instead of needing a one-off integration for each plugin. (developer.wordpress.org) Automattic had already been laying track for this on WordPress.com before the 7.0 release. WordPress.com added Model Context Protocol support in October 2025, added OAuth 2.1 support in January 2026, and said in March 2026 that connected agents could create, edit, and manage posts, pages, and media with approval controls. (wordpress.com 1) (wordpress.com 2) (wordpress.com 3) This lands inside a very large installed base. W3Techs said on March 27, 2026 that WordPress ran 42.4 percent of all websites it tracks and 59.7 percent of sites whose content management system it can identify, so even quiet plumbing changes can spread widely. (w3techs.com) The practical shift is that a store plugin, an analytics plugin, and a publishing workflow plugin can now describe their capabilities in one shared language. Once those abilities are registered, they can be reached through WordPress interfaces, browser code, or the Model Context Protocol layer instead of each vendor reinventing the same connector. (wordpress.com) (make.wordpress.org) (developer.wordpress.org) That is why this release looks small if you only search for a chatbot button. WordPress 7.0 is not mainly adding one flashy assistant feature on April 8, 2026; it is turning WordPress into a standard set of sockets, permissions, and tool calls that other artificial intelligence systems can plug into. (wordpress.com)