WordPress 6.9 Abilities API Lets AI Agents Discover Your Store’s Tracking
WordPress 6.9 shipped the Abilities API in December 2025, creating a machine-readable registry where plugins declare what they can do. The MCP Adapter bridges this registry to AI agents like Claude and ChatGPT. Most WooCommerce tracking plugins have not registered a single ability, which means AI agents composing workflows cannot discover or interact with conversion tracking. The tracking plugin that registers abilities first gains a structural advantage in the AI-agent-managed WordPress future.
What the Abilities API Actually Does
WordPress now has a structured menu of capabilities that any external tool — human or AI — can read, understand, and execute.
WordPress 6.9 shipped in December 2025 with a framework that quietly changes how the entire platform communicates with external tools. The Abilities API creates a standardised, machine-readable registry at /wp-json/wp-abilities/v1/ where plugins declare typed, permissioned capabilities. Think of it as a restaurant menu for your WordPress site — every registered ability specifies exactly what it does, what inputs it needs, what outputs it returns, and who has permission to use it.
Before this, AI tools interacting with WordPress had to guess at what a site could do, or developers had to write custom code for every single integration. The Abilities API replaces guesswork with structure. A plugin calls wp_register_ability(), defines the ability’s schema, and it becomes discoverable to any tool that knows how to read the registry.
Only three core abilities ship by default: get-site-info, get-user-info, and get-environment-info. Everything else depends on plugins registering their own capabilities — and that is where the gap opens for WooCommerce tracking.
WordPress 6.9 shipped the Abilities API in core in December 2025, creating a standardized registry at /wp-json/wp-abilities/v1/ where plugins declare typed, permissioned capabilities.
The MCP Bridge — From Registry to AI Agent
The Abilities API describes what your site can do. The MCP Adapter lets AI agents actually do it.
The Model Context Protocol, originally created by Anthropic as an open standard, provides a structured way for AI models to communicate with external tools. The WordPress MCP Adapter, released in February 2026, takes whatever Abilities are registered on your site and exposes them as MCP tools that AI clients can discover, inspect, and execute.
The interaction model follows a clear hierarchy: discover what is available, inspect the schema, then execute. Claude Desktop, ChatGPT, Cursor, and VS Code can all connect to a WordPress site through the MCP Adapter. An AI agent asks the site what it can do, gets back a structured list of callable functions, and can then execute those functions within the permissions of the connected user.
Authentication is the key differentiator. WordPress.com handles MCP connections through OAuth 2.1 — the AI tool authenticates through the browser, inherits the logged-in user’s permissions, and access can be revoked at any time. Self-hosted WordPress sites currently rely on JWT tokens or Application Passwords, which adds a configuration step but provides the same functional result.
The practical implication is significant. A WooCommerce store operator could connect Claude Desktop to their site and ask natural language questions about orders, products, or site health — provided the relevant plugins have registered their capabilities as Abilities. Without registration, the AI agent sees nothing.
The WooCommerce Tracking Gap
Most WooCommerce tracking plugins have not registered a single ability, making them completely invisible to AI agents.
Here’s the thing: WordPress 6.9 provides the infrastructure, but the tracking plugin ecosystem has not adopted it. The major WooCommerce tracking plugins — the pixel managers, the server-side GTM connectors, the event pipelines — have not called wp_register_ability(). Their functionality exists, but it is invisible to any AI agent connecting through MCP.
An AI agent composing a WooCommerce workflow cannot discover that tracking exists on the site, cannot check whether events are firing correctly, and cannot validate that conversion data is reaching ad platforms. The tracking infrastructure is a black box to the very tools that are increasingly managing WordPress workflows.
This is not a theoretical problem. As AI agents become the primary interface for managing WordPress sites — a trajectory the WordPress AI Team is actively pursuing — tracking plugins that remain invisible lose their operational advantage. An AI agent managing a WooCommerce store’s marketing cannot optimise what it cannot see or interact with.
The default-deny model is correct from a security perspective. Abilities must be explicitly registered and marked as exposed before MCP clients can access them. But this security model also means that plugin inaction equals permanent invisibility.
The MCP Adapter released in February 2026 bridges WordPress Abilities to the Model Context Protocol, enabling AI agents like Claude Desktop and ChatGPT to discover and execute plugin functionality.
You may be interested in: WordPress 6.8 Speculative Loading Is Firing GA4 and Meta Pixel Ghost Visits
What Tracking Abilities Would Look Like
The concrete capabilities a tracking plugin should register to become AI-agent-discoverable.
A well-designed tracking plugin would register abilities across several operational categories. Event validation abilities would let an AI agent check whether a specific event type — purchase, add-to-cart, page view — fired correctly for a given session or order. Pipeline health abilities would report whether the server-side connection to BigQuery, Google Ads, or Meta CAPI is active and delivering events.
Conversion confirmation abilities would let an agent verify that a specific WooCommerce order’s conversion data reached the destination ad platform. Data quality abilities would inspect event payloads for missing or malformed fields. Tracking status abilities would report whether the overall tracking infrastructure is healthy or degraded.
| Ability Category | Example Ability | What AI Agent Can Do |
|---|---|---|
| Event Validation | validate-purchase-event | Confirm a WooCommerce purchase event fired and payload is complete |
| Pipeline Health | check-pipeline-status | Report whether server-side pipeline is active and delivering |
| Conversion Confirmation | confirm-conversion-delivery | Verify order conversion data reached Google Ads or Meta CAPI |
| Data Quality | inspect-event-quality | Check event payloads for missing user-provided data fields |
| Tracking Status | get-tracking-health | Overall health score of the tracking infrastructure |
Each of these abilities follows the same pattern: typed inputs, typed outputs, capability-based permissions. An AI agent does not get raw database access — it gets structured, validated responses that respect the WordPress permission model. A shop manager can check tracking health; only an administrator can modify pipeline configuration.
The Ecosystem Is Moving Fast
Third-party developers are already building on the Abilities API while tracking plugins wait.
The Enable Abilities for MCP plugin, available on WordPress.org, registers 58 abilities across 13 categories — including WooCommerce product management, order management, and customer management using the native WooCommerce API. It demonstrates the scope that is possible and the gap that tracking plugins are leaving unfilled.
The WebMCP Abilities plugin has already extended the pattern further, bridging registered WordPress Abilities to Chrome’s new WebMCP standard so browser-based AI agents can discover site capabilities. Register once with wp_register_ability(), and both the MCP Adapter for CLI/API agents and WebMCP for browser-based agents pick it up automatically. Two transports, one registration.
InstaWP has built MCP integration directly into its WordPress hosting platform — a single toggle in the dashboard enables MCP, and Claude Desktop connects with a copied URL. No JSON configuration, no Application Password creation, no proxy setup. The gap between having MCP installed and having it usable is disappearing rapidly.
WordPress 7.0, planned for April 2026, will merge the Abilities API deeper into core. This is not a plugin experiment — it is becoming a fundamental WordPress API that all plugins are expected to use. The DreamHost team described WordPress 6.9 as the kind of release that ships features invisible to the end user but completely changes what developers can create.
Only three core abilities ship by default — get-site-info, get-user-info, and get-environment-info — and most WooCommerce tracking plugins have registered zero additional abilities.
You may be interested in: Google AI Mode Is Default — What It Means for Your WooCommerce Data
What This Means for WooCommerce Store Operators
The tracking plugin that registers abilities first gains a structural advantage that compounds as AI agent adoption grows.
For store operators, the immediate action is straightforward: check whether your tracking plugin has registered any WordPress Abilities. If you visit /wp-json/wp-abilities/v1/ on your site and see only the three core abilities, your tracking infrastructure is invisible to every AI agent that connects.
The competitive dynamic here is first-mover, not feature parity. The first tracking plugin to register comprehensive abilities — event validation, pipeline health, conversion confirmation — becomes the default recommendation when AI agents evaluate what tools to use on a WooCommerce site. An agent composing an e-commerce workflow will naturally select the plugin whose capabilities it can see and interact with.
This matters beyond tracking. As AI agents manage more of the WordPress operational workflow — content publishing, order management, customer communication — the plugins that are discoverable through Abilities will be favoured over those that remain opaque. Tracking is just the first domain where the gap is most visible because tracking failures are time-sensitive and expensive.
Transmute Engine™ is being designed with Abilities API registration as a core feature — making server-side tracking infrastructure discoverable, inspectable, and manageable by AI agents from day one.
Key Takeaways
- WordPress 6.9 created the registry: The Abilities API ships in core, providing a standardised way for plugins to declare what they can do in a machine-readable format.
- The MCP Adapter connects AI agents: Released February 2026, it bridges Abilities to Claude, ChatGPT, Cursor, and any MCP-compatible tool.
- Tracking plugins are invisible: Most WooCommerce tracking plugins have not registered a single ability — AI agents cannot discover or interact with conversion tracking.
- The ecosystem is moving ahead: Third-party plugins already register 58+ abilities. WordPress 7.0 will deepen core integration. Browser-based AI agents are joining CLI-based ones.
- First-mover advantage is real: The tracking plugin that registers abilities first becomes the default in AI-agent-managed WooCommerce workflows.
The Abilities API, shipped in WordPress 6.9 core in December 2025, is a standardized registry where plugins declare typed, permissioned capabilities in a format that both humans and machines can read. Each ability specifies inputs, outputs, permission rules, and descriptive labels. When an AI agent connects to a WordPress site, it reads this registry to understand exactly what actions it can perform.
The MCP Adapter bridges registered WordPress Abilities to the Model Context Protocol, which AI agents like Claude Desktop and ChatGPT use to discover and execute functionality. If a tracking plugin registers abilities for event validation, pipeline health checks, or conversion confirmation, AI agents can monitor and troubleshoot tracking without manual intervention.
The Abilities API is new — it shipped in December 2025 and the MCP Adapter followed in February 2026. Most plugin developers have not yet updated their code to call wp_register_ability(). By default, abilities are invisible to MCP clients, so unless a plugin explicitly registers and marks abilities as exposed, AI agents cannot discover them.
A tracking plugin could register abilities for checking event delivery status, validating conversion pipelines, confirming pixel firing, inspecting data quality, and reporting tracking health. These abilities would let an AI agent monitor tracking in real-time, flag failures automatically, and even trigger remediation without requiring a human to log into the WordPress admin.
References
- WordPress Developer Blog (February 2026). From Abilities to AI Agents: Introducing the WordPress MCP Adapter.
- WordPress MCP Adapter GitHub Repository (2026). Official WordPress package for MCP integration with Abilities API.
- WordPress.org Plugin Directory (2026). Enable Abilities for MCP — 58 abilities across 13 categories including WooCommerce.
- InstaWP (March 2026). WordPress MCP Adapter Review — architecture, capabilities, and WordPress 7.0 roadmap.
- DreamHost (May 2026). AI for WordPress 6.9: Use Cases, Plugins, and Tools.
- miniOrange (May 2026). Abilities API for WordPress in 6.9 and the Role of MCP.
- WS Form (November 2025). How to Create an MCP Server in WordPress with the Abilities API and MCP Adapter.
If you want to understand how AI-agent-discoverable tracking infrastructure changes your WooCommerce data strategy, start with a Seresa tracking diagnostic.