Museder RestoreOne vs SiteSkite MCP AI – Connector for Claude, ChatGPT, Cursor & WordPress WebOps

Museder RestoreOne lets you create complete WordPress backups (database + wp-content) as a single archive, and restore them in a guided 3-step wizard. It is designed for shared hosting environments and uses WordPress APIs for database backup/restore, with archive compression handled by ZipArchive or WordPress’ bundled PclZip. Key features One-click full-site backup Export the database, meta.json, and wp-content/ into a single archive you can download or restore later. Restore Center wizard A clear 3-step flow: upload & analyze → review summary & options → start restore with real-time progress and logs. Chunked uploads with validation Bypass upload_max_filesize / post_max_size limits by uploading your archive in small chunks, with retries and integrity checks. Shared-hosting friendly Uses pure PHP + WordPress APIs for database backup/restore, and falls back from ZipArchive to PclZip compression when needed. Schedules and logs Create one or more automatic backup schedules (or run backups manually), then inspect, download, or clean up structured backup and restore logs. Neo-glass admin UI Modern Dashboard, Backups, Restore, Schedules, Logs and Settings screens with clear calls-to-action, status messages, and responsive layout. Multisite This release is not formally tested on WordPress Multisite. For predictable results, use RestoreOne on standard single-site installs (one site per admin context). If you run a network, treat use as experimental until you have verified backups and restores on a staging clone. External services This plugin does not use external services. The only programmatic outbound HTTP the base plugin performs by default is an optional, short non-blocking request to your own site’s wp-cron.php (same host / local loopback) to encourage scheduled tasks to run. No third-party API is called for backups or restores. All admin JavaScript and CSS for RestoreOne are loaded from files shipped under this plugin’s assets/ directory (including vendored libraries under assets/vendor/). Optional add-ons, if you install them separately, may introduce their own network behavior; see each add-on’s readme. See the FAQ for more on the local wp-cron.php nudge. Privacy What this plugin stores on your server Backups — Complete-site archives are written under your WordPress uploads area (typically wp-content/uploads/museder-restoreone/backups/ or the path shown on the Backups screen). Each archive contains a database export (database.ndjson), meta.json, and a copy of wp-content/ from your site at backup time. Logs — Text logs for backup, restore, and related operations are stored under wp-content/uploads/museder-restoreone/logs/ (see the Logs admin screen). Restore reports — When you generate a restore report, files are stored under wp-content/uploads/museder-restoreone/reports/ (or the path configured for reports on your install). Schedules and settings — Options and scheduled events are stored in your WordPress database like other plugins. Diagnostics Version / build heartbeat — After an upgrade, the plugin may write a one-line informational entry to the local Logs directory (same server, no remote host) noting the active plugin version and build id. This is for support troubleshooting only. Exact folder names may vary with your uploads path or custom content directory; nothing is sent to a fixed external hostname by this plugin. The plugin resolves these locations using WordPress APIs (for example wp_upload_dir() and path helpers derived from your install) rather than hard-coded internal constants, so custom wp-content or uploads layouts can be reflected correctly where your host allows. Third parties The free plugin does not upload your backup contents, database, or logs to third-party APIs or clouds. That statement matches External services above and the FAQ entries on external data and local wp-cron loopback. Optional add-ons (separate plugins or extensions, if you install and activate them) could send specific categories of data to remote storage or services only when you enable and configure those extensions; the base RestoreOne plugin does not do that on its own. Retention and deletion You can delete backup archives from the Backups screen, remove or download logs from Logs, and adjust retention-related options where provided. Uninstall (uninstall.php) removes plugin-owned options, transients (including timeout rows), dynamic job-lock option rows, and scheduled cron hooks whose names start with museder_restoreone_. It does not delete backup ZIP archives, log files, restore reports, or other files under your uploads/storage tree; delete those manually from the Backups / Logs UI or your host if you no longer need them. On Multisite, uninstall walks sites in batches (100 IDs per query) instead of loading the entire network at once. Very large networks should still use a maintenance window so uninstall is not interrupted by web-server timeouts. Developer Development source of truth is the public GitHub repository: https://github.com/artherslin-source/museder-restoreone Contributors and release maintainers should follow the Modification & Release SOP (docs/SOP-PLUGIN-DEVELOPMENT-AND-RELEASE.md in the repo). Summary: Branching: work on fix/, feature/, or agent/ branches from current main; avoid long-lived dirty main. WordPress.org Lite: fully functional, GPL, no license gates, trialware, or bundled Add-on/PRO code in the Lite package or SVN. Security: every sensitive AJAX/REST/form handler needs capability checks, nonces, sanitize/validate input, and escaped output. Release version sync (six fields, same version): museder-restoreone.php Version, MUSEDER_RESTOREONE_VERSION, MUSEDER_RESTOREONE_BUILD_ID, readme.txt Stable tag, new Changelog block, and new Upgrade Notice block (easy to forget — WP.org shows the notice to updaters). Package Lite ZIP: use create-package.sh or tools/package-lite-windows.ps1 only; require BOUNDARY_CHECK=PASS. Do not use PowerShell Compress-Archive. Lite ZIP must not include docs/, tools/, .cursor/, .github/, logs/, or museder-restoreone-pro/. GitHub release: after explicit approval, tag vX.Y.Z on main; GitHub Actions builds release artifacts. WordPress.org SVN: commit Lite source files only (no zip); copy trunk to tags/X.Y.Z; fill docs/RELEASE-X.Y.Z-SVN-HANDOFF.md from the template before SVN commit. Checklists: docs/RELEASE_CHECKLIST.md, docs/PACKAGING.md, docs/WORDPRESS_ORG_DEVELOPMENT_GUIDE.md, AGENTS.md.

SiteSkite is a WebOps for WordPress built for agencies, developers, and site owners who manage one site or many. Connect your sites for backups, updates, monitoring, sandboxes, and team workflows — and, with SiteSkite AI, edit a live WordPress site using assistants like Claude, ChatGPT, and Cursor. Live on-site edits with WordPress AI do not use SiteSkite AI Site Studio credits. Whether you manage 1 site or 100+, SiteSkite simplifies WordPress maintenance and scales with your workflow. Important: SiteSkite only manages your website after you connect it with a secure API key. Plugin installs, activations, and maintenance actions are initiated from your SiteSkite account so you stay in control. What SiteSkite Helps You Do ✔️ Manage multiple WordPress sites from one dashboard ✔️ Automate backups and restore anytime ✔️ Edit live sites with AI (Claude, ChatGPT, Cursor) via SiteSkite MCP ✔️ Choose Off, WordPress AI, or Platform AI per linked site ✔️ Create pages, menus, forms, and page-builder layouts with WordPress AI ✔️ Privacy-minded SiteSkite AI Chat for portal workflows ✔️ Advanced Site Recovery: keep working even after many fatal errors ✔️ Snapshot and incremental backups ✔️ Create blueprints for rapid deployment ✔️ Launch sandbox sites ✔️ Spin up new sites from existing backups (on SiteSkite servers) ✔️ Store backups in your own cloud (bring your own storage) ✔️ Vulnerability detection guard ✔️ Monitor uptime and site health across all sites ✔️ Bulk update, activate, deactivate, and delete plugins/themes ✔️ Roll back plugin and theme versions safely ✔️ Add team members and organize sites into workspaces ✔️ WP Canvas tools (maintenance mode, debug, search & replace, indexing, WP Reset, and more) ✔️ Manage WP admin users and roles ✔️ Track Core Web Vitals performance ✔️ Install curated plugin presets with WP Essentials ✔️ White-label the plugin for agency clients ✔️ Automated reports for your customers ✔️ Clear views for error, debug, and custom logs ✔️ and much more… Built to simplify workflows and scale your WordPress operations without stress. Get started in minutes. SiteSkite AI & MCP (new in 2.1.0) Connect once at https://mcp.siteskite.com, sign in with your SiteSkite account, and use Quick Connect for Claude or ChatGPT (Cursor and other clients supported too). This gives your assistant the whole platform — every connected site, plus backups, sandboxes, and logs. No account? SiteSkite MCP is free to use without one. Open SiteSkite → AI MCP → Connect in wp-admin and connect Claude, ChatGPT, or Cursor straight to this one site. No sign-up, no API key, nothing metered. You approve each app in your own WordPress admin and can cut it off there at any time. Sign in later and the same connector gains the platform tools and the rest of your sites. Per site, pick how AI works: – Off — AI will not change that site – WordPress AI — edit the live website (pages, menus, forms, Gutenberg, Elementor, WPBakery, and more) – Platform AI — SiteSkite portal tools (backups, sandboxes, AI Site Studio, and more) Only one mode can be active at a time. With WordPress AI you can: – Create, edit, and publish pages – Install and toggle plugins – Edit with the WordPress block editor (keep the Block Editor Queue page open while the assistant works) – Build Elementor and WPBakery layouts – Manage menus and add images from a URL – List forms and create Contact Form 7 forms You stay in control: – Turn individual AI actions on or off in Abilities – Switch Advanced Power Tools off if you would rather withhold deeper server-side actions (PHP, WP-CLI, files) – Add site notes in Context so the AI follows your preferences – Use Skills (ready-made playbooks) for Gutenberg, Elementor, WPBakery, and more Key Features Backups, Restore, Site Migrate/Clone Stay in control of your site backups: – On-demand, daily, or weekly backups – Full, database-only, or file-only backups – Incremental backups (resource-efficient) – Classic snapshot backups (full archive) – Restore with a click – Migrate or clone a site from Server A to Server B BYO Cloud Storage Use your own cloud storage, including: – Google Drive – Dropbox – AWS S3 – Backblaze B2 – pCloud Bring your own AI model Use your preferred AI where the platform supports it: – ChatGPT – Claude – Other supported models Connect Claude, ChatGPT & Cursor (MCP) One SiteSkite connection for everyday use Quick Connect for Claude and ChatGPT WordPress AI for live site edits; Platform AI for portal tools No per-site config files required for normal users Free to use, and works without a SiteSkite account if you only want the AI connector Bulk WordPress Actions Update plugins, themes, and core Activate, deactivate, or delete plugins and themes Rollback plugin and theme versions Install bulk plugins from presets Built-in Native Features Maintenance Mode WP Debug Search & Replace Permalink settings WP Reset Site indexing toggle Performance & Monitoring Uptime monitoring BirdEye status overview Core Web Vitals metrics Collaboration & Scaling Workspaces to group sites and clients Add users, team members, and clients White-label plugin branding Marketplace Browse tools, presets, and digital assets Wishlist and follow sellers 1GB free space Enjoy free cloud storage for your site backups Learn More Website: SiteSkite.com Documentation: Knowledgebase Who is SiteSkite for? WordPress website owners Agencies managing client sites Freelancers and developers Hosting providers offering WP upkeep Anyone who wants peace of mind and automation External services This plugin connects to external services to perform backups, restores, and operational callbacks. Below is a list of services, what they are used for, what data is sent, and relevant policies. Dropbox What it’s used for: Uploading and downloading backup archives to the site owner’s Dropbox. What data is sent and when: Backup file contents and related metadata (e.g., file name and size) during backup and restore operations initiated by the administrator. Endpoints: https://content.dropboxapi.com, https://api.dropboxapi.com Policies: Terms https://www.dropbox.com/terms · Privacy https://www.dropbox.com/privacy Google Drive What it’s used for: Uploading and downloading backup archives to the site owner’s Google Drive. What data is sent and when: Backup file contents and related metadata during backup and restore operations initiated by the administrator. Endpoints: https://www.googleapis.com/drive/v3/files and related upload endpoints such as https://www.googleapis.com/upload/drive/v3/files (resumable/multipart uploads). Policies: Terms https://policies.google.com/terms · Privacy https://policies.google.com/privacy Amazon S3 What it’s used for: Uploading and downloading backup archives to the site owner’s Amazon S3 bucket. What data is sent and when: Backup file contents and related metadata during backup and restore operations initiated by the administrator. Endpoints: Region-specific S3 REST API (e.g., https://s3. .amazonaws.com). Policies: Service Terms https://aws.amazon.com/service-terms/ · Privacy https://aws.amazon.com/privacy/ Backblaze B2 What it’s used for: Uploading and downloading backup archives to the site owner’s Backblaze B2 bucket. What data is sent and when: Backup file contents and related metadata during backup and restore operations initiated by the administrator. Endpoints: Backblaze B2 API (e.g., https://api.backblazeb2.com). Policies: Terms https://www.backblaze.com/company/legal/terms.html · Privacy https://www.backblaze.com/company/privacy.html pCloud What it’s used for: Uploading and downloading backup archives to the site owner’s pCloud storage. What data is sent and when: Backup file contents and related metadata during backup and restore operations initiated by the administrator. Endpoints: pCloud API (e.g., https://api.pcloud.com) and regional variants such as https://eapi.pcloud.com (EU) and https://asiaapi.pcloud.com (Asia). OAuth token exchange: https://my.pcloud.com/oauth2_token. Policies: Terms https://www.pcloud.com/terms.html · Privacy https://www.pcloud.com/privacy-policy.html SiteSkite endpoints (operational callbacks and validation) What it’s used for: Validating the plugin API key, linking a site, downloading managed assets, and sending operational status callbacks to SiteSkite services. Some staging endpoints may be used for validation or asset download during testing. When AI / MCP features are used, the SiteSkite platform may coordinate ability requests to this linked site using your Connect API key. What data is sent and when: Site identifier and operation status metadata (e.g., backup/restore status) during validation and callbacks. For asset downloads, only the requested asset path is transmitted. Backup contents are never sent to SiteSkite; only selected metadata required to coordinate operations. Policies: Terms https://www.siteskite.com/terms-of-service · Privacy https://www.siteskite.com/privacy-policy WordPress.org (downloads) What it’s used for: Downloading official WordPress core translation files when requested by an administrator. What data is sent and when: The request URL includes the WordPress core version and language code to retrieve the matching translation archive; no personal data is sent. Endpoints: https://downloads.wordpress.org/translation/core/ / .zip Policies: Terms https://wordpress.org/about/privacy/ · Privacy https://wordpress.org/about/privacy/ Notes: – Data is transmitted only when you initiate an action that requires it (e.g., starting a backup/restore, validating your API key, or downloading translations). – You choose and configure the cloud storage provider(s) to be used.