WooCommerce 11.3 changes MCP integration: what you need to update

WooCommerce 11.3 is changing how AI clients connect to a store through the Model Context Protocol (MCP). The deprecated WooCommerce-specific endpoint is being removed, and MCP connections will instead use the WordPress MCP Adapter. If you already connected an AI client to WooCommerce's old MCP endpoint, you should migrate that connection before upgrading.

What changes in WooCommerce 11.3?

WooCommerce has been moving away from its own MCP transport since 10.9. Version 11.3 completes that migration by removing /wp-json/woocommerce/mcp, its WooCommerce REST API key authentication, and the older REST-derived product and order abilities that existed specifically for that endpoint.

Instead, WooCommerce registers product and order abilities through WordPress, while the WordPress MCP Adapter plugin exposes those abilities to compatible clients. The default remote endpoint becomes:

Remote clients authenticate as a WordPress user, typically with a WordPress application password. WooCommerce permissions still apply when an ability runs.

If you already use the old WooCommerce MCP endpoint

An existing MCP connection using /wp-json/woocommerce/mcp and a WooCommerce REST API key will stop working after the move to 11.3. WooCommerce says requests to the removed endpoint will return HTTP 410 with migration guidance.

The practical migration is straightforward:

1. Install and activate the WordPress MCP Adapter plugin.
2. Create a WordPress application password for a user with only the capabilities the MCP client actually needs.
3. Change the MCP client endpoint to the MCP Adapter default server.
4. Replace the old WooCommerce REST API key authentication with the WordPress user and application password.
5. Test discovery and actions on staging before relying on the connection in production.

If the old REST API key existed only for MCP, it can be revoked once the new connection is working.

What does the MCP Adapter expose?

WooCommerce's current MCP documentation covers abilities for products and orders, including querying products, creating and updating products, querying orders, changing order status, and working with order notes. The adapter exposes a small set of MCP tools that let a client discover available abilities, inspect their schemas, and execute them.

Architecturally, this is cleaner than every plugin maintaining its own MCP endpoint. WooCommerce abilities can live alongside abilities registered by other WordPress plugins and use a shared connection layer. That matters for more complex business automation and AI workflows, where a useful agent may need access to more than just WooCommerce.

WooCommerce 11.3 also experiments with extensible abilities

A second change coming with 11.3 is aimed mainly at extension developers. WooCommerce is testing an experimental extensible abilities API that lets extensions add their own fields, filters, and validation to existing WooCommerce abilities.

For example, an extension could expose its own product metadata through the standard product ability rather than creating a separate MCP-specific version of that product operation. WooCommerce says the feature is off by default and still experimental, with known gaps around some order writes, custom product types, and variable-product workflows. It should be treated as a testing API for now, not a production dependency.

What should normal store owners do?

If you are not using MCP, there is nothing special to migrate. WooCommerce 11.2.1 remains the current stable release as of October 24, and these MCP changes are preparation for 11.3.

When 11.3 is released, handle it like any other meaningful WooCommerce update: use a recoverable backup, test important customizations, and verify checkout, payments, orders, subscriptions, emails, and integrations after the upgrade. Our WooCommerce update checklist covers that process.

Why this change matters

The important part is not simply that one REST endpoint is disappearing. WooCommerce is aligning its AI/tool integration with a shared WordPress abilities and MCP layer instead of maintaining a separate WooCommerce-specific transport.

For stores that eventually want AI systems to work with products, orders, support processes, CRM data, or other business systems, that shared architecture is more interesting than an isolated chatbot feature. It creates a cleaner base for combining WooCommerce development with controlled automation while keeping WordPress capabilities and permissions in the loop.

FAQ