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.
Modern Cart abilities, governed through the Bridge
An agent can read Modern Cart's settings, discover valid setting values, check plugin and Pro status, read a summary of the current WooCommerce cart, and update or reset the cart's settings.
- Abilities
- 77 destructive
- Active installs
- 60K+
- Rating
- 98% (14 ratings)
- Version
- 1.1.0
- Requires
- WP 5.4+, PHP 7.4+
- Last updated
- 2026-09-22 5:54am GMT
View Modern Cart on WordPress.org
What has to be true first
Modern Cart and WooCommerce must both be installed and active, on WordPress 6.9 or newer for the Abilities API. Every ability checks against a single capability property on the ability class; the evidence available did not show which capability that is, though settings and status abilities are typically restricted to shop-manager-level or administrator accounts.
- WooCommerce must be installed and active; Modern Cart's own metadata declares it as a required plugin and every ability operates on WooCommerce's cart or Modern Cart's WooCommerce-specific settings.
- The plugin ships a moderncart_abilities filter that lets its own Pro add-on register extra abilities (e.g. a popup cart style), so the exact ability list can grow on a site running that add-on.
A note on the count below
Matches easymcpai's listed count of 7; verified directly from register-abilities.php and the 7 ability classes. Ids carry the 'moderncart/' namespace prefix (the base list is a static array, not dynamic, though a moderncart_abilities filter lets the Pro add-on register more). Every ability's meta.annotations uses the MCP tool-hint key names (readOnlyHint/destructiveHint) inherited from Abstract_Ability::get_annotations(), never the Abilities API's own readonly/destructive keys, so none of them present a readonly signal to the registry; per the Bridge's fail-safe rule this makes every one of the 7 abilities destructive risk, including the four that are functionally read-only.
The 7 Modern Cart abilities
Grouped by what each one can change. Every one starts off until you enable it.
Destructive 7
- Destructive
Get settings
Returns Modern Cart's current configuration, optionally scoped to one or more setting groups.
- Destructive
Update settings
Updates Modern Cart's cart, floating cart, or appearance settings.
- Destructive
Get available setting options
Returns the valid dropdown and enum values for every configurable setting.
- Destructive
Reset settings to defaults
Resets all Modern Cart settings back to their defaults.
- Destructive
Get plugin status
Returns whether Modern Cart and its Pro add-on are active and licensed.
- Destructive
Complete onboarding
Marks the Modern Cart setup wizard as completed.
- Destructive
Get cart summary
Returns a summary of the current WooCommerce cart contents.
No abilities match that search.
How to switch these on
Four steps from two active plugins to a governed connection.
Install Modern Cart and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. Modern Cart registers its own abilities; this plugin discovers and governs them.
Open the Other plugins screen
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.
Enable one ability at a time
Every ability from Modern Cart starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Connect as a least-privilege user
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.
Frequently asked questions
Does Modern Cart work with the Bridge?
Yes. Modern Cart registers 7 abilities over its own settings and cart state with real permission checks, so the Bridge can wrap and expose each one once an operator turns it on.
What has to be true for Modern Cart's abilities to register?
WooCommerce must be installed and active; Modern Cart's own metadata declares it as a required plugin and every ability operates on WooCommerce's cart or Modern Cart's WooCommerce-specific settings.. The plugin ships a moderncart_abilities filter that lets its own Pro add-on register extra abilities (e.g. a popup cart style), so the exact ability list can grow on a site running that add-on..
Does Modern Cart need anything special to work with the Bridge?
Modern Cart and WooCommerce must both be installed and active, on WordPress 6.9 or newer for the Abilities API. Every ability checks against a single capability property on the ability class; the evidence available did not show which capability that is, though settings and status abilities are typically restricted to shop-manager-level or administrator accounts.
More Ecommerce plugins
WooCommerce PayPal Payments
ConditionalAn 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.
WooCommerce Stripe Payment Gateway
ConditionalAn 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.
Verified from Modern Cart'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, Brainstorm Force or Modern Cart. Back to the full directory.
Bridge Modern Cart, keep the same control.
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.