E-commerce integration
WooPayments MCP
gateways.health is a read op on the woo-read dispatcher, listed in the woo-ops catalog. For WooPayments it reports whether the gateway is enabled and in test mode, and whether an account is connected, read from the account data WooPayments caches on the site. When an account is linked it adds the account status, whether payments are enabled, whether details are submitted, whether requirements are past due, and when the cache was last checked, in UTC. If WooPayments' own last account fetch failed, connected reads as unknown and the last error is account_fetch_failed. WooPayments webhooks arrive through its own servers, which the site cannot inspect, so their status is reported as managed. The read never calls WooPayments or its servers and never returns an account id, key, secret or token. It needs manage_woocommerce.
What your AI can do
Real WooPayments operations, every write reversible.
- See whether WooPayments is enabled and in test mode
- Check that an account is linked and payments are enabled
- See whether account details are submitted and anything is past due
- Notice when WooPayments could not fetch its account
Example prompts
Example WooPayments prompts.
Is WooPayments connected and able to take payments?
Does our WooPayments account have anything past due?
Is WooPayments still in test mode?
Under the hood
The WooPayments calls, under the hood.
woo-read({ op: "gateways.health", params: { gateway: "woocommerce_payments" } }), Pro; from the account cache; no account id
Part of WP MCP Pro
The WooPayments integration is part of WP MCP Pro.
One Pro licence unlocks the WooPayments tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.
Frequently asked
WooPayments MCP: questions, answered.
Why does the webhook status say managed?
WooPayments receives its webhooks through its own servers, not a webhook the site registers, so there is nothing on the site to inspect. The response says so rather than guessing.
Is the account status live?
It is read from the account data WooPayments itself caches on the site, with checked_at showing when that cache was fetched. WP MCP does not trigger a new fetch.
Can the agent change WooPayments settings?
Not through gateways.health, which is read only. WooCommerce Pro ops can change a gateway's non-secret settings with gateways.update, which refuses secret fields.
Related integrations
More integrations for the same agent.
MCP for Stripe
ProE-commerce, 2 tools.
MCP for PayPal Payments
ProE-commerce, 2 tools.
MCP for WooCommerce
FreeE-commerce, 9 tools.
MCP for WooCommerce Subscriptions
ProE-commerce, 3 tools.
MCP for WooCommerce Bookings
ProE-commerce, 3 tools.
MCP for WooCommerce Memberships
ProE-commerce, 3 tools.
Browse the full Integrations hub, or read more on MCP for WooCommerce and the WordPress MCP plugin.