WordPress 7.0 adds AI plumbing
WordPress 7.0 introduces shared AI infrastructure—an Abilities API, AI Client and adapter—so plugins can interoperate with AI models without bespoke integration code. (wordpress.com) That plumbing should make it easier for agencies to embed purpose-built AI features into client sites and will raise expectations for seamless plugin-to-plugin dataflow. (wordpress.com)
Most website builders bolt artificial intelligence onto one feature at a time, so one plugin writes captions, another summarizes posts, and neither knows how to talk to the other. WordPress 7.0 is trying a different move on April 9, 2026: put the shared pipes into core first, then let plugins build on top of them. (wordpress.com, make.wordpress.org) In WordPress, a plugin is an add-on, and today many artificial intelligence plugins each ship their own model software kit, settings screen, and credentials flow. The new built-in Artificial Intelligence Client gives those plugins one common way to send a prompt and get back text or images. (make.wordpress.org, make.wordpress.org) WordPress calls that client “provider-agnostic,” which means a plugin can ask for a job without hard-wiring itself to one company’s model. The site owner configures a provider, and WordPress routes the request to a suitable model through the same interface. (make.wordpress.org) The other piece is the Abilities Application Programming Interface, which works like a menu of actions a tool is allowed to perform inside a site. WordPress 6.9 added the server-side version, and WordPress 7.0 adds a JavaScript version for browser-side actions like navigating the dashboard or inserting blocks into the editor. (make.wordpress.org) That sounds abstract until you picture an editor asking a plugin to draft a product description and then place it into a page. One system can generate the text through the Artificial Intelligence Client, and another can use the Abilities Application Programming Interface to insert that text into the right spot without custom glue code between the two. (wordpress.com, make.wordpress.org, make.wordpress.org) WordPress is also adding a Model Context Protocol adapter, and Model Context Protocol is an open standard for letting external artificial intelligence tools discover and call software actions. In plain English, that gives outside agents a standard doorway into WordPress instead of forcing every plugin author to invent a separate one. (wordpress.com) The company is being careful about what ships by default. The core merge proposal says WordPress 7.0 includes no bundled providers, no bundled credentials, and no automatic outbound artificial intelligence calls unless a site owner explicitly configures a provider and a plugin explicitly invokes it. (make.wordpress.org) That restraint is the point of the release. Core is standardizing transport, authentication storage, capability checks, REST application programming interface endpoints, and JavaScript hooks, while leaving the actual products and user-facing assistants to plugins. (make.wordpress.org) For agencies that build client sites, this changes the economics of adding small purpose-built features. A team can wire one plugin to summarize support tickets, another to draft schema markup, and a third to move results into the editor, without maintaining three separate model integrations. (wordpress.com, make.wordpress.org) The pressure now shifts to plugin developers. Once WordPress itself supplies the common pipes, site owners will expect plugins to share credentials, detect available models, and pass data between each other as smoothly as payment plugins already share checkout details. (wordpress.com, make.wordpress.org)
