WooCommerce 11.3 removes its MCP endpoint: how to reconnect, and what MCP can do for your store

WooCommerce 11.3 removes its own MCP endpoint. If you connected Claude or another AI assistant to your store through /wp-json/woocommerce/mcp with a WooCommerce API key, that connection stops working when you update. WooCommerce 11.3 is scheduled for the week of November 9, 2026, and its first beta came out on October 26, so there is still time to test on staging. MCP on WooCommerce doesn’t go away, though. It moves to the WordPress MCP Adapter plugin, and WooCommerce’s product and order abilities come along, switched on by default.

Below is what changes, how to reconnect, and the bigger question for a store owner: which jobs are worth handing to an assistant, and which should stay with a person. The removed endpoint, the abilities and the permission checks below were tested on WordPress 7.1.3 with a WooCommerce development build that already includes the 11.3 changes, and MCP Adapter 0.7.1.

What changes for WooCommerce MCP in 11.3?

The old endpoint, its API key login and its REST-based tools are removed, and the MCP Adapter becomes the only way in. WooCommerce’s developer blog lists the changes:

• The endpoint is gone. Any request to /wp-json/woocommerce/mcp now gets an HTTP 410 response.
• API key login is gone. The X-MCP-API-Key header, which carried a WooCommerce REST API key, no longer works.
• The feature toggle is gone. The MCP option under WooCommerce, Settings, Advanced, Features no longer exists.
• The old tools are replaced. Tools such as woocommerce/products-list and woocommerce/orders-create are removed, and purpose-built abilities take their place.
• The MCP Adapter is required. WooCommerce no longer bundles its own copy, so the adapter plugin has to be installed and active.

The 410 isn’t a bare error. In testing, the old endpoint answered with a message that names the fix: install and activate the MCP Adapter, then connect to /wp-json/mcp/mcp-adapter-default-server with a WordPress application password. Stores that had the MCP feature switched on also get an admin notice after updating, headed “WooCommerce MCP has been removed.”, with a link to install or activate the adapter.

How do you reconnect your MCP client after updating to WooCommerce 11.3?

Install the MCP Adapter, create an Application Password for a dedicated user, and point your client at the adapter’s default server. Do it on staging first.

1. Install and activate MCP Adapter from Plugins, Add New Plugin, or with wp plugin install mcp-adapter --activate. It worked if https://yourstore.com/wp-json/mcp lists /mcp/mcp-adapter-default-server.
2. Create a WordPress user just for the assistant, with only the permissions it needs (more on that below), and add an Application Password under Users, Profile. It worked if WordPress shows the password once; copy it then.
3. Replace the old WooCommerce entry in your client’s configuration with the adapter’s address and the new credentials. For Claude Desktop, that is the entry below. It worked if the server shows as connected after a restart.
4. Ask the assistant to list the store’s abilities. It worked if woocommerce/products-query and woocommerce/orders-query are in the list.
5. Revoke the WooCommerce REST API keys you created for the old endpoint, under WooCommerce, Settings, Advanced, REST API. It worked if nothing you still use breaks.

{
  "mcpServers": {
    "my-store": {
      "command": "npx",
      "args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
      "env": {
        "WP_API_URL": "https://yourstore.com/wp-json/mcp/mcp-adapter-default-server",
        "WP_API_USERNAME": "store-assistant",
        "WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
      }
    }
  }
}

Remote connections need HTTPS and pretty permalinks. If the client won’t connect, WordPress MCP Adapter errors and how to fix them goes through the messages you’re likely to see.

What can an AI assistant do in WooCommerce through MCP?

Query and manage products, and query and update orders. In testing, the adapter’s discovery listed eight WooCommerce abilities next to the three that WordPress core provides, and a products query through MCP returned the store’s product list. WooCommerce marks each ability with what it does to your data:

• Read only: woocommerce/products-query, woocommerce/orders-query and woocommerce/order-notes-query.
• Adds something: woocommerce/product-create and woocommerce/order-add-note.
• Marked destructive: woocommerce/product-update, woocommerce/product-delete and woocommerce/order-update-status.

Each ability runs WooCommerce’s normal permission checks for the connected user, the same ones its REST API uses. So the user you connect with decides what the assistant can actually do, whatever the client asks for. WooCommerce’s documentation still calls the MCP integration a developer preview, so expect the details to keep moving.

One thing to know before you let it create products: woocommerce/product-create publishes by default. In testing, a product created with only a name went live straight away as published; only asking for "status": "draft" kept it as a draft. Creating a product also needs the publish_products capability, so any user who can create products through MCP can publish them too.

Which store jobs should you hand to an AI assistant?

The repetitive lookups and checks that eat a store team’s day, not the decisions that reach a customer. When I ran e-commerce for a retailer that sold tools and machinery to the public and to contractors, most of the daily questions were lookups: where is this order, is that item in stock, which products are missing a description or a photo. The read-only abilities cover most of those jobs:

• Order lookups: status, notes and history for a customer who calls or emails.
• Catalogue checks: products that are out of stock, or have no price or no SKU, gathered into a list for someone to fix. WooCommerce’s product query doesn’t return descriptions, images or categories, so a check for those needs a custom ability.
• Product copy drafted for review: a short description or product text written in the conversation, which a person pastes in and publishes.

Keep these with a person: refunds, price changes, deleting products, and order status changes. In WooCommerce a status change can send the customer an email, so a wrong one is a message you can’t take back. The same goes for anything a customer sees before someone has reviewed it.

How do you connect an AI assistant to WooCommerce safely?

Give it its own user with the smallest role that covers the jobs above, because an Application Password carries every permission of its user across the whole REST API, not just the MCP endpoint. A Shop Manager can change prices, refund orders and delete products, so it is too much for an assistant that only needs to look things up.

1. Create a read-only role for the assistant with the code below, in a small plugin, and give its user that role. Tested on WordPress 7.1.3, this role could query products and orders through MCP and was refused when it tried to create a product.
2. Leave product creation off until you need it. Because WooCommerce’s create ability needs publishing rights and publishes by default, there is no role that can create products but not publish them. If you want the assistant to prepare products, a custom ability that always saves drafts is safer.
3. Use one Application Password per client and revoke it when you stop using that client. It worked if the user’s profile lists only the passwords you know about.

register_activation_hook( __FILE__, function () {
	add_role( 'store_assistant', 'Store assistant', array(
		'read'                     => true,
		'read_private_products'    => true,
		'read_private_shop_orders' => true,
	) );
} );

I walked through building a role like this, a draft-only ability, and testing what the password can and can’t do, in How to build a custom MCP server for WordPress. If you’re still deciding whether your store needs any of this, start with Should your WordPress site have an MCP server?

What do WooCommerce extension developers need to change?

Register your features as abilities with the WordPress Abilities API, and stop calling WooCommerce’s old MCP classes. According to WooCommerce’s developer blog, the old provider and transport classes still exist in 11.3 but only trigger a notice, and its own transport can no longer be passed to the adapter. To show an ability on the adapter’s default server, set 'mcp' => array( 'public' => true ) in its meta, and check that the adapter is loaded before using its classes:

if ( class_exists( 'WP\MCP\Core\McpAdapter' ) ) {
	// Register your MCP server or tools.
}

Update staging first, reconnect the assistant there, and let it run read-only for a week. You’ll learn which questions it answers well before it ever touches an order, and by then the adapter will be the only way in anyway.