Get the plugin
WP MCP/Integrations/Operations

Operations integration

Action Scheduler MCP

Action Scheduler is the job queue inside WooCommerce and many other plugins, and "my store emails did not send" is often a stuck queue. WP MCP adds four ops on the plugin-data pair, all through Action Scheduler's own store, logger and queue runner, never raw SQL, so the database store and the older posts store behave the same. actionscheduler-list-actions filters by hook, group, status (pending, complete, failed, canceled, running) and scheduled date, newest first, with an exact total; every email and IPv4 address in the args is masked and every token, key, password or signature is hidden. actionscheduler-get-action returns one action in full with its newest 100 log entries, which say why a run failed, secrets still hidden. Writes are off until a site opts in with the wpmcp_enable_action_scheduler_write filter. actionscheduler-cancel-action cancels one pending action and is undoable: the action is snapshotted first and a rollback queues it again, pending, on its old schedule. actionscheduler-run-action runs one pending action now through the queue runner; whatever its hook does, such as sending mail or calling a service, stays done, so it is not undoable, answers recoverable:false and needs confirm:true after a preview. Both refuse WP MCP's own hooks and run at manage_options.

plugin-data-readplugin-data-write

What your AI can do

Real Action Scheduler operations, every write reversible.

  • List queue actions by hook, group, status and date, with personal data masked
  • Read one action with its args and log entries to see why it failed
  • Cancel a pending action, undoable (opt-in)
  • Run a pending action now (opt-in, confirm:true, not undoable)

Example prompts

Example Action Scheduler prompts.

Are there failed Action Scheduler jobs from the last day, and why did they fail?

How many pending woocommerce_ actions are queued right now?

Cancel the pending action 4821; it is a duplicate.

Under the hood

The Action Scheduler calls, under the hood.

wpmcp, action-scheduler

plugin-data-read({ operation: "actionscheduler-list-actions", args: { status: "failed", per_page: 20 } }), emails, IPs and tokens masked

plugin-data-write({ operation: "actionscheduler-cancel-action", args: { action_id: 4821 } }), opt-in; snapshotted; rollback queues it again

plugin-data-write({ operation: "actionscheduler-run-action", args: { action_id: 4822 }, confirm: true }), opt-in; not undoable; recoverable:false

In the free plugin

The Action Scheduler integration is in the free plugin.

The core Action Scheduler tools ship in the free, GPL plugin with the full snapshot and undo engine, and no trial clock. Pro adds 133 more tools, including Elementor deep editing, the other page builders, the forms adapter pack and, for some integrations, extra operations. The pricing page lists what each tier includes.

Frequently asked

Action Scheduler MCP: questions, answered.

Can I undo running an action?

No. Running an action executes its hook, and what that hook did, an email sent or an API called, cannot be taken back. That is why actionscheduler-run-action answers recoverable:false and needs confirm:true. Cancelling a pending action, by contrast, is undoable: a rollback queues it again on its old schedule.

Do I need WooCommerce?

No. Action Scheduler also ships as a standalone plugin and inside many others. The ops work wherever Action Scheduler is loaded, and answer cleanly with plugin_missing or plugin_inactive where it is not.

With Action Scheduler, can the agent see customer data in job args?

Lists mask every email and IPv4 address and hide every token, key, password or signature. A single action read returns the args in full except those secret-shaped values, which stay hidden.

Point your AI at Action Scheduler.