Store coverage
Move from the question to the store result
Choose the WooCommerce surface behind the question. The package keeps each read or change attached to the store record or setting that needs attention.
28
Products, variations, taxonomy, metadata, and stock
Query products and variations, then create, update, or delete them. Query and manage categories, tags, attributes, and attribute terms by creating, updating, or deleting those records; query product metadata and update it; duplicate a product; and bulk-update stock when the intended correction is clear.
9
Orders
Query or create orders, update their status and line items, query order notes and refunds, create refunds, delete orders, and resend the order’s transactional email when needed.
4
Coupons
Query coupons before creating, updating, or deleting a coupon, so a promotion change stays attached to the record it affects.
4
Customers
Query, create, update, or delete customer records while WooCommerce remains the owner of the store data.
4
Reports
Run sales overview, product, customer, and stock reports in the relevant currency to get a bounded view for the next catalog, fulfillment, or customer decision.
15
Store and operational settings
Query store settings, tax rates and classes, shipping zones, shipping methods and classes, payment gateways, webhooks, email settings, and system status. Query system tools and run only tools explicitly allowlisted by WordPress; create, update, or delete webhooks when authorized.
11
Store infrastructure mutations
Update store settings; save or delete tax rates, shipping zones, and shipping classes; add, update, or delete shipping methods; and update payment gateways when inspection identifies a specific configuration change.
4
Product reviews
Query, create, update, or delete product reviews, keeping review maintenance connected to the product record it informs.
Operation boundaries
The useful result is controlled, not merely connected
Each operation keeps the store’s data path, permissions, workload limits, and protected surfaces explicit.
Store data path
Operations use WooCommerce CRUD and query APIs and support High-Performance Order Storage. WooCommerce remains the data owner across those storage modes.
Authorization and confirmation
Authorization is object-specific. High-impact operations require explicit confirmation before a consequential change is committed, so the result can be inspected first.
Workloads and failures
Collection and report workloads are bounded, and failures are normalized before schema validation. A failed query returns a structured failure for the next decision instead of an ambiguous result.
Outbound data
Persistent outbound URLs must use public HTTPS hosts, and webhook secrets are never returned. External actions can be reviewed without exposing a secret through the result.
Protected surfaces
Protected product metadata and system tools remain denied unless WordPress filters explicitly allowlist them. The interface does not bypass the store’s existing control point.
Dependencies
Install the runtime the package depends on
Before the first store question can be answered, the host needs these three source-owned dependencies.
WordPress 6.9 or newer
WordPress Abilities APIRegisters the WooCommerce operations through the WordPress runtime.
PHP 8.0 or newer
PHP 8.0 or newerProvides the required server runtime.
Required plugin
WooCommerceOwns the products, orders, customers, reports, settings, and store data controlled by this add-on.
Stable package
Download the stable plugin for your AI client
Download the stable MCP Abilities for WooCommerce plugin ZIP to let an AI client work with your WooCommerce store through WordPress. It returns a specific store result or targeted change while WooCommerce remains the data owner.