If you run WooCommerce and want to know whether Claude can shop your store, the answer shipped on September 15: a new open-source repo wires Anthropic’s Claude Commerce Agent reference straight into WooCommerce’s own Store API — no Universal Commerce Protocol (UCP), no MCP, no platform migration required.

What shipped

woocommerce/agentic-tools (commit 37f8976, Apache-2.0, cloned and read directly) ports Anthropic’s commerce-agents blueprint — covered on this site when it first shipped for a fictional store — onto a real, general-purpose WooCommerce site. The repo’s own README calls it “an experimental reference implementation, not a production deployment,” with the limitations spelled out in full: no operator login on the merchant API (loopback host names stand in for authentication), in-memory demo state, and a multi-target write that can partially apply without automatic rollback.

The storefront agent reads your live Store API

The storefront agent targets any WooCommerce site whose Store API is reachable — which, per the README, “is, on every store, unless a plugin has closed it.” Reading storefront/api/store_client.py directly confirms the wire format: everything runs through wc/store/v1, the same REST namespace WooCommerce’s own Cart, Checkout and Mini-Cart blocks already use. The agent searches the catalog, walks a variable product down to its individual variations, keeps a real Store API cart under a Cart-Token, quotes shipping rates, and answers policy questions by reading the site’s own pages — there is no fixed return/warranty schema here, just a search over whatever content exists. It never calls the Store API’s /checkout route; a WordPress bridge plugin hands the cart to the shopper’s own browser session for a human to complete the order.

The merchant agent writes only what a person approves

The merchant agent reads products, orders, stock and revenue through wc/v3 and wc-analytics (confirmed in merchant/api/rest_client.py), then proposes changes — price, listing content, stock, scheduled promotions. Every proposed change lands in a ledger first; nothing reaches the store until a person calls the apply endpoint. The REST credential is loaded once, at startup, and never passes through the model or the logs.

Neither UCP nor MCP — a second protocol path, not a shared one

This matters because it’s the second major platform to run Anthropic’s blueprint, and the two implementations don’t agree on the wire. Shopify’s version of the same blueprint runs over UCP and Sign in with Shop. WooCommerce’s runs straight over its own pre-existing REST surfaces — the README never mentions UCP or MCP at all. Both satisfy the same four-operation contract (catalog, cart, order, policy) StorefrontBackend defines, the same interface this site covered in detail when Anthropic first published it. But how a backend answers those calls is diverging by platform, not converging on one protocol — worth knowing before you assume “UCP-ready” and “agent-ready” mean the same thing on every stack.

What this means for your WooCommerce store

Nothing here is a plugin you install today — the repo is explicitly a reference, not a product. But it’s a dated signal of what an agent expects from a live WooCommerce catalog, and two things are checkable right now:

  • Is your Store API actually reachable? Security plugins and some caching layers block wc/store/v1 outright. If it’s closed, this entire agent path — and anything else built on WooCommerce’s own cart blocks — has nothing to talk to.
  • Do your variable products expose complete variations? The agent walks a parent product down to its purchasable variants; a catalog with thin or missing variation data leaves the agent guessing at what’s actually in stock.

FAQ

Does Claude’s WooCommerce agent place real orders?

No. The storefront agent builds a cart against WooCommerce’s Store API and hands the shopper to the store’s own checkout page through a bridge plugin; the repo’s /checkout route is never called, and the README states directly that nothing in it “places an order, charges a card, or changes a live listing” without human action.

Does this require UCP or MCP support on my store?

No. The WooCommerce implementation talks to wc/store/v1 and wc/v3, WooCommerce’s own existing REST namespaces — the README doesn’t mention UCP or MCP anywhere. That’s a different wire protocol from Shopify’s version of the same Anthropic blueprint, which runs over UCP.

Is this a WooCommerce plugin I can install on my store?

Not yet. It’s an experimental open-source reference implementation with documented production gaps (no operator authentication, in-memory state, no automatic rollback on partial writes). It shows what a Claude shopping agent expects from a WooCommerce store’s data, not a shipped product.

Sources

  • WooCommerce, agentic-tools — root README and claude-commerce-agent/README.md, storefront/api/store_client.py, merchant/api/rest_client.py (commit 37f8976, fetched directly via git clone, Apache-2.0)
  • Anthropic, commerce-agents — the blueprint this ports, fetched directly for the earlier StorefrontBackend coverage on this site

Two independent platforms just answered “how does an agent shop here” two different ways — which is exactly why AgentReady’s transaction audit checks what your own store actually exposes, not which protocol logo it claims to support.