ChatGPT + xCloud
Back up and stage sites with ChatGPT on xCloud
Backing up and staging sites with ChatGPT means asking OpenAI's assistant, through the developer-mode app that points at xCloud, to report on your backups, start one before a change and request a staging copy, all inside a chat.
- Skill: xcloud:sites
- Toolsets: sites
- Free with every xCloud account
YouUsing the xcloud app, which sites have no backup schedule? Then back up the shop.
sites_backupSettingsread-only
AgentTwo of seven sites have no schedule: blog.example.com and docs.example.com. The shop has a daily schedule and its last backup completed 22 hours ago. I will start a new one for the shop.
sites_backup
AgentThe backup is completed and stored locally. To restore it later, use Site > Site Backup > Previous Backups > Restore in the xCloud dashboard.
. Keep a human in the loop: xCloud stops and asks before anything that creates, deploys, updates, reboots, deletes or buys.
Setup
How Do You Set Up ChatGPT to Back up and stage sites on xCloud?
Connect ChatGPT once; every job on this account uses the same connection. Then ask in plain words.
Turn on developer mode and open Plugins
In ChatGPT on the web, open Settings, Security and login and turn on Developer mode. Then open the Plugins page and select the plus button to create an app. OpenAI lists developer mode for Pro, Plus, Business, Enterprise and Education accounts on the web, but its help center puts full MCP support with write actions in beta on Business, Enterprise and Edu workspaces and gives Pro accounts read and fetch access only, so check your plan before you expect ChatGPT to deploy or update anything. That path is for a personal account. In a Business, Enterprise or Edu workspace the controls sit under Apps instead. On Business only an admin or owner can use Developer mode: they turn it on while creating the app from Workspace settings, Apps, Create, and publish it from Workspace settings, Apps. On Enterprise and Edu an admin or owner can also toggle Developer mode under Settings, Apps, Advanced settings, and a member granted developer access under Permissions and Roles turns it on there too and can create and test the app from their own Settings, Apps, Create, but only an admin or owner can publish it. An ordinary member cannot do this, so ask an admin to publish the xcloud app; then open Settings, Plugins, select xcloud, install it if offered and choose Connect, sign in to xCloud and pick the teams and access level, and only then start at the last step.
https://chatgpt.com/pluginsCreate the app with the xCloud MCP URL
Name the app xcloud, paste this as the MCP server URL and choose OAuth for authentication. xCloud supports dynamic client registration, so you do not need to create a client ID. Sign in with xCloud when the browser asks, tick the teams and choose Read-only or Full access.
https://app.xcloud.host/mcpInstall the plugin and use it in a Work chat
Open your personal Plugins page, open xcloud and select the plus button to install it. Back on the ChatGPT homepage, switch the tab at the top from Chat to Work, start a new Work chat, type @ and pick xcloud; a plain Chat tab conversation does not offer the plugin. Then type a request like this one.
Using the xcloud app, who am I on xCloud and which servers do I have?Check it worked
Then ask ChatGPT for the job itself, for example:
Using the xcloud app, list my sites that have no backup schedule and show when each last backed up.
In practice
How Does Backups and staging Work from ChatGPT?
ChatGPT is the place you ask when you do not want to open a dashboard at all. You pick the xcloud plugin for the conversation with @xcloud in a Work chat, then ask in ordinary language: which of my sites have no backup, and when did the shop last back up? ChatGPT calls the xCloud read operations for each site, works out which are native sites and which are Docker apps, and answers with a list or a table of schedule, last backup, result and storage. Mention the app in the first message, for example using the xcloud app, so ChatGPT does not answer from general knowledge instead of from your account.
Starting a backup is where ChatGPT's own rules show. xCloud runs a backup without a confirmation, but OpenAI's developer mode asks you to confirm write actions by default, so you may see a ChatGPT confirmation card before the backup starts. Read it, because it names the tool and the site. ChatGPT tells you first that a Docker app is stopped briefly while its volumes are captured, then reports completed or failed once it has read the result. Starting a backup is a change, so it also needs the Full access level on the xCloud approval screen. If you approved Read-only, ChatGPT can still answer every backup question but will explain that it cannot start one.
Staging and restores are conversations about boundaries. ChatGPT has no repository, so for a Laravel, Node.js, custom PHP or Lovable site you name the branch, ChatGPT restates the site and branch and you confirm the staging creation, which needs a paid plan. For a restore, a native schedule change, a storage provider or WordPress staging, ChatGPT does not try a workaround. It gives you the dashboard path and the site link, such as Site > Site Backup > Previous Backups > Restore, and you finish there. Because developer mode is marked as higher risk by OpenAI, it is worth keeping the connection on Read-only until you actually want ChatGPT to take a backup.
ChatGPT specific: ChatGPT connects from OpenAI's servers, and OpenAI's help center puts write actions on Business, Enterprise and Edu workspaces, with Pro accounts on read and fetch access only, so starting a backup from ChatGPT needs one of those plans as well as Full access on the xCloud approval screen. A backup start may show a ChatGPT confirmation even though xCloud asks nothing. Check the app under Drafts in ChatGPT's settings if the backup tools do not appear.
What xCloud does for backups and staging
xCloud lets the agent read every site's backup state, start a backup on demand for native and Docker sites, and create a staging environment for Git sites. Restores, storage providers and WordPress staging stay in the dashboard, and the agent tells you the exact path when you ask for one.
- Find the site. The agent resolves the site by name or domain, restates which one it is about to act on, and reads whether it is a native site or a Docker app, because the two use different backup operations.
- Read the protection state. It reads the backup settings, status, count and recent backups. That answers whether the site has a schedule, when the last backup ran, whether it succeeded and where it is stored, before anything is changed.
- Back up now. A backup starts without an approval prompt. A native site takes a local backup by default or a remote one when a storage provider is connected. A Docker app is stopped briefly while its volumes are captured, so the agent says so before it backs up a production app.
- Wait for the result. xCloud queues the backup and returns straight away. The agent follows the backup task or row until it is terminal, then reports completed or failed instead of treating the queued response as done.
- Stage the change. For a Git site such as Laravel, Node.js, custom PHP or Lovable, the agent creates a staging environment from the branch you name, after you approve, and gives you its URL. A WordPress staging site is a dashboard step, and the agent gives you the path.
- Hand off restores and settings. If you ask to restore a backup, change a native site's schedule or add a storage provider, the agent explains that these are dashboard-only and gives the path and the site's dashboard link. It never improvises a workaround.
Reference
Backups and staging Settings and Limits on xCloud
The facts ChatGPT works within when it backs up and stage sites. Where a row names the dashboard, that step stays yours to take there.
| Setting or limit | What applies |
|---|---|
| Native site backup | On demand through the API; the type is local (the default) or remote. A remote backup needs a storage provider with a working connection, otherwise xCloud refuses it with a 422 before anything is queued |
| Docker app backup | On demand through the API for Compose deploys and most one-click apps. The app is cold-stopped for a moment while volumes are captured. A remote copy goes to an S3-compatible or SFTP provider; Google Drive and pCloud are not supported for Docker apps |
| Reading backups | Backup list, count, status and settings are readable for every site. Docker apps also expose one backup's detail |
| Docker backup housekeeping | The agent can label a Docker backup with a note and delete one. Deleting is irreversible, so it names the exact backup by date and note first |
| Native schedule and retention | Read-only through the API. Change them in the dashboard under Site > Site Backup > Backup Settings |
| Docker backup settings | Writable through the API: automatic backup on or off, daily, weekly or monthly frequency, and the number of days to keep backups |
| Restores | Dashboard-only for every site type: Site > Site Backup > Previous Backups > Restore. A backup can also be restored to another site from the same page |
| Storage providers | Dashboard-only, under Integrations > Storage Provider. Backup settings return a provider's identifier and status, never its credentials |
| Team-wide backup policy | Applying one backup policy to many sites is dashboard-only, under Global Settings > Site Backup |
| Git staging | Created through the API for Git sites on paid plans. On the free plan xCloud answers 403 because it is a plan limit, not a permission |
| WordPress staging | Dashboard-only: xCloud answers 422 when the API is asked for it. Push and pull between staging and production also happen in the dashboard |
| Snapshots | Snapshots are listed per site. The server-wide snapshot list holds site snapshots, not a server image. Taking or restoring a snapshot, and a whole-server provider backup, stay in the dashboard |
Rules ChatGPT has to follow
- A backup runs without an approval prompt, but the agent says when it briefly stops a Docker app and does not trigger one on a busy production app without telling you.
- A queued backup is not a finished backup: the agent reports completed or failed only after it has read the result.
- Restoring a backup, changing a native site's schedule, adding a storage provider and creating WordPress staging are dashboard steps; the agent gives you the path instead of guessing an operation.
- Creating a staging environment stops for your approval, and deleting a backup names the exact backup first.
- Before you push staging data to production in the dashboard, take a backup of the production site so you can recover if the push goes wrong.
Example prompts
What Can You Ask ChatGPT to Do for Backups and staging?
Type these as written and swap in your own repository, site and server names. Reads and routine actions such as backups, cache purges, PageSpeed scans and vulnerability scans run straight away; creating, deploying, updating, rebooting, deleting, buying or starting a broken-link scan stops and asks first.
Using the xcloud app, list my sites that have no backup schedule and show when each last backed up.Using the xcloud app, take a backup of shop.example.com now because a developer is deploying this afternoon, and tell me when it has finished.Using the xcloud app, create a staging environment for the API site from the feature/checkout branch. Tell me what you will create first.When was the last backup of the shop site, did it succeed, and where is it stored?Check the backup settings on every site and list the ones with no schedule.Take a backup of the n8n Docker app now, before I upgrade it, and tell me when it is done.Switch the n8n Docker app to a daily backup and keep backups for 14 days. Show me the change before you apply it.Create a staging environment for the API site from the feature/checkout branch and give me its URL.List the snapshots of the shop site and tell me which is newest.I need to restore the shop site to last night's backup. Tell me where to click.ChatGPT and Backups and staging: Frequently Asked Questions
What people ask before they let ChatGPT back up and stage sites through xCloud.
Why does ChatGPT ask me to confirm a backup on xCloud?
xCloud starts a backup without a prompt, but ChatGPT's developer mode asks you to confirm write actions by default. That confirmation comes from ChatGPT, not from xCloud. Read the tool name and the site in the card before you accept it.
Can ChatGPT create a staging site for WordPress?
No. WordPress staging is a dashboard step, because xCloud does not offer it through the API. ChatGPT can create a staging environment for a Laravel, Node.js, custom PHP or Lovable site on a paid plan, after you approve it in the chat.
Can an AI agent restore a backup for me?
No. Restoring a native or Docker backup is a dashboard step, under Site > Site Backup > Previous Backups > Restore. The agent can list the backups, tell you which one is newest and completed, and give you the site's dashboard link so you can start the restore yourself.
Does the agent ask before it takes a backup?
No. A backup is a routine action, so xCloud runs it without a confirmation prompt. For a Docker app the agent tells you first that the app stops briefly while its data is captured, and it reports the result only after the backup has finished.
Can the agent change my backup schedule?
For Docker apps, yes: it can turn automatic backups on or off, set daily, weekly or monthly, and set how many days backups are kept. For native sites the schedule, retention and destination are read-only through the API, so you change them in the dashboard under Site > Site Backup > Backup Settings.
Can the agent connect my S3 bucket or other storage?
No. Storage providers are added in the dashboard, under Integrations > Storage Provider, so credentials never pass through a chat. Once a provider exists, the agent can read which one a site's backup settings point at and use it for a remote backup.
Can the agent create a staging site for WordPress?
Not through the API. xCloud answers 422 for WordPress staging, so you create it in the dashboard from the site overview. For Laravel, Node.js, custom PHP and Lovable sites the agent can create a staging environment, which needs a paid plan.
Other agents
Backups and staging with Other Agents
The same job, the same xCloud tools, a guide for each client.
- Back up and stage sites with Claude CodeAnthropic's terminal coding agent. One claude mcp add command, plus the xCloud skills plugin with nine skills on top.
- Back up and stage sites with ClaudeAnthropic's chat assistant on the web and desktop. Add xCloud as a custom connector, no terminal needed.
- Back up and stage sites with Claude CoworkAnthropic's desktop agent for delegated work. Add the xCloud connector, then hand off hosting jobs.
- Back up and stage sites with CursorThe AI code editor. One mcp.json entry with the compact URL, because Cursor stops at 40 tools.
- Back up and stage sites with CodexOpenAI's coding agent for the terminal. A codex mcp add command or a config.toml entry, then codex mcp login.
- Back up and stage sites with OpenCodeThe open-source terminal coding agent. One remote MCP entry, then opencode mcp auth xcloud.
- Back up and stage sites with Hermes AgentNous Research's agent with memory and a built-in scheduler. An mcp_servers entry in config.yaml and one login.
- Back up and stage sites with OpenClawThe open-source agent runtime with chat apps and automations. ClawHub skill plus the MCP client.
- Back up and stage sites with WindsurfThe Cognition editor, now Devin Desktop. devin mcp add for the Devin Local agent, a serverUrl entry for legacy Cascade.
- Back up and stage sites with GitHub CopilotCopilot agent mode in VS Code. One .vscode/mcp.json entry, or the Agent Plugins package.
- Back up and stage sites with Gemini CLIGoogle's terminal agent. One gemini mcp add command, OAuth found automatically.
- Back up and stage sites with ChatGPT dotsOpenAI's always-on agent in ChatGPT. Uses the xCloud MCP plugin you add in ChatGPT, with custom rules and scheduled tasks.
- Back up and stage sites with GrokxAI's terminal agent, Grok Build. One grok mcp add command or a config.toml entry.
- Back up and stage sites with Grok BotxAI's always-on Bots on a cloud computer. One Remote HTTPS MCP plugin, OAuth sign-in, routines on a schedule.
- Back up and stage sites with KiroAWS's agentic IDE. One url entry in .kiro/settings/mcp.json, plus the portable xCloud Agent Plugins package.
- Back up and stage sites with AntigravityGoogle's agentic IDE. One serverUrl entry in mcp_config.json and a browser sign-in.
- Back up and stage sites with ZedThe Zed editor's Agent Panel. One context_servers entry in settings.json and a browser sign-in.
More ChatGPT guides
- ChatGPT and xCloud overview
- Deploy from Git with ChatGPT
- Run Docker apps with ChatGPT
- Install one-click apps with ChatGPT
- Manage WordPress with ChatGPT
- Manage SSL and domains with ChatGPT
- Manage servers with ChatGPT
- Troubleshoot a broken site with ChatGPT
- Speed up a slow site with ChatGPT
- Secure sites and servers with ChatGPT
Run Your Hosting from ChatGPT
xCloud MCP, the Agent Skills and the Public API are free with every account. Connect once and ask.