WooCommerce MCP: choose and verify the store connection
Choose the actual WooCommerce MCP implementation, then verify authentication, discovered abilities and a product read before allowing store changes.
- Published
- Last updated
To connect WooCommerce MCP, identify the implementation installed on your store, use its matching authentication and verify a product read before allowing changes. The WordPress MCP Adapter route, WooCommerce AI and the W7S extension have different connection instructions. Their credentials and endpoints aren’t interchangeable.
Model Context Protocol (MCP) lets an AI client call store operations. An ability is an operation with defined inputs and permission checks. A successful connection establishes access to a server. It doesn’t prove that the client has retrieved the right product or can change it.
Identify the installed MCP implementation
Record the active WordPress, WooCommerce and MCP plugin versions before selecting a guide. Match the plugin name as well as the version. Keep that record with your connection configuration so a later update can be diagnosed against the implementation actually running.
The core abilities and WordPress adapter route
The WooCommerce developer guide describes core product and order abilities exposed through the WordPress MCP Adapter. It labels the implementation developer preview. WooCommerce registers abilities without a feature toggle, but the adapter must be installed separately.
WooCommerce 11.3 removes /wp-json/woocommerce/mcp. The current default-server path is /wp-json/mcp/mcp-adapter-default-server. An old tutorial using the removed path describes a different generation.
WooCommerce AI
The WooCommerce AI MCP server guide describes a separate setup. It requires WooCommerce AI and a store and user connected to WordPress.com. Under WooCommerce’s settings, open WooCommerce AI, then Advanced and MCP server. Enable Progressive MCP server and copy the generated configuration from Setup.
The generated WordPress.com connection uses OAuth. Its optional direct-store connection instead accepts a WooCommerce REST API credential through X-MCP-API-Key. Select one documented route before entering credentials.
The W7S marketplace extension
W7S MCP for WooCommerce has its own server at /wp-json/w7s-mcp/v1/mcp. Its guide requires WordPress 6.9 or later and WooCommerce 10.4 or later. It also needs an MCP Adapter, installed separately when another plugin doesn’t supply one.
The extension uses WooCommerce API keys and configurable tool packs. Its server accepts X-MCP-API-Key, while generated connector URLs carry revocable tokens. These are separate from the core adapter’s Application Password authentication.
The remaining walkthrough follows the core abilities and WordPress adapter route on a WooCommerce 11.3 test store. Use the other implementation’s linked guide if that is what your store runs.
Connect with the supported authentication
For the core adapter’s remote connection, use a dedicated WordPress user and an Application Password over HTTPS. Keep that user’s capabilities limited to the intended work. The adapter authenticates the user, and each ability checks permission when called.
- In the dedicated user’s WordPress profile, create a named Application Password. Keep the generated value in the client’s secure configuration.
- Configure the official
@automattic/mcp-wordpress-remoteproxy. SetWP_API_URLto your store’s default-server endpoint,WP_API_USERNAMEto the dedicated username andWP_API_PASSWORDto the Application Password. - Start the connection and request tool discovery. Confirm that the selected site is the intended test store.
- Execute a permitted product read and compare the result with WordPress admin.
- On an isolated test store, attempt a write that this test user isn’t authorised to perform. Expect a permission error and confirm the record remains unchanged.
WordPress’s authentication documentation explains Application Passwords. An Application Password authenticates its user. Naming it “read only” doesn’t remove that user’s write permissions. Restrict the user’s capabilities and verify the refusal.
If the negative test succeeds in changing the fixture, stop using that account for the intended read-only workflow. Correct the permissions before reconnecting. Don’t perform this permission test against a real customer order.
Verify the product and order context
Discover abilities and inspect their schemas before choosing lookup inputs. The WordPress adapter’s default-server guide describes discovery, ability information and execution as separate steps.
- Call
mcp-adapter-discover-abilities. Find the product-query ability exposed by this store. - Use
mcp-adapter-get-ability-infoto retrieve its input schema. Check the accepted filters and pagination fields. - Execute the selected ability through
mcp-adapter-execute-ability, using only schema-supported inputs. - Compare the returned product with the same record in admin before presenting its details to a shopper or support agent.
For a fictional lookup, the requested item is a navy jacket, SKU JACKET-NAVY-M. Use that SKU filter if the discovered schema supports it. Otherwise, narrow the search using supported fields and inspect the returned records. Match the product ID and variation attributes before answering about stock or price.
A parent jacket record and its medium navy variation are different records. An incorrect answer takes the parent’s general availability as proof that this variation is in stock. The correct answer uses the matched variation’s returned stock field.
Follow the response’s pagination information until the bounded search is complete. A missing item on the first page doesn’t establish that the catalogue lacks it. Keep the search limited to this product instead of downloading the entire catalogue.
Treat order and customer records as private support information. A public product lookup doesn’t justify retrieving them. For an authorised order enquiry, compare the order’s customer reference with the verified customer and match its line-item variation to the product. Order status and product stock answer different questions.
Handle failures and potential changes
Diagnose a connection failure against the chosen implementation before changing credentials. The core guide documents HTTP 410 for its removed WooCommerce endpoint. Switching password types won’t restore that route.
| Symptom | Check | Next action |
|---|---|---|
| Old core endpoint returns 410 | Compare the configured path with the installed version | Move to the documented adapter route |
| Server or ability missing | Check adapter activation and discovered abilities | Correct the installation or exposure before requesting broader access |
| Permission refused | Compare the authenticated user’s capabilities with the selected ability | Use the required authorised account for that task |
| Previously working credential fails | Check whether that specific credential remains active | Replace the revoked credential through its own implementation’s setup |
For the core route, revoke an unused Application Password from its user profile. In W7S, Revoke key removes the key and its connector URL. Disconnect URL removes only that URL, leaving header-based access possible. Confirm a fresh request is refused after revocation.
For a supported product update, first read the current record and inspect the discovered update schema. Prepare the exact product ID and the proposed field value for approval. A fictional test could change a test product’s description from “Navy jacket” to “Navy cotton jacket”.
After an authorised update on that test store, retrieve the product again and reload its admin page. Confirm the saved description matches the approved value and the product ID is unchanged. If the write times out, read the record before retrying: the first request might already have saved it.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.