Jason Adams @jason_the_adams (Team RepTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.) – Automattic
This week’s meeting focused on WordPress 7.2 release readiness, including testing the Secrets APIAPIAn API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., reviewing Abilities APIAbilities APIA core WordPress API (introduced in 6.9) that creates a central registry of capabilities, making WordPress functions discoverable and accessible to AI agents, automation tools, and developers. Transforms WordPress from isolated functions into a unified system. changes, and preparing developer documentation ahead of Release CandidateRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1. Contributors also agreed to move shared WordPress abilities into a dedicated Composer package under the WordPress GitHubGitHubGitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ organization, discussed plans for AI pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. 1.6.0 and its evolving AI workspace experience, and reviewed PHPPHPPHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php AI Client dependencies, documentation improvements, and plugin discovery on WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/.
WordPress 7.2 Release Readiness
@jeffpaul encouraged contributors to continue testing the Secrets API ahead of WordPress 7.2, particularly on multisiteMultisiteMultisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core. Advanced Administration Handbook -> Create A Network. installations where testing coverage can be limited. The API provides an important foundation for additional capabilities planned for WordPress 7.3.
With WordPress 7.2 Release Candidate 1 approaching, the team also discussed preparing developer notes for the Abilities API functionality included in the release. @jeffpaul will coordinate with @jorgefilipecosta or @gziolo to ensure documentation is drafted, ideally in time for the release candidate and accompanying field guide.
@justlevine requested additional feedback on a TracTracTrac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket proposing changes to how abilityAbilityA registered, self-documenting unit of WordPress functionality that can be discovered and invoked through multiple contexts (REST API, Command Palette, MCP). Includes authorization and input/output specifications. permissions are defined. The underlying concern is allowing permissions to be enumerated without executing permission callbacks. Without sufficient feedback before the release, @justlevine suggested reverting the proposed change to allow more time to consider the public API.
The team also noted that previous input coercion changes have been reverted in favor of a new input preparation function. Follow-up pull requests are being prepared in the AI plugin and MCP AdapterMCP AdapterTranslates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts. to align with the updated implementation once the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. changes land.
The package would centralize the development and maintenance of reusable abilities, allowing multiple projects to consume them as a Composer dependency rather than maintaining separate implementations. This approach would also enable projects such as WooCommerce to use shared abilities without requiring the entire AI plugin.
Following discussions in previous meetings and the absence of objections to the overall approach, contributors agreed to proceed with moving the package into the WordPress GitHub organization. The final repository name and several implementation details remain to be determined.
The team also discussed several considerations for the package’s longer-term development:
Ability lifecycle: Establishing how abilities move from experimental implementations to stable functionality and potentially into WordPress core.
Development workflows: Supporting experimentation without creating unnecessary dependencies or blocking progress in consuming plugins.
Naming and compatibility: Avoiding the core/ prefix for abilities developed within the AI plugin to prevent conflicts with existing or future core abilities.
Maintenance: Establishing clear ownership for reviewing contributions, managing releases, and maintaining the shared package.
@nikskyverge volunteered to coordinate the initial migrationMigrationMoving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. and maintainership, with @justlevine offering additional support. Contributors emphasized the need to broaden maintainership over time to avoid creating a single point of failure.
@jeffpaul will coordinate with the WordPress systems and MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. teams to facilitate the repository transfer. Existing abilities pull requests can then be migrated or consolidated into the shared package as appropriate.
AI Plugin 1.6.0 and AI Workspace
@jeffpaul outlined priorities for AI plugin 1.6.0, currently targeted for the end of November and expected to be the last regularly scheduled major plugin release before WordPress 7.2. A primary focus is the evolving AI Workspace concept, which brings together ongoing site agent and Command Palette work into a more unified experience within WordPress.
The initial implementation would provide a chat-based agent experience directly inside WordPress, using models available through configured AI connectors. Unlike the broader WordPress 7.3 vision of connecting external agents and tools through MCP, this first version would focus on interactions that operate within WordPress itself.
The team also hopes to incorporate the shared abilities package as a Composer dependency in 1.6.0. @dkotter noted that approximately a dozen abilities pull requests are currently open and could be migrated to the new package rather than blocking the release. Additional abilities can continue to be developed and released independently as the package and its integration workflows mature.
PHP AI Client Dependencies and Security
@justlevine raised questions about whether the PHP AI Client requires dependency updates ahead of the WordPress 7.2 release, particularly where upstream libraries may have received security improvements.
During the discussion, contributors clarified that Guzzle is currently a development dependency rather than a production dependency. However, other dependencies used in production, including PSR-related packages, may still warrant review.
Because another PHP AI Client release was not already planned, the team agreed to first establish whether any updates would affect the code shipped with WordPress 7.2 before allocating additional resources.
@justlevine will investigate the production dependency footprint and coordinate with @jason_the_adams if a release or additional review is warranted.
Documentation and Contributor Experience
Contributors revisited the question of how documentation for the AI plugin and MCP Adapter should be published and maintained. Although both projects include Markdown documentation within their repositories, there is not yet an established approach for presenting that documentation through a more accessible, user-facing interface. The discussion also highlighted the importance of making documentation contributions easier for non-developers, particularly contributors participating in WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Contributor Days.
Potential approaches include GitHub Pages or similar publishing workflows, although no specific solution was selected.
@justlevine also encouraged contributors to help improve existing MCP Adapter documentation, including reviewing and refining content that originated from AI-generated drafts.
Discoverability of AI Capabilities on WordPress.org
@nikskyverge provided an update on work to make AI-related plugin capabilities more discoverable within the WordPress.org Plugin Directory. An ability scanner developed following WordCamp Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ discussions can identify registered abilities and store that information as plugin metadata. The implementation has received an initial review from the Meta team and requires additional cleanup before progressing.
@nikskyverge also shared that a related Trac ticket has been opened to explore identifying plugins that consume the PHP AI Client. This could help users discover plugins that support AI connectors or provide AI-powered functionality, making it easier to understand which WordPress plugins can participate in broader AI workflows.
Next Steps
WordPress 7.2 testing: Contributors are encouraged to test the Secrets API, particularly on multisite installations, and provide feedback on the outstanding Abilities API permissions proposal.
Developer documentation:@jeffpaul will coordinate with @jorgefilipecosta or @gziolo to prepare Abilities API developer notes ahead of Release Candidate 1.
Shared abilities package:@nikskyverge and @jeffpaul will coordinate moving the repository into the WordPress GitHub organization, then continue refining integration workflows and migrating relevant abilities.
Package maintainership:@nikskyverge and @justlevine will provide initial maintenance support while identifying additional contributors.
AI plugin 1.6.0: Continue development of the AI workspace experience and prepare the shared abilities package integration for the targeted end-of-month release.
PHP AI Client:@justlevine will review production dependencies and consult @jason_the_adams if updates are needed before WordPress 7.2.
Documentation: Contributors are encouraged to submit improvements to MCP Adapter documentation and explore more accessible publishing and contribution workflows.
Plugin discoverability: Continue refining the abilities scanner and related WordPress.org Meta work to improve visibility into plugins supporting abilities and the PHP AI Client.
Upcoming Meetings
Contributors are welcome to join the weekly AI contributor call. All team meeting schedules are published on the WordPress Meeting Calendar.
AI Team Office Hours: Thursday, November 12, 2026 at 17:00 UTC.
This week’s meeting focused on the approach for developing and distributing WordPress abilities across coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., the AI pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party., and MCP AdapterMCP AdapterTranslates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts., including compatibility considerations and the roadmap for WordPress 7.3. Contributors also discussed OAuth authentication, the role of retrieval-augmented generation (RAG) in WordPress, and coordinating work across the AI team. The team identified follow-up work to confirm the shared abilities approach, communicate proposed changes more broadly, and clarify the recurring meeting schedule.
WordPress Abilities and MCP Adapter Integration
The team continued discussing how abilities should be developed and shared between WordPress core, the AI plugin, and MCP Adapter. @jorgefilipecosta outlined an approach where WordPress core trunk would become the source of truth for abilities once development reopens, with updates synchronized back to MCP Adapter. This would allow contributors to deliver new capabilities through the adapter ahead of their inclusion in a WordPress release.
@justlevine questioned whether abilities needed to be prioritized for WordPress 7.3 if they could already be made available through MCP Adapter. The discussion highlighted the importance of supporting multiple transport mechanisms, including REST and MCP, while avoiding unnecessary duplication and maintenance overhead.
Contributors also revisited the proposed shared abilities package discussed during the previous meeting. Before proceeding with implementation, the team needs to confirm the package approach, determine where abilities should be maintained, and establish how updates should flow between WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ repositories and the AI and MCP Adapter plugins.
Compatibility was another important consideration. Unlike abilities included in WordPress core, which must maintain backward compatibility, abilities exposed through MCP Adapter primarily serve AI models and agents that consume dynamically provided schemas. Contributors generally agreed that adapter-specific schemas could evolve more freely, although the implications for developers building programmatic integrations require consideration.
Rather than immediately proceeding with the proposed synchronization strategy, contributors agreed to document the approach in a GitHubGitHubGitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ issue and allow additional time for feedback from stakeholders who could not attend the meeting.
OAuth Authentication and WordPress 7.3
The team discussed ongoing OAuth development and its potential inclusion in WordPress 7.3. @ovidiu-galatan shared that an initial prototype implementing a minimal subset of OAuth functionality had been developed, while noting that the full protocol includes significant complexity and requires a clearly defined scope.
Contributors discussed continuing experimentation in a separate MCP Adapter development branch before pursuing core integration. The broader goal is to provide reusable authentication capabilities that can support MCP connections, REST APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”)
https://developer.wordpress.org/rest-api/ integrations, and other external applications.
The group supported pursuing OAuth in WordPress core independently of whether MCP Adapter itself is integrated into core. However, the proposed scope and implementation still require broader review and agreement.
@jason_the_adams will help coordinate a formal proposal on the AI team blog, cross-post it to the Core team, and bring the discussion to upcoming Core meetings. Contributors emphasized the importance of making this work visible early so interested developers can participate before architectural decisions are finalized.
Retrieval-Augmented Generation and Embeddings
An earlier discussion addressed community interest in retrieval-augmented generation (RAG) within WordPress. @gajendrasingh shared feedback from WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Rajasthan, where contributors asked about using RAG to search, filterFilterFilters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output., and retrieve WordPress content for AI applications.
@justlevine explained that vectorization and embeddings provide the foundational capabilities for these use cases. Embeddings are part of the WordPress 7.2 work, while the AI plugin is also exploring experimental support for adding embeddings to post types.
The discussion explored whether RAG itself belongs in WordPress core or is better supported through plugins and external services. While there was no formal decision, the distinction between providing foundational capabilities in core and leaving specialized implementations to plugins was an important consideration.
Contributors briefly discussed the challenges of maintaining integrations with external AI providers, particularly as providerProviderAn AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). APIs and policies continue to evolve.
@jason_the_adams emphasized the importance of working toward a consistent user experience rather than focusing exclusively on individual provider integrations. The broader vision remains enabling users to connect AI assistants and agents to WordPress sites and manage site functionality through those interactions.
This work connects directly to the ongoing abilities, MCP Adapter, and OAuth efforts, which together provide the underlying functionality, communication, and authentication needed to support those experiences.
Meeting Schedule and Coordination
The meeting also highlighted confusion caused by daylight saving time changes across contributor time zones. Some participants joined at the previously expected local time, resulting in separate discussions before the main meeting began.
@jeffpaul will confirm the recurring meeting time, update the calendar invitation to remain fixed at 17:00 UTC, and adjust the published meeting information as needed. This should provide a consistent reference for contributors regardless of local daylight saving time changes.
Next Steps
Abilities integration:@jorgefilipecosta will document the proposed development and synchronization strategy in an MCP Adapter GitHub issue, allowing contributors to review and provide feedback before implementation.
Shared abilities package: Confirm the package approach, then coordinate any necessary changes to WordPress.org repositories and update the AI and MCP Adapter plugins accordingly.
Contributor review:@justlevine will help bring additional contributors into the abilities discussion, including @apeatling and @nikskyverge. Contributors will have time to review the proposed approach asynchronously.
OAuth proposal:@jason_the_adams will coordinate a proposal for broader Core team review, while contributors working on OAuth continue refining its scope and implementation.
RAG research:@gajendrasingh will document findings from the community discussion, and @justlevine will share the AI plugin embeddings experiment.
Core release review:@jason_the_adams will review the TracTracTrac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket raised by @justlevine ahead of WordPress 7.2 Release CandidateRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1.
Meeting schedule:@jeffpaul will confirm the recurring meeting time and update the calendar invitation and meetings page as needed.
Upcoming Meetings
Contributors are welcome to join the weekly AI contributor call. All team meeting schedules are published on the WordPress Meeting Calendar.
AI Team Office Hours: Thursday, November 12, 2026 at 17:00 UTC.
AI 1.5.0 has been released and is available for download! “What’s new in AI…” posts (labeled with the #ai-release tag) are posted following every AI pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. release, showcasing new features included in each release.
We’re pleased to announce the release of AI 1.5.0, the latest update to the canonical plugin powering AI-powered features in WordPress. This release introduces six new Experiments, including Text to Speech, Content Verification, MCP Access, WebMCP, Revision Change Summary, and BlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Container Label Generation. It also expands the Embeddings infrastructure, improves Content Translation and Markdown Feeds, introduces additional AI providerProviderAn AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). connectors, and brings several Abilities into alignment with WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress..
What’s new in 1.5.0?
New Experiment: Text to Speech
The new Text to Speech experiment lets editors generate an audio version of a post, giving visitors the option to listen to content instead of reading it.
When enabled, editors can generate audio from a post’s title and content using a configured AI provider that supports speech generation. Audio processing runs in the background, allowing editors to continue working or return later while longer posts are processed.
Once generated, the audio file is saved to the Media Library and can be played directly in the editor. Editors can choose whether to display an audio player on the published post and regenerate the audio when needed. This provides another way for publishers to make their content accessible and available in different formats without requiring a separate audio production workflow.
New Experiment: Content Verification
The new Content Verification experiment introduces support for detecting C2PA Content Credentials in images uploaded to WordPress.
Content Credentials are a standard for attaching provenance information to digital media, helping publishers and audiences understand where content originated and how it may have been modified. When enabled, the experiment detects embedded C2PA data in uploaded JPEG, PNG, and WebP images and preserves the manifest information alongside the attachment. Credential status is displayed in the Media Library, including a new indicator in the grid view.
This initial implementation is read-only. It detects and preserves existing Content Credentials but does not yet perform cryptographic verification or generate new credentials for images. The experiment establishes a foundation for future content provenance features, including deeper verification and support for preserving credentials through WordPress image-processing workflows.
New Experiment: MCP Access
The new MCP Access experiment makes it easier to connect WordPress to external AI agents through the Model Context Protocol (MCP).
MCP provides a standardized way for AI applications and agents to discover and interact with tools and capabilities exposed by other systems. When enabled, the experiment installs and activates the MCP Adapter plugin when site permissions allow. It also adds a new Tools → MCP Access administration screen where site owners can review registered WordPress Abilities and control which ones are exposed to AI agents.
The interface displays the site’s MCP endpoint and provides controls for exposing or hiding individual Abilities, along with the option to restore their default settings. This separates the underlying MCP infrastructure from the controls site owners need to manage agent access, making it easier to explore how external AI systems can interact with WordPress functionality.
New Experiment: WebMCP
AI 1.5.0 also introduces a WebMCP experiment, allowing compatible AI-powered browsers to interact directly with the WordPress Block Editor.
While MCP Access exposes server-side WordPress Abilities to external agents, WebMCP focuses on interactions within the browser itself. Using the experimental document.modelContext interface, an AI agentAI AgentAn AI system that autonomously performs tasks and interacts with systems through available tools and resources. can interact with the editor through a collection of tools that support actions such as:
Reading the current post and updating its title.
Inserting, editing, moving, and duplicating blocks.
Modifying block attributes and content.
Saving and publishing posts.
These actions use the editor’s existing data stores, so changes appear directly in the editing interface as they happen. This provides an early look at how AI agents could work alongside editors within familiar WordPress interfaces rather than operating exclusively through external APIs.
New Experiment: Revision Change Summary
The new Revision Change Summary experiment helps editors understand what changed between two revisionsRevisionsThe WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. of a post.
WordPress already provides detailed revision comparisons, but interpreting those changes can become time-consuming for longer or more complex content. With this experiment enabled, editors can generate a plain-language summary of the differences between revisions directly from the visual or classic revision comparison screens.
The summary highlights meaningful changes to post content and titles, helping editors, reviewers, and content teams understand how a post has evolved without reviewing every individual change. The experiment is read-only and does not modify either revision or the underlying post. Additional improvements also preserve more detailed comparisons for multiline content such as tables and quotes.
As posts and pages grow in complexity, List View can become difficult to navigate when multiple Group, Columns, and other container blocks appear with generic names. This experiment uses AI to suggest concise, descriptive labels based on the content and purpose of a container. Generated labels are available in List View and the block Rename modal, helping editors identify sections without changing their visible content.
A follow-up enhancement also incorporates document-level context, including the post title, surrounding sections, and existing labels, to produce more useful suggestions.
For editors working with complex page layouts, reusable patterns, or long-form content, these labels can make document navigation and organization considerably easier.
Expanded embeddings infrastructure
AI 1.5.0 continues building on the Embeddings infrastructure introduced in previous releases.
Using WordPress Cron, the system can process existing content in batches, detect when content changes, and update or remove stored embeddings as needed. It also supports resuming interrupted operations and avoids unnecessary requests when content has not changed.
Embedding generation is not automatically activated for every site. Features that need embeddings must register their requirements, allowing the infrastructure to run only when needed.
Like the earlier embedding storage and vector ranking additions, this is primarily developer infrastructure rather than a new end-user experiment. It provides additional building blocks for future semantic search, content recommendations, retrieval, and other AI-powered workflows.
Previously, translation focused primarily on paragraphs and headings. AI 1.5.0 expands that behavior to blocks containing rich-text content, allowing more of a post’s content to be translated within the existing workflow. The release also improves translation behavior when working with the editor’s “Show template” mode and prevents translations from being applied to blocks that have been edited, removed, or replaced while a request was processing.
These changes make Content Translation more useful for complex posts and help protect editors’ work when content changes during a translation request.
Individual posts requested with ?output_format=markdown now include their approved comments, providing AI agents and other Markdown consumers with additional context from the discussion surrounding published content. The release also improves site-wide comment feeds, fixes content negotiation so requests respect the preferred response format, and applies existing WordPress feed filters for greater compatibility with other plugins.
One behavior has changed: individual post URLs using /<post>/feed/markdown/ are no longer supported. Consumers should request the post’s Markdown document using ?output_format=markdown instead.
Improved AI settings and provider discovery
AI 1.5.0 makes it easier to understand how different AI capabilities operate before enabling them.
The AI settings interface now more clearly distinguishes between stable Features and experimental functionality. Experiments that run automatically are identified, and an information control provides details about when each experiment runs, what information is sent to the configured AI provider, and how many requests it makes.
These improvements are intended to give site owners better visibility into AI usage, especially for experiments that can trigger requests automatically.
The release also expands the available connectors featured on Settings → Connectors, adding Mistral and Vercel AI Gateway alongside the existing Anthropic, Google, and OpenAI options. Featured connectors can be discovered, installed, activated, and configured from the same interface.
Additional links to the AI-Powered WordPress course make it easier for new users to find educational resources.
Updated Abilities Explorer
The Abilities Explorer has been rebuilt using WordPress DataViews, bringing its interface more closely into alignment with modern WordPress administration experiences. The updated Explorer makes it easier for developers and administrators to discover, inspect, and execute registered WordPress Abilities.
Three new REST APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”)
https://developer.wordpress.org/rest-api/ endpoints support retrieving and running Abilities, replacing parts of the previous implementation that relied on older administration patterns. Developers can also extend the Explorer with additional read-only columns using the new ai.abilitiesExplorer.fieldsJavaScriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser.
https://www.javascript.comfilterFilterFilters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output..
Updated core Abilities and breaking changes
AI 1.5.0 includes important updates to three general-purpose WordPress Abilities:
These Abilities have been synchronized with their corresponding implementations coming in WordPress core with 7.2 this December, helping developers work with consistent interfaces as the Abilities APIAbilities APIA core WordPress API (introduced in 6.9) that creates a central registry of capabilities, making WordPress functions discoverable and accessible to AI agents, automation tools, and developers. Transforms WordPress from isolated functions into a unified system. evolves. The updates introduce changes to request and response structures, including new where, fields, and pagination inputs for content and user queries, consistent result structures, and updated field names.
These updates include breaking changes for existing integrations. The deprecated aliases introduced in earlier releases have now been removed:
core/read-content → use core/content-query
core/read-users → use core/users-query
core/read-settings → use core/settings-get
Developers using these Abilities should review the updated schemas and adjust existing calls accordingly. Additional changes to date fields and user lookup behavior may also require updates.
Additional fixes and improvements
The release includes several fixes and smaller enhancements across existing experiments and administration interfaces:
Title Generation: A new Generate title button is available in the post Rename modal.
AI Request Logging: Successful requests from providers using custom transports are now recorded, and administrators can delete logs by age rather than only purging everything.
Suggest Reply: Reply suggestions are applied to the correct comment, and protected post titles and excerpts are no longer sent to AI providers.
Comment Moderation: Automatic analysis no longer processes pingbacks, trackbacks, or block editor Notes by default.
Content Classification: Improved handling of taxonomy terms containing special characters or non-ASCII text.
Key Encryption: Integration with the emerging WordPress Secrets APIAPIAn API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. includes backward compatibility and migrationMigrationMoving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. for existing encrypted keys.
Performance: Feature and experiment settings are loaded more efficiently, reducing repeated database queries on sites without persistent object caching.
AI Status: The dashboard widgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. now summarizes enabled and disabled experiments in a more compact format.
The release also improves how private and password-protected post information is handled in AI-powered comment workflows and includes additional protections around stored connector credentials.
Sites using the AI plugin are encouraged to update promptly.
What’s next?
Work is already underway on additional Features, Experiments, Developer Tools, and Abilities planned for 1.6.0 and future releases, including:
As always, we welcome feedback, testing, and contributions from the community. Whether you are interested in editor UXUXUX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it., APIs, accessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), performance, or AI ethics and policy, there are many ways to participate.
This week’s meeting focused on the newly published strategy for making WordPress ready for the agentic web, including coordinated work on the MCP AdapterMCP AdapterTranslates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts., coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. abilities, OAuth authentication, and user experience. Contributors also discussed a proposed shared abilities package, upcoming AI pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. and PHPPHPPHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php AI Client releases, and the roadmap for delivering a stable MCP experience alongside WordPress 7.2 and preparing for WordPress 7.3.
WordPress for the Agentic Web: Strategy and User Experience
@jeffpaul highlighted the newly published WordPress for the Agentic Web proposal, outlining the team’s priorities across the remaining WordPress 7.2 cycle and into 7.3. The strategy identifies three technical workstreams, MCP Adapter, Abilities, and OAuth authentication, supported by a coordinated user experience (UXUXUX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it.) effort to ensure they work together seamlessly.
@karmatosed volunteered to help lead the UX effort, emphasizing asynchronous collaboration and the need to map the complete user journey across these capabilities. @jeffpaul suggested beginning with the experience described in the proposal and identifying how the individual workstreams contribute to each step.
@apeatling also highlighted that user experience will vary significantly depending on which AI client or agent someone uses, requiring ongoing testing and refinement rather than a single implementation.
Contributors are encouraged to review the proposal and volunteer to help lead or contribute to the workstreams.
Currently, abilities may need to be maintained separately across the AI plugin, MCP Adapter, and other integrations. The proposed package would provide a shared implementation that these projects could consume without duplicating development work. The approach could also benefit third-party developers who want to use specific abilities without depending on an entire plugin. @nikskyverge is additionally exploring tooling to streamline the process of promoting abilities into WordPress core.
The prototype remains experimental, with outstanding considerations around autoloading, version management, and compatibility. The immediate priority remains getting useful abilities into the AI plugin and MCP Adapter, with the shared package potentially simplifying that work going forward.
AI Plugin 1.5.0 and AbilityAbilityA registered, self-documenting unit of WordPress functionality that can be discovered and invoked through multiple contexts (REST API, Command Palette, MCP). Includes authorization and input/output specifications. Compatibility
@jeffpaul and @dkotter shared that AI plugin version 1.5.0 was targeted for release on October 29. The release includes continued work on custom abilities, incorporating changes aligned with implementations being developed for WordPress core.
@justlevine raised concerns about potential breaking changes to ability schemas between versions 1.4.0 and 1.5.0, including renamed abilities and changes to existing interfaces. The team clarified that most content abilities are new to 1.5.0, limiting compatibility concerns for existing installations. However, settings abilities and other previously available functionality may require additional review.
Because these abilities remain part of an experimental feature, compatibility guarantees differ from those of stable functionality. Nevertheless, contributors agreed that any identified breaking changes should be clearly documented in the release changelog.
@justlevine will review the changes, while @dkotter will ensure relevant compatibility information is included in the release notes.
Contributors with outstanding pull requests targeted for 1.5.0 were encouraged to address remaining review and testing feedback promptly.
PHP AI Client 1.5.1
The team also discussed an upcoming maintenance release of the PHP AI Client, version 1.5.1, targeted for October 28 or 29. This release includes fixes following the PHP AI Client 1.5.0 integration into WordPress 7.2 BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1.
The goal is to incorporate the updates into WordPress 7.2 Beta 3, or Beta 4 at the latest, ensuring the fixes receive additional testing before the final WordPress release.
MCP Adapter Roadmap and WordPress 7.3
@justlevine provided an MCP Adapter update, noting that work continues on open pull requests and potential improvements to the adapter’s internal implementation.
Contributors were encouraged to review MCP Adapter issue #402, which collects user stories, technical improvements, testing requirements, and related work needed to deliver a more complete MCP experience.
@jeffpaul proposed targeting a stable MCP Adapter 1.0 release around December 8, alongside WordPress 7.2. This would provide an opportunity to gather real-world feedback and iterate ahead of the WordPress 7.3 development cycle. The proposed timeline would require any planned core integration for WordPress 7.3 to be ready for review ahead of Beta 1, tentatively expected in the first quarter of 2027. The scope and timing of MCP Adapter 1.0 remain open for further discussion.
@apeatling emphasized that delivering useful abilities should be the highest priority, since connecting an agent to WordPress provides limited value unless it can perform meaningful site operations.
The team also discussed whether additional abilities should be considered for WordPress 7.2 after Beta 1. While there may be opportunities to include sufficiently mature functionality, contributors cautioned against introducing unnecessary release pressure when experimental plugins can already make those abilities available for testing.
@nikskyverge will coordinate with @ovidiu-galatan to determine whether the MCP Adapter should consume abilities through the proposed shared package or integrate them directly in the short term.
Next Steps
Agentic Web UX:@karmatosed will begin mapping the end-to-end user journey and coordinating UX considerations across the MCP Adapter, Abilities, and OAuth workstreams.
Shared abilities package:@nikskyverge will continue refining the prototype and coordinate with @ovidiu-galatan on MCP Adapter integration.
AI plugin 1.5.0: Contributors will address outstanding pull request feedback ahead of the targeted release.
Ability compatibility:@justlevine will investigate potential breaking schema changes, with @dkotter ensuring they are documented in the changelog.
PHP AI Client 1.5.1: Finalize the maintenance release and prepare its fixes for inclusion in WordPress 7.2 Beta 3 or Beta 4.
MCP Adapter roadmap: Continue reviewing issue #402, prioritize foundational abilities, and refine the proposed scope for a stable 1.0 release.
Meeting documentation:@justlevine will share the draft meeting handbook, and @nikskyverge will review it and provide feedback.
Upcoming Meetings
Contributors are welcome to join the weekly AI contributor call. All team meeting schedules are published on the WordPress Meeting Calendar.
AI Team Office Hours: Thursday, October 29, 2026 at 17:00 UTC.
Recently, Google announced that its total users of AI exceeded 1 billion while OpenAI reports around 1.2 billion. Anthropic hasn’t shared a number, but others also share numbers in hundreds of millions. Even accounting for people using accounts across multiple platforms, AI adoption is staggering and shows no signs of slowing down.
This shift toward the Agentic Web is fundamentally changing how people experience the internet. People are increasingly using agents to search the web, find products, build apps, and run their businesses. There are interesting benefits, such as Adobe sharing that AI traffic converts 60% better than non-AI traffic, and brings in 53% more revenue. This means that once a user arrives they’re more confident in why they’re there and what they want to do. As these capabilities expand, users will expect their agents to work with the sites and platforms they already use.
Making WordPress Agent-Ready
Within the WordPress ecosystem, products such as Jetpack, Elementor, and WPVibe have demonstrated demand for users to manage their WordPress sites agentically. Commercialism aside, it’s amazing to think of users being able to build the most incredible versions of their WordPress worlds because their agents raise the bar in what they can achieve. It’s not just another surface by which to control WordPress, it opens another level of possibilities for those users. That’s exciting!
The goal remains: Democratize Publishing. To fulfill that mission in the Agentic Web, WordPress needs to make it possible for everyone to manage their sites with the agents they choose. This isn’t about putting an agent inside WordPress; it’s about making WordPress ready to work with the agents users bring. WordPress is the best solution for the open web, we need to make it the same in the agentic web.
The vision is simple: A user opens their personal agent and says, “I want you to help me with my example.com site.” The agent recognizes WordPress, provides a link to authorize access, and the user signs in. The agent responds, “I’m in! How can I help you with your site?”
Making that experience possible for every WordPress user requires native capabilities that are simple to discover, connect to, and use.
Making Agent Connectivity Native
Agents can already accomplish a lot with WordPress through WP-CLIWP-CLIWP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/https://make.wordpress.org/cli/, the REST APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”)
https://developer.wordpress.org/rest-api/, and file management. However, these approaches often require local access or more advanced configurations. For users bringing their own agents, connecting to WordPress needs to be much simpler.
MCP has emerged as the open standard for connecting agents to external systems. The existing MCP Adapter plugin provides an important foundation, but users still need to install and configure it, ensure useful Abilities are available (perhaps via the AI plugin), and manually manage authentication through Application Passwords (hopefully not pasting them in plaintext to their agent). This is not a scalable approach for the broad WordPress user base.
To deliver the experience described above, this proposal includes four coordinated areas of work, targeting WordPress 7.3 while using the 7.2 release cycle to establish the necessary foundations.
MCP AdapterMCP AdapterTranslates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts.
We’ll rapidly iterate on the MCP Adapter pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party., focusing on reliability, security, and usability to have a solid foundation alongside WordPress 7.2. From there the goal is to propose bringing MCP functionality into coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. for WordPress 7.3 either through a direct merge or a bundled approach that allows the adapter to evolve independently.
Abilities
Connecting an agent is only useful if it can accomplish meaningful tasks. We’ll identify a baseline of Abilities needed for common site management workflows, continuing rapid development through the AI and/or MCP Adapter plugins.
We’ll also explore whether a few additional foundational Abilities can land in WordPress 7.2 before the end of the betaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. cycles, with the broader goal of bringing a useful set of native Abilities into core for 7.3.
OAuth Authentication
Users should be able to securely authorize their agents without having to manually generate and share Application Passwords. During the 7.2 cycle, we’ll map out the necessary OAuth flows, architecture, and security considerations, targeting implementation in core for WordPress 7.3.
This functionality would benefit more than just MCP (e.g. the REST API) and should be developed in coordination with the broader Core team. The upcoming Secrets APIAPIAn API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. in WordPress 7.2 also provides an opportunity to support secure token handling.
End-to-End User Experience
The three technical capabilities above need to come together as one simple, intuitive experience. We’ll need to map the complete user journey, from an agent discovering a WordPress site and requesting access to performing tasks and managing or revoking permissions.
During the 7.2 cycle, we’ll need to develop and test prototypes to identify friction and inform all three technical workstreams. For 7.3., the goal is a cohesive experience that allows users to connect their preferred agents to WordPress without complex setup or technical knowledge.
Working Toward WordPress 7.3
These are ambitious goals and delivering them will require clear ownership and close collaboration across the project. We’re looking for a dedicated focus lead for each of these four areas, supported by contributors who want to help. Each lead will establish milestones for WordPress 7.2 and 7.3, coordinate development and testing, and share progress, blockers, and calls for help during our weekly AI contributor meetings.
We also want to pair each focus lead with interested Core Committers, involving them throughout development rather than waiting until features are ready for merge. This will help address architectural, compatibility, and security considerations early.
Security will be especially important as we introduce new ways for external agents to interact with WordPress. Appropriate review and audits, including specialized security-focused AI models, will help ensure these capabilities are safe to use.
While WordPress 7.3 is our shared target, inclusion in core will depend on technical readiness, security, and the normal core review processes.
Get involved
We’re looking for contributors willing to lead or help with MCP, Abilities, OAuth, and UXUXUX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it., as well as Core Committers interested in partnering with these efforts.
This week’s meeting focused on a significant step toward making Model Context Protocol (MCP) a native part of the WordPress experience, following approval to move forward with the initiative. Contributors discussed how MCP should be delivered, early agent benchmarking results, authentication and security requirements, and the balance between seamless user experiences and modular development. The team also identified maintenance bottlenecks affecting the PHPPHPPHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php AI Client and related components.
MCP as Part of the WordPress Experience
@jason_the_adams shared that Matt has approved moving forward with making MCP a de facto part of the WordPress experience, recognizing the growing adoption of AI agents and the importance of making WordPress accessible through agent-driven workflows.
The discussion clarified that this does not necessarily mean moving the entire MCP AdapterMCP AdapterTranslates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts. into WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.. Options include bundling the pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. with WordPress, enabling it through existing core interfaces, or incorporating specific capabilities directly into core.
@bacoords highlighted existing WordPress patterns, such as importers and connectors, where plugins can be installed behind the scenes without introducing complexity for users. @jorgefilipecosta emphasized defining the desired user experience first, then selecting the appropriate implementation.
@ovidiu-galatan advocated for preserving the MCP Adapter as a modular plugin, allowing it to evolve independently of WordPress core release cycles as the protocol continues to change.
The team found common ground around making MCP part of the default WordPress experience, while leaving the technical implementation open for further discussion.
Early testing found that agents completed 0% of the benchmarked tasks using the MCP Adapter alone, primarily because the adapter does not currently bundle the abilities needed to perform common WordPress operations. Agents using alternative methods, including REST APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”)
https://developer.wordpress.org/rest-api/ access, achieved higher success rates, although some approaches introduced security concerns.
The discussion distinguished between two related challenges:
Agent capability: Whether an agent can successfully complete tasks using WordPress tools. Adding standardized core abilities to the MCP experience can directly improve these results.
Agent selection: Whether an agent recommends or chooses WordPress in the first place. This depends on broader discoverability, product positioning, and model behavior, making it a longer-term challenge.
Contributors emphasized that the benchmarks demonstrate the importance of delivering a complete MCP experience rather than simply providing a connection mechanism.
Default Enablement and Agent-First User Experience
@apeatling raised concerns about requiring users to visit WP Admin and manually install or enable the MCP Adapter before connecting an AI agentAI AgentAn AI system that autonomously performs tasks and interacts with systems through available tools and resources..
For users interacting with existing WordPress websites through tools such as Claude or other personal agents, this additional setup could become a significant barrier.
The team explored whether MCP should be bundled and available by default, allowing agents to initiate authentication without requiring users to first configure the integration manually.
@jorgefilipecosta noted that bundling could also avoid filesystem restrictions that prevent plugin installation on some hosting environments. WordPress 7.3 was discussed as a possible target for deeper integration, though no release commitment was made.
The discussion also touched on creating a complete agent-driven experience for users starting without an existing WordPress website. @jason_the_adams noted that a broader proposal addressing hosting environments and agent-first site creation is being developed with @apeatling.
OAuth Authentication and Security
The team discussed the need for OAuth authentication to make MCP connections more accessible and secure for everyday WordPress users.
@jorgefilipecosta suggested that OAuth should be part of the default MCP experience, reducing reliance on application passwords and providing a familiar authorization flow.
@ovidiu-galatan raised concerns about introducing additional security-sensitive functionality into WordPress websites without sufficient review and auditing.
@justlevine emphasized that authentication is a broader WordPress architectural concern rather than something exclusive to MCP. Contributors discussed whether OAuth infrastructure should be implemented centrally in WordPress core, potentially leveraging the new Secrets APIAPIAn API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to secure tokens.
The team also highlighted the importance of separate credentials for individual clients and integrations to limit the impact of compromised access.
No final implementation decision was reached, with additional exploration needed around the appropriate architecture and security requirements.
PHP AI Client Maintenance and Streaming Support
@laurisaarni raised concerns about the pace of development for the PHP AI Client and whether core development processes can keep up with rapidly evolving AI providerProviderAn AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). APIs.
@jason_the_adams acknowledged that limited maintainer availability has become a bottleneck and proposed formally recruiting additional contributors willing to take ongoing responsibility for maintaining the library.
The discussion also identified a dependency affecting streaming support. Work in the PHP AI Client is currently blocked by an outstanding pull request in the WordPress Requests library, which itself has limited maintainer availability.
@whyisjake volunteered to help move the request forward, with coordination needed from an appropriate core committer to review and merge the changes.
The discussion reinforced the importance of sustainable maintenance across the AI building blocks and their underlying dependencies.
Next Steps
MCP integration proposal:@jason_the_adams will draft a post outlining the proposed direction for MCP in WordPress, including potential implementations and outstanding questions.
Agent benchmarking: Continue evaluating agent task completion, MCP capabilities, and WordPress discoverability to help guide implementation priorities.
OAuth architecture: Explore authentication requirements and whether shared OAuth infrastructure should be considered for WordPress 7.3.
PHP AI Client maintenance:@jason_the_adams will solicit additional maintainers to help reduce development bottlenecks.
Streaming support:@whyisjake will coordinate with a core committer to advance the outstanding Requests library pull request.
Upcoming Meetings
Contributors are welcome to join the weekly AI contributor call. All team meeting schedules are published on the WordPress Meeting Calendar.
AI Team Office Hours: Thursday, October 29, 2026 at 17:00 UTC.
This week’s meeting focused on finalizing coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. abilities ahead of WordPress 7.2 BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1, improving schema compatibility across AI providers, and integrating the new Secrets APIAPIAn API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. with WordPress connectors. Contributors also discussed early benchmarking results for AI agents interacting with WordPress, the balance between core functionality and ecosystem innovation, and emerging protocols for agent-based interactions.
Core Abilities: Schema Refinements and WordPress 7.2
The team refined the input and output schemas, separating abilities that query collections from those retrieving individual items. This simplifies the schemas, strengthens type definitions through nested objects, and improves compatibility with AI providers that have limitations around certain schema structures.
The settings abilityAbilityA registered, self-documenting unit of WordPress functionality that can be discovered and invoked through multiple contexts (REST API, Command Palette, MCP). Includes authorization and input/output specifications. remains ready, while the users and content abilities are undergoing final reviews ahead of Beta 1. Additional single-item and write abilities remain under development and may follow after the initial release.
@jeffpaul suggested prioritizing the core implementations until Beta 1, then returning to the remaining abilities in the AI pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.. The team agreed this would avoid duplicating work while the schemas are still changing, with the goal of making a broader set of abilities available through the plugin ahead of WordPress 7.3.
The discussion also highlighted workflows as an important non-AI use case for abilities. @nikskyverge noted that workflows provide a useful way to test whether abilities are sufficiently predictable, composable, and reusable beyond AI agents.
AI ProviderProviderAn AI service offering models for generation, embeddings, or other capabilities (e.g., Anthropic, Google, OpenAI). Schema Compatibility
@gziolo reported discovering compatibility issues with Gemini’s tool-calling implementation during testing. Certain schema constraints, including validation keywords such as minimum and maximum, are not consistently supported across providers.
@jorgefilipecosta recommended maintaining broadly useful validation rules in core while allowing individual provider integrations to remove or adapt unsupported keywords. This would avoid weakening core schemas to accommodate limitations in individual AI providers.
The team discussed potential improvements to the PHPPHPPHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php AI Client that would allow providers to transform schemas automatically, improving compatibility for third-party plugins that may not test against every available provider.
@gziolo will file issues documenting the Gemini incompatibilities, with additional testing planned during the WordPress 7.2 beta period.
Secrets API and Connector Integration
@whyisjake shared details about the newly merged Secrets API, which introduces support for securely storing encrypted values in WordPress core.
The API includes a migrationMigrationMoving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. mechanism that allows developers to convert existing plaintext options into encrypted secrets, providing a path for existing integrations to adopt the new functionality without requiring users to re-enter credentials.
@gziolo and @jorgefilipecosta discussed integrating the Secrets API directly with WordPress connectors so provider API keys can benefit from encrypted storage. @whyisjake agreed to open a tracking ticket and begin work, with timing dependent on the upcoming GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc.
https://wordpress.org/gutenberg/ code freeze.
The team also discussed compatibility with encryption functionality already implemented in the AI plugin, including the existing migration issue.
The Secrets API is part of a broader WordPress security initiative, although secure storage of AI provider credentials remains a key use case.
AI AgentAI AgentAn AI system that autonomously performs tasks and interacts with systems through available tools and resources. Benchmarking and MCP Effectiveness
@apeatling shared preliminary results from benchmarking AI agents against typical WordPress editing tasks. The benchmark includes approximately 50–60 prompts tested across different models and environments, comparing the MCP AdapterMCP AdapterTranslates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts., third-party integrations, and setups without dedicated connectors.
Early results suggest that agents can sometimes complete tasks more successfully without an MCP connector than with the current implementations. @apeatling emphasized that these findings are preliminary, with additional runs needed before drawing conclusions.
The benchmarking intentionally uses default environments without assuming tools such as WP-CLIWP-CLIWP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/https://make.wordpress.org/cli/ are already installed, providing a closer representation of the experience for everyday WordPress users rather than developers with customized setups.
@apeatling plans to share more comprehensive results and expand testing to include personal agents and environments such as Muse and Grok Bot.
WordPress Core, MCP, and Ecosystem Strategy
The team discussed whether WordPress should take a more opinionated approach to providing a consistent foundation for AI agents.
@apeatling raised concerns that multiple independently developed MCP servers could create fragmented experiences, inconsistent security practices, and confusion for both users and AI agents. A standardized entry point could provide a more reliable foundation while allowing hosts and plugins to extend functionality.
@nikskyverge drew parallels to WooCommerce, where extensions initially drive innovation before common capabilities are incorporated into the platform. Contributors generally recognized the value of allowing ecosystem experimentation while identifying opportunities to standardize successful approaches.
The discussion also explored how AI agents may increasingly become an entry point for discovering and interacting with websites, raising questions about how WordPress sites, hosts, and services remain discoverable through emerging agent platforms.
@jorgefilipecosta highlighted WebMCP as a promising direction for exposing WordPress functionality directly to browser-based agents, potentially allowing them to interact with forms, content, and editing interfaces without requiring separate connection setup.
No specific architectural changes were agreed upon, but the discussion reinforced the importance of a consistent, extensibleExtensibleThis is the ability to add additional functionality to the code. Plugins extend the WordPress core software. foundation for future agent interactions.
Next Steps
Core abilities:@jorgefilipecosta and @gziolo will continue finalizing the users and content abilities ahead of WordPress 7.2 Beta 1.
AI plugin abilities: Resume work on the remaining ability implementations after Beta 1, incorporating the updated core schemas.
Provider compatibility:@gziolo will document Gemini schema compatibility issues and investigate provider-level transformations.
Secrets API:@whyisjake will create a tracking ticket for connector integration and share demonstration videos with @jason_the_adams.
Beta 1 communication:@jason_the_adams will prepare a post summarizing the AI-related work included in WordPress 7.2 Beta 1.
Agent benchmarking:@apeatling will continue testing across models and environments, expand coverage to additional agent platforms, and share results with the team.
Upcoming Meetings
Contributors are welcome to join the weekly AI contributor call. All team meeting schedules are published on the WordPress Meeting Calendar.
AI Team Office Hours: Thursday, October 15, 2026 at 17:00 UTC.
This week’s meeting focused on preparing coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. abilities for WordPress 7.2 BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1, including the status of settings, content, and user abilities, architectural decisions around REST APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”)
https://developer.wordpress.org/rest-api/ independence, and naming conventions. Contributors also discussed the recent MCP AdapterMCP AdapterTranslates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts. release, improvements to abilityAbilityA registered, self-documenting unit of WordPress functionality that can be discovered and invoked through multiple contexts (REST API, Command Palette, MCP). Includes authorization and input/output specifications. exposure controls and connection management, and the longer-term goal of making AI integration with WordPress easier for everyday users.
Core Abilities: WordPress 7.2 Readiness
@jorgefilipecosta provided an update on the core abilities targeted for WordPress 7.2. The settings ability has received approval from a core reviewer, content abilities have incorporated recent feedback, and user abilities are undergoing another iteration. Additional abilities for updating content, media, and comments are also progressing through the AI pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party..
@gziolo emphasized the importance of reviewing the broader set of abilities together to ensure consistent naming, functionality, and compatibility. He suggested prioritizing read-only abilities for content and users, which would provide immediate value and allow developers to begin testing integrations while more complex write operations continue to evolve.
@jason_the_adams supported moving forward with the ready abilities rather than treating the broader catalog as an all-or-nothing release. He committed to reviewing the settings, content, and user implementations, with a follow-up discussion planned if outstanding issues could not be resolved through code review.
@jorgefilipecosta will also update the draft merge proposal to reflect the current implementation status and release timeline.
Core Abilities Architecture and Security
The team discussed whether core abilities should proxy existing REST API functionality or operate through an independent implementation.
@gziolo outlined trade-offs between the two approaches, including implementation complexity, compatibility with existing plugins, and the potential for unintended behavior when REST API filters affect exposed data.
@jorgefilipecosta clarified that the current implementation uses a parallel mechanism rather than routing ability execution through REST. Post types must explicitly opt in using show_in_abilities, independently of their REST API visibility. This prevents accidentally exposing content that plugins may have restricted through REST-specific filters.
The team generally supported maintaining this separation, recognizing that explicit opt-in introduces additional work for developers but provides a safer foundation for exposing WordPress functionality, including through AI tools.
Ability Naming and Categorization
@justlevine raised questions about the proposed noun-verb naming convention, including names such as settings/get and content/query.
@jorgefilipecosta explained that placing the entity name first groups related abilities together when sorted alphabetically and aligns with conventions already used by WooCommerce. The distinction between get and query reflects whether an ability retrieves a specific value or supports more complex filtering and searches.
@raftaar1191 also proposed allowing abilities to belong to multiple categories rather than a single required categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging..
@jason_the_adams explained that ability categories were originally introduced to help AI agents and other consumers narrow down large collections of available tools. Allowing multiple categories could weaken that filtering behavior, so the team encouraged documenting concrete use cases before reconsidering the existing design.
A tracking issue will be opened to explore the proposal further.
MCP Adapter Release and Improvements
@jason_the_adams highlighted the positive community response to the recent release of the MCP Adapter on WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/.
@ovidiu-galatan shared ongoing work to improve the adapter, including breaking down an issue related to displaying connection information and server status into smaller tasks. A maintenance release addressing outstanding issues was planned for the following week.
The team also discussed compatibility concerns when different versions of shared functionality are bundled across plugins and WordPress core. Further investigation is needed to clarify version conflicts and how implementations should interact when multiple versions are present.
Ability Exposure Controls and User Experience
@andrei shared progress on an experimental interface in the AI plugin for controlling which abilities are exposed through MCP integrations. The implementation uses WordPress DataViews and could provide an initial interface for users to manage exposed capabilities.
@dkotter recommended continuing with the implementation in the AI plugin rather than delaying it to move the functionality into the MCP Adapter. Because it is experimental, the interface can be refined or relocated as the integration matures.
@jason_the_adams noted that the MCP Adapter is increasingly reaching users beyond its original developer audience, making clearer onboarding and management interfaces important. @nikskyverge is preparing a release post that explains the adapter’s development history and current capabilities.
Looking further ahead, @apeatling emphasized that the ideal experience should require minimal configuration, allowing users to connect AI tools to WordPress without needing to understand the underlying protocols or infrastructure. The discussion highlighted the importance of balancing secure, flexible controls with an experience that feels seamless for everyday users.
Next Steps
Core abilities reviews:@jason_the_adams will review the settings, content, and users query implementations, with contributors regrouping if significant blockers remain.
WordPress 7.2 merge proposal:@jorgefilipecosta will update the proposal to reflect the current scope and timeline.
Ability categorization:@raftaar1191 will open a tracking issue exploring support for multiple categories per ability.
MCP Adapter:@ovidiu-galatan will continue work on connection management improvements and prepare a maintenance release.
Version compatibility: Contributors will investigate conflicts when multiple versions of shared functionality are bundled across plugins.
MCP Adapter communication:@nikskyverge will continue drafting the release post outlining the adapter’s capabilities and intended audience.
Upcoming Meetings
Contributors are welcome to join the weekly AI contributor call. All team meeting schedules are published on the WordPress Meeting Calendar.
AI Team Office Hours: Thursday, October 15, 2026 at 17:00 UTC.
This week’s meeting focused on the roadmap for bringing coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. WordPress abilities into future releases, the role of the AI pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. and Model Context Protocol (MCP) Adapter in validating and distributing those abilities, and outstanding technical considerations around schema design and compatibility. The team discussed a potential timeline for WordPress 7.2 and 7.3, with an emphasis on balancing faster adoption against long-term architectural stability.
Core Abilities Roadmap and WordPress 7.2
@jorgefilipecosta shared a draft proposal outlining a path for developing and validating core WordPress abilities ahead of their inclusion in WordPress core. The proposal calls for making a broader set of abilities available through the AI plugin by the WordPress 7.2 release, with the goal of including ready abilities in 7.2 and targeting broader core adoption in 7.3.
The discussion focused on content-related abilities, including querying and managing posts, as initial candidates. Contributors emphasized that these are fundamental capabilities for a content management system and that a shared implementation would reduce duplication across plugins and integrations.
@gziolo noted that existing core pull requests have undergone security reviews and REST APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”)
https://developer.wordpress.org/rest-api/ compatibility testing, providing confidence in their readiness. @jorgefilipecosta also confirmed that earlier feedback on naming conventions has been addressed, though additional validation against real-world implementations and AI clients remains valuable.
The team generally supported using the AI plugin to validate abilities before core inclusion, while recognizing that neither WordPress 7.2 nor 7.3 should become a hard deadline for functionality that has unresolved technical concerns or lacks consensus.
MCP AdapterMCP AdapterTranslates WordPress abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools, resources, and prompts. and Abilities Distribution
@justlevine proposed using the MCP Adapter as an additional distribution channel for MCP-specific abilities, allowing integrations to move forward without requiring every capability to be immediately included in WordPress core.
The approach would separate immediate MCP integration needs from the longer-term work of establishing reusable, protocol-independent abilities in core. This would allow MCP-specific implementations to evolve independently while reducing pressure to finalize core interfaces prematurely.
@gziolo, @jason_the_adams, and others emphasized that the MCP Adapter should not become a substitute for bringing foundational abilities into core. Standardized core abilities would reduce ecosystem fragmentation, improve consistency across plugins, and establish examples of secure implementation practices for developers.
The discussion also highlighted that abilities serve more than MCP integrations, with WebMCP and the WordPress AI Client representing additional consumers.
The general direction was to continue prioritizing core adoption while allowing the MCP Adapter to address immediate, protocol-specific needs independently.
AbilityAbilityA registered, self-documenting unit of WordPress functionality that can be discovered and invoked through multiple contexts (REST API, Command Palette, MCP). Includes authorization and input/output specifications. Schemas, Compatibility, and Deprecation
@justlevine raised concerns about the long-term flexibility of flat input schemas, particularly as abilities expand to support more sophisticated filtering, sorting, and pagination. Nested input objects, following patterns established by GraphQL, were suggested as a way to improve extensibility and reduce future compatibility challenges.
@jorgefilipecosta noted that the current schemas follow established WordPress REST API and WooCommerce conventions and have not demonstrated significant compatibility issues in existing testing.
@jason_the_adams requested side-by-side examples of the different schema approaches to help distinguish necessary changes from potential future improvements. The team emphasized identifying concrete blockers rather than delaying progress in pursuit of an ideal design.
@justlevine also reported progress on ability deprecation support, with a pull request already submitted and additional work underway to support deprecating individual ability arguments. This work could help abilities evolve without introducing unnecessary breaking changes.
Schema examples:@justlevine will share side-by-side examples of flat and nested input structures to clarify the compatibility concerns.
Ability development: Continue work on core ability candidates, including schema validation, deprecation support, and testing across MCP and other consumers.
Slug fragments:@justlevine will continue work to unblock the slug fragments implementation.
Release planning: Continue refining the proposed WordPress 7.2 and 7.3 roadmap, identifying remaining technical blockers and opportunities for real-world validation through the AI plugin.
Upcoming Meetings
Contributors are welcome to join the weekly AI contributor call. All team meeting schedules are published on the WordPress Meeting Calendar.
AI Team Office Hours: Thursday, October 1, 2026 at 17:00 UTC.
You must be logged in to post a comment.