mainwp-backups category. Use them to manage MainWP Built-In Backups through the WordPress Abilities API or the MainWP MCP Server.
Prerequisites
- MainWP Dashboard 6.4 or later and the matching MainWP Child release
- WordPress 6.9 or later on the Dashboard
- An authenticated Dashboard user with access to the requested sites and the required backup permissions
- Built-in backups enabled for backup creation and restores
Discover the Available Schemas
List the category to retrieve each ability’s input schema, output schema, and execution instructions:Read Backup Status
Read abilities useGET. Pass input as a JSON-encoded input query parameter when needed:
Preview and Confirm Changes
Write abilities usePOST and require either dry_run: true to preview or confirm: true to execute. Preview the action, review its affected sites, destinations, retention deletions, and warnings, then confirm the same selection. Do not set both flags to true.
For example, preview an on-demand full backup:
not_started, no work was queued; retry later. An already_running result attaches to an existing run, so poll it rather than starting another.
Edit destination credentials, hosts, buckets, and paths in Backups > Storage (
/wp-admin/admin.php?page=ManageBackupsStorage). Configure encryption and the recovery passphrase in Backup Settings.
Permissions and Restore Results
Abilities enforce the user’s site access, task ownership, and operation permissions. Storage changes require an account with access to all sites. Reading or changing global backup settings requires the corresponding Dashboard settings permissions. Before confirming a restore, review the preview’s replacement and WooCommerce warnings. After starting it, pollmainwp/get-restore-job-v1 and inspect outcome, partial_state_risk, and verification. A cancellation request may still be pending; keep polling until the site confirms it stopped. Rollback requires an available safety backup from the original restore.
For restore precautions and recovery options, see Restore a Snapshot.