--- title: "WordPress For The Agentic Web: The 7.3 Plan Explained" url: https://nexterwp.com/blog/wordpress-agentic-web-plan/ date: 2026-11-03 modified: 2026-11-03 lang: en author: "Aditya Sharma" description: "WordPress has proposed native MCP, abilities and OAuth so users can connect their own AI agents. Here is the plan for 7.2 and 7.3." image: https://nexterwp.com/wp-content/uploads/2026/11/nexter-wordpress-agentic-web-plan-featured-1024x538.webp word_count: 637 --- # WordPress For The Agentic Web: The 7.3 Plan Explained ## Key Takeaways - WordPress 7.3 es el objetivo para hacer WordPress listo para los agentes que los usuarios traen consigo, mientras que el ciclo 7.2 construye las bases para MCP Adapter, abilities, OAuth y la experiencia de extremo a extremo. - MCP Adapter pasa por mejoras de fiabilidad, seguridad y usabilidad, y la propuesta plantea llevar MCP al core de WordPress, ya sea fusionado o incluido, para 7.3. - OAuth authentication elimina la necesidad de generar y compartir Application Passwords, y el post señala que los flujos y la seguridad se mapean en 7.2 antes de implementarse en core para 7.3. - WordPress Abilities API permite que un plugin describa una acción de forma estándar para que cualquier agente conectado la descubra y la invoque, y Nexter Blocks ya registra abilities a través de esta API. WordPress has published a plan to make sites ready for the agents people bring with them. The proposal, posted on October 28, 2026 by the WordPress AI team, aims to let a user tell their own AI agent to help with their site, have the agent recognise WordPress, and get authorised through a normal sign-in link. It targets WordPress 7.3, with the 7.2 cycle used to build the foundations. This guide explains the four parts of the plan, what is planned for 7.2 versus 7.3, and what site owners and plugin makers can do now. Everything here comes from the official [WordPress for the Agentic Web](https://make.wordpress.org/ai/2026/10/28/wordpress-for-the-agentic-web/) post, and it is a proposal, not shipped software. Table of Contents ## What The Plan Is Trying To Fix Agents can already work with WordPress through WP-CLI, the REST API and file access. The proposal points out that these routes often need local access or a more advanced setup. For someone bringing their own agent, connecting should be far simpler. Today, using the MCP Adapter plugin means installing and configuring it, making sure useful abilities exist, and managing authentication through Application Passwords. The post calls that approach unscalable for the broad WordPress user base. The goal is not to put an agent inside WordPress. It is to make WordPress ready for whichever agent a person already uses. ## The Four Areas Of Work | Area | What it covers | Timing in the post | | ---- | -------------- | ------------------ | | MCP Adapter | Improve reliability, security and usability of the adapter plugin, then propose bringing MCP into core, either merged or bundled | Solid alongside 7.2, core proposal for 7.3 | | Abilities | Define a baseline of abilities for common site management tasks, through the AI and MCP Adapter plugins | Possibly a few foundational abilities in 7.2, a useful native set for 7.3 | | OAuth authentication | Let users authorise agents securely without generating and sharing Application Passwords | Map flows and security in 7.2, implement in core for 7.3 | | End-to-end experience | One simple journey from an agent finding a site, to asking for access, to working and revoking permissions | Prototypes in 7.2, cohesive experience for 7.3 | The post adds that the upcoming Secrets API in WordPress 7.2 gives a chance to support secure token handling for the OAuth work. ## What Changes For Site Owners Nothing changes today. The plan says inclusion in core depends on technical readiness, security and the normal core review process, so 7.3 is a target and not a promise. If it lands, the practical gain is that connecting an agent would work like authorising any other app, instead of copying a password into a configuration file. Security gets its own call-out in the post. New ways for outside agents to act on a site need review and audits, including specialised security-focused AI models. That fits the wider picture, where agents with write access are a new risk surface, not only a convenience. ***Also Read:** [MCP Security For WordPress](https://nexterwp.com/blog/mcp-security-wordpress/) for the risks to weigh before you give an agent access to a live site.* ## What Plugin Makers Can Do Now Abilities are the piece plugin makers can act on today. The WordPress Abilities API lets a plugin describe an action in a standard way so any connected agent can discover and call it. The post asks for contributors and focus leads for MCP, Abilities, OAuth and user experience, and asks Core Committers to partner with them early. Nexter Blocks already registers abilities through this API, so an agent can work with its blocks. Our guide to [Nexter Abilities](https://nexterwp.com/blog/nexter-abilities-explained/) explains how that works in practice. ## What This Doesn’t Cover This guide does not predict whether every item ships in 7.3, and it does not cover the technical design of the OAuth flow, which the post says still needs to be mapped. For the wider background on agents and WordPress, read the guides below. #### Suggested Reading - [WordPress MCP Server](https://nexterwp.com/blog/wordpress-mcp-server/) - [WordPress Abilities API](https://nexterwp.com/blog/wordpress-abilities-api/) - [WordPress 7.2 Guide](https://nexterwp.com/blog/wordpress-7-2/) #### Stay updated with Helpful WordPress Tips, Insider Insights, and Exclusive Updates – Subscribe now to keep up with Everything Happening on WordPress! Subscribe