An agent can list, create, update, and delete WooCommerce products, and list orders, add order notes, or change an order's status, all through the same REST layer as the wc/v3 API.
View WooCommerce on WordPress.org
WooCommerce must be installed and active on WordPress 6.9 or later (this build lists 7.0 as its own minimum). Every ability is wrapped around WooCommerce's REST controllers, so it is gated by the same REST-key permission check WooCommerce's own Products and Orders endpoints use, and updating a product also checks the 'publish_products' capability.
Beyond what the Bridge discovers here, Agent Abilities for MCP also maintains its own built-in integration for WooCommerce, which we build and keep up to date ourselves rather than read from WooCommerce's code. See the built-in WooCommerce abilities.
WooCommerce ships 7 core ability definition classes (products and orders). easymcp's count of 9 may include two extension-registered abilities from the 'woocommerce_ability_definition_classes' filter that are not part of WooCommerce core itself.
Grouped by what each one can change. Every one starts off until you enable it.
Lists WooCommerce orders via the wc/v3 Orders REST endpoint.
Lists WooCommerce products via the wc/v3 Products REST endpoint.
Adds a note to a WooCommerce order.
Creates a new WooCommerce product.
Changes a WooCommerce order's status.
Deletes a WooCommerce product.
Updates an existing WooCommerce product.
No abilities match that search.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. WooCommerce registers its own abilities; this plugin discovers and governs them.
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Every ability from WooCommerce starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Yes. The seven core commerce abilities register unconditionally on the Abilities API init hook once WooCommerce is active, so the Bridge can discover and enable all of them.
Yes, unconditionally, once WooCommerce is active. Nothing else has to be configured for the Bridge to discover them.
WooCommerce must be installed and active on WordPress 6.9 or later (this build lists 7.0 as its own minimum). Every ability is wrapped around WooCommerce's REST controllers, so it is gated by the same REST-key permission check WooCommerce's own Products and Orders endpoints use, and updating a product also checks the 'publish_products' capability.
An agent can check whether the store's PayPal account is connected, list configured payment methods, and look up a PayPal order's captures, refunds and shipment tracking, all read-only, once WooCommerce and the plugin's ability feature flag are both enabled.
An agent can pull the connected Stripe account's status and balance, and read charges, payment intents, disputes, payouts and balance transactions by ID or as lists, all read-only, once WooCommerce and the plugin's ability feature flag are both enabled.
An agent can read the abandonment and recovery dashboard stats, see which products get abandoned most, look up one configuration setting by key or label, list every configurable setting, and update a single setting's value.
Verified from WooCommerce's own free wordpress.org code on 28 September 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, Automattic or WooCommerce. Back to the full directory.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.