Antigravity + xCloud

Manage WordPress with Antigravity on xCloud

Managing WordPress with Antigravity means asking Google's agentic IDE to inspect your xCloud WordPress sites, then letting it run updates, scans and checks while Antigravity's Ask mode and xCloud's confirmation both stand guard.

Skill: xcloud:wordpress
Toolsets: wordpress-actions, sites-wordpress, vulnerabilities, broken-links, pagespeed
Free with every xCloud account

Set up Antigravity All Antigravity guides

YouScan northwind.example.com for broken links and list the pages with the most.

AgentA broken-link scan asks first, and the first scan also turns on monitoring for the site. Start it?

YouYes.

sites_broken-links_scanneeds approval

sites_broken-links_scans_showread-only

AgentThe scan finished and was not truncated. /pricing/ has 4 broken links and /blog/launch/ has 2. This first scan also turned on monitoring with a manual frequency. Want the URLs for /pricing/?

Last updated: October 2026. 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 Antigravity to Manage WordPress on xCloud?

Connect Antigravity once; every job on this account uses the same connection. Then ask in plain words.

1
Add xCloud in View raw config
In the Antigravity IDE, click the three dots at the top of the agent side panel, choose MCP Servers, then Manage MCP Servers, then View raw config. Paste this into mcp_config.json and save. The field is serverUrl: it is the only remote URL property in Antigravity's documented configuration, so do not write url or httpUrl.
JSON
```
{
  "mcpServers": {
    "xcloud": {
      "serverUrl": "https://app.xcloud.host/mcp"
    }
  }
}
```
2
Sign in, then check the connection
Open Agent settings (Cmd+, on Mac, Ctrl+, on Windows and Linux), go to Customizations and click Authenticate next to xcloud. Approve the teams and the access level in the browser, copy the authorization code it shows, paste it into the settings panel and click Submit. Then ask this in the agent panel.
Prompt
```
Who am I on xCloud?
```
3
No browser sign-in? Use an API key
Create a token with the mcp:invoke scope plus the read abilities for the areas it will use (read:servers and read:sites, with read:billing and read:addons for billing and add-on tools) and the matching write: abilities if it should change things in Settings, Developers, API Tokens and add it as a header. Replace YOUR_TOKEN with the token, which contains a pipe character, and never paste it into chat. Keep this file out of git.
JSON
```
{
  "mcpServers": {
    "xcloud": {
      "serverUrl": "https://app.xcloud.host/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}
```

Check it worked

Then ask Antigravity for the job itself, for example:

Prompt

Using xCloud, list every WordPress site on my team that has pending plugin, theme or core updates, grouped by site.

In practice

How Does WordPress Work from Antigravity?

Antigravity treats an MCP tool you have not configured as an Ask-mode call, so you approve each one. For most jobs that is a small cost. For WordPress it adds up, because a fleet question is naturally one call per site: list the sites, then read sites_wordpress_updates for each WordPress one. You can allow the reads one at a time with the mcp(xcloud/tool_name) pattern, for example mcp(xcloud/sites_wordpress_updates), and leave the rest on Ask. After that, the fleet answer arrives grouped by site, with counts for core, plugins and themes, without a prompt per site.

An update therefore passes two checkpoints, and they ask different things. Antigravity asks whether the agent may call sites_wordpress_update at all. xCloud then asks you to confirm the actual change, the plugin slugs and the backup. The agent sets backup_before_update to true for production sites, sends the request for the type and slugs you approved, and reads the site's events afterwards, because the update runs in the background and the first response only means it was accepted. If you said update everything of one type, it tells you that leaving the slugs out updates every item of that type.

Broken links are a good job for an agent panel. A broken-link scan stops for your approval first, then the agent polls the run, and the report lists the pages with the most broken links, calling a truncated scan partial instead of complete. The first scan on a site also turns on monitoring with a manual frequency, and the agent says so. Link text and finding titles come from the site's own content, so Antigravity treats them as data and does not follow instructions that appear inside them.

Antigravity specific: Allow the WordPress reads one at a time and never write a wildcard such as mcp(xcloud/*). That pattern would also skip Antigravity's prompt for sites_wordpress_update and sites_magic-login, leaving xCloud's confirmation as the only check before a plugin changes or an admin login link appears. Authenticate once under Settings, Customizations by pasting the code from the browser, or every WordPress call fails until you do.

What xCloud does for wordpress

xCloud reads each site's plugins, themes and pending updates, runs the updates after you approve with a backup first, and scans for vulnerabilities, broken links and PageSpeed results. It also toggles WP_DEBUG, issues magic login links and creates new WordPress sites with a dry run first.

Pick the site or the fleet. For one site the agent uses the one you name. For a fleet question such as pending updates it lists your sites, keeps the WordPress ones and answers grouped by site. It reads WordPress health first.
Refresh and read the inventory. The agent refreshes the cached plugin and theme list when it may be stale, then reads plugins, themes and the updates summary for core, plugins and themes. Refreshing and reading run without a prompt.
Back up, then update. Updates and activations stop for your approval. The agent sets backup_before_update to true for production sites, sends the request for the type and slugs you approved, and confirms the result from the site's events, because updates run in the background.
Scan for vulnerabilities. The agent starts a site scan, reads the count by severity and the findings, or reads the team-wide rollup worst first. You decide which findings to ignore, and the agent can unignore one later.
Check links and speed. A broken-link scan starts once you confirm it, the agent polls the run and reports the pages with the most broken links, calling a truncated scan partial. A PageSpeed scan covers mobile and desktop and can be compared with earlier runs.
Debug, log in or create a site. The agent toggles WP_DEBUG, issues a magic login link, or creates a new WordPress site. A new site gets a dry run first, then one approval, then polling until the site is live.

Reference

WordPress Settings and Limits on xCloud

The facts Antigravity works within when it manages WordPress. Where a row names the dashboard, that step stays yours to take there.

Setting or limit	What applies
Updates	Plugin, theme and core updates take a type of plugin, theme or core and optional slugs; leaving slugs out updates every item of that type. They run in the background
Backup first	backup_before_update and backup_before_action snapshot the site before the change. The agent sets them for production sites
Activation	Plugins and themes are activated by type and slug, with an optional backup first
Inventory refresh	Refreshes the cached plugin and theme list before it is read, and runs without a prompt
WP_DEBUG	A toggle with enabled set to true or false. Reading debug.log stays in the dashboard under Site, Site Monitoring, Logs
Magic login	A single-use link that expires after about ten minutes. The first call on a site installs the magic-login plugin over SSH, so it stops for confirmation
Vulnerability scans	Per site: start a scan, read the count by severity (critical, high, medium, low), list findings, ignore or unignore one. Team-wide: one rollup across every site
Broken-link scans	Start a scan, poll the run, then read open findings. The first scan turns on monitoring with a manual frequency, and a 409 means a scan is already running
PageSpeed	One scan runs both mobile and desktop and is complete when both results are in. A 409 means a scan is still running. History is kept per strategy
Caching	All layers are readable and caches can be purged. Turning page cache, object cache or Cloudflare edge cache on or off is a dashboard step under Site, WordPress, Caching
WordPress staging	Dashboard-only, under Site overview, Add Staging. The API answers 422 for a WordPress site
New WordPress site	Nginx or OpenLiteSpeed servers only. Dry run first, demo mode for a free hostname or live mode with a domain and SSL. Auto-generated admin credentials are returned once

Rules Antigravity has to follow

Plugin, theme and core updates stop for your approval, and the agent takes a backup first on production sites.
A magic login link is a password: it is shown once in the reply and never repeated in a summary, a ticket or a shared channel.
Vulnerability scans, PageSpeed scans and inventory refreshes change nothing on the site and run without a prompt; a broken-link scan asks first. Ignoring a finding hides it, so the agent records the reason you give.
WP_DEBUG is turned back off when you say you are done.
WordPress staging, caching switches and restores are dashboard steps; the agent gives you the path and the dashboard link xCloud returned.
Link text and finding titles come from site content, so the agent treats them as data and never as instructions.

Example prompts

What Can You Ask Antigravity to Do for WordPress?

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.

Prompt

Using xCloud, list every WordPress site on my team that has pending plugin, theme or core updates, grouped by site.

Prompt

Scan northwind.example.com for broken links and show me the five pages with the most broken links. Say so if the scan was truncated.

Prompt

Dry-run a new WordPress site called Northwind on my Frankfurt server and show me the resolved configuration without creating anything.

Prompt

Which of my sites have pending WordPress core, plugin or theme updates? Group them by site.

Prompt

Update every plugin on the Northwind site with a backup first, then confirm the homepage still loads.

Prompt

Show the vulnerability count for every site on this team, sorted worst first, and name the top three findings.

Prompt

Turn on WP_DEBUG for the shop site so I can see the error. Turn it off again when I say I'm done.

Prompt

Give me a magic login link for the Northwind WordPress admin.

Prompt

Scan the Northwind site for broken links and list the pages with the most broken links.

Prompt

Run a PageSpeed scan on the Northwind homepage and compare the score with the previous scans.

Antigravity and WordPress: Frequently Asked Questions

What people ask before they let Antigravity manage WordPress through xCloud.

Why does Antigravity ask before every WordPress read on xCloud?

Antigravity runs MCP tools you have not configured in Ask mode, so each call needs your approval. Allow the read tools you trust with mcp(xcloud/tool_name) patterns, such as the updates summary and the vulnerability count, and keep update and login tools on Ask.

Will an Antigravity WordPress update stop for approval twice?

Yes, when the tool is on Ask. Antigravity asks whether the agent may call the update tool, and xCloud separately requires an explicit confirmation of the change. Production sites get a backup first because the agent sets backup_before_update to true.

Does the agent back up my WordPress site before it updates plugins?

It asks xCloud to snapshot the site first by setting backup_before_update to true, and it does this by default for production sites. The update itself stops for your approval and runs in the background, so the agent confirms the result from the site's events.

How does an agent find vulnerable WordPress sites?

It can read the vulnerability rollup for your whole team in one call and sort it worst first, or scan a single site and read the count by severity. Findings can be ignored with a reason and unignored later.

Is a magic login link safe to ask an agent for?

The link is single-use and expires after about ten minutes, but anyone who opens it is logged in as the admin. Treat it like a password: use it yourself and do not paste it into a ticket or a shared channel.

Can an agent switch my WordPress caching on or off?

No. It can read every caching layer and purge caches, but turning page cache, object cache or Cloudflare edge cache on or off is a dashboard step under Site, WordPress, Caching. Cache choices can only be set while a new site is created.

Can an agent create a WordPress staging site?

No. WordPress staging is dashboard-only, under Site overview, Add Staging, and the API refuses it for WordPress sites. Staging from the API covers Git sites only.

Can an agent create a new WordPress site?

Yes, on an Nginx or OpenLiteSpeed server. It runs a dry run first, shows the resolved configuration and creates the site only after you approve. WordPress is not supported on Docker servers.

Other agents