WordPress contributors have set WordPress 7.3 as the target for letting site owners connect AI agents to their sites without extra plugins or hand-copied passwords. The plan is set out in "WordPress for the Agentic Web", a proposal by Jason Adams published on the Make WordPress AI blog on 28 October 2026.

The proposal uses the WordPress 7.2 cycle to lay foundations and targets 7.3 for the main work. It is explicit that this is not guaranteed:

“While WordPress 7.3 is our shared target, inclusion in core will depend on technical readiness, security, and the normal core review processes.”

Jason Adams, WordPress AI team, 28 October 2026

Background

The Model Context Protocol (MCP) is a standard way for AI agents to discover and use tools in other systems. On 7 October the AI team released the MCP Adapter as a canonical plugin in the WordPress.org directory. The plugin exposes a site's registered Abilities, units of WordPress functionality, to AI agents. At the time, the team said the fast-changing MCP specification made it "a poor fit for inclusion in the core WordPress package at this time".

The problem the team wants to fix

Agents can already work with WordPress through WP-CLI, the REST API and file access, but the proposal says these "often require local access or more advanced configurations."

Connecting an agent through MCP today means installing and configuring the MCP Adapter, making sure useful Abilities are available, and managing authentication through Application Passwords. The proposal adds "(hopefully not pasting them in plaintext to their agent)" and concludes: "This is not a scalable approach for the broad WordPress user base."

The goal it describes is a user telling their own agent, "I want you to help me with my example.com site." The agent recognises WordPress, provides a link to authorise access, and the user signs in.

Four workstreams

The team wants a dedicated focus lead for each area, paired with interested Core Committers. It says security review and audits, "including specialized security-focused AI models", will help make sure these features are safe to use.

Earlier signals and next dates

According to the published summary of the 21 October AI meeting, Adams shared that "Matt has approved moving forward with making MCP a de facto part of the WordPress experience." The same summary says early testing found agents "completed 0% of the benchmarked tasks using the MCP Adapter alone", mainly because the adapter does not yet bundle the Abilities needed for common tasks.

The 28 October meeting summary records a proposal to target a stable MCP Adapter 1.0 release around 8 December, alongside WordPress 7.2. Under that timeline, any core integration for 7.3 would need to be ready for review before 7.3 Beta 1, "tentatively expected in the first quarter of 2027." The summary notes that the scope and timing of version 1.0 are still open for discussion.

What this means for site owners

Analysis by Depakar B

This is a plan, not a shipped feature. Nothing changes on your site until a release includes it, and the dates could move. WordPress 7.2 is currently planned for 8 December, according to WordPress.org.

The OAuth workstream is the one to watch for security. Many agent set-ups today depend on Application Passwords, and the proposal itself warns against pasting them into an agent in plaintext. If you already use them for an agent or automation, review who holds one and revoke any you do not recognise. My guide to Application Passwords security explains how. My earlier explainer on the MCP Adapter covers how the current plugin works.

About this report

This report is based on posts and meeting summaries published by the WordPress AI team on make.wordpress.org, and WordPress.org News. Facts and quotes are taken from the sources credited below, which I re-read on 3 November 2026. Sections marked "Analysis" are my own view. I am an independent WordPress developer and am not affiliated with the organisations named here.

Credits and sources

Corrections

Updated 5 November 2026, 11:40 IST:52 IST: the description no longer says OAuth would "replace" Application Passwords (the proposal says users should not have to generate and share them by hand), the 21 October meeting attribution now quotes the summary exactly instead of naming a person it does not name in full, the 7.2 date is described as planned, and a background section, quotes and full source credits were added.

Spotted an error? Please contact me. Corrections are noted on this page with the date.