Antigravity + xCloud

Manage servers with Antigravity on xCloud

Managing servers with Antigravity means asking Google's agentic IDE to read your xCloud servers and change their runtimes, PHP versions and services, with Antigravity's Ask mode and xCloud's confirmation both in front of every change.

Skill: xcloud:servers
Toolsets: servers, alerts, user
Free with every xCloud account

Set up Antigravity All Antigravity guides

YouSet PHP 8.3 as the default on Frankfurt and move my sites to it.

servers_php-versionsread-only

Agent8.3 is installed on frankfurt-1. As the server default it changes the command-line php and the version new sites get. It does not move existing sites: each site's PHP version is a dashboard setting under Site > Site Settings. Set the default?

YouYes, set the default.

servers_php-versions_defaultneeds approval

AgentDone once the task settled. The default on frankfurt-1 is 8.3, and your existing sites still run their own versions.

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 servers 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

Which PHP versions are installed on the Frankfurt server, and which one is the default? Do not change anything.

In practice

How Does Server management Work from Antigravity?

Runtime versions are the part of server management where an agent most needs to be precise, and Antigravity's agent panel is a good place to ask. Say you upgrade an application and want a newer PHP on the Frankfurt server. You ask for PHP 8.3 as the server default. The agent lists the installed and available PHP versions, installs the one you need if it is missing, and then explains what the default does before it sets it: it changes the command-line php and the version new sites get, and it does not move any existing site. Each existing site keeps its own PHP version, a dashboard setting under Site > Site Settings, so if you wanted your sites moved too, the agent gives you that path instead of pretending it did the work.

Node.js is the opposite case. The default is server-wide, so changing it affects every Node site on that server, and the agent says so in its question. After you approve, it reads the server's task list until the task settles and reports the version that is now the default. OPcache toggles and PHP patch updates follow the same rhythm, and a reboot you ask for afterwards is tracked until xCloud reports a verified new boot, never assumed from the acceptance.

Antigravity adds its own check in front of that. A tool you have not configured runs in Ask mode, so every xCloud call that changes something appears in the panel for you to approve, and xCloud then applies its own confirmation to the changes it treats as explicit-confirmation. Reads are the calls you will want to stop being asked about, and the permission policy lets you allow them one tool at a time. The same mcp_config.json serves the IDE, the command-line tool and Antigravity 2.0, so the setup you tune here applies wherever you open a project.

Antigravity specific: Antigravity runs an MCP tool you have not configured in Ask mode, which is the right behaviour for a default change or a service restart. When you allow tools, do it one at a time with patterns such as mcp(xcloud/servers_index) and mcp(xcloud/servers_monitoring). A wildcard like mcp(xcloud/*) would also skip Antigravity's prompt for service changes, PHP and Node.js defaults and firewall rules, leaving xCloud's confirmation as the only check. And keep the remote property as serverUrl in mcp_config.json.

What xCloud does for server management

xCloud lets the agent list your servers, read their monitoring, and manage services, Node.js and PHP versions, cron jobs, firewall rules, Fail2Ban and sudo users. Changes that can interrupt a server stop for your approval, and a reboot is only reported as done after xCloud verifies a new boot.

Pick the team and the server. The agent works on one team at a time and uses the server you name. If a name is missing or matches several servers, it lists them and asks. It always restates which server it is about to change before it changes it.
Read the state first. It reads the server's status, installed services, runtimes and monitoring figures. A status such as low disk space or reboot required is worth surfacing on its own. Monitoring history is a paid-plan feature, so a free plan answers 403.
Say what will change, then ask. For a service, runtime, cron, firewall or sudo change, the agent names the server, the item and the impact, for example that a Node.js default affects every Node site on the server. It waits for your approval when the change could interrupt a service.
Follow the task to the end. xCloud accepts server work and returns before it finishes. The agent reads the server's task list until the task settles and reports the real outcome, not the acceptance.
Reboot with proof. A reboot starts a tracked operation. The agent reads that operation until xCloud reports a verified new boot. If the result is unconfirmed it investigates and never repeats the reboot just to check.
Buy a server only after approval. A new server is billable. The agent checks what you already have, reads the plans and the card on file, shows the plan, region and price, and waits for a yes. It sends the purchase once with an idempotency key so a retry cannot buy a second server.

Reference

Server management Settings and Limits on xCloud

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

Setting or limit	What applies
Inventory	Every server on the team with its status, stack and the sites it hosts, plus the tasks, supervisor processes and site snapshots on a server
Monitoring	Current CPU, memory and disk are readable. Monitoring history is a paid-plan feature: xCloud answers 403 on the free plan, which is a plan limit and not a permission
Services	Install, enable, restart and disable. A restart runs without a server-side prompt; the agent still confirms the exact server, service and impact before any service change, because disabling ssh, nginx or a database can lock you out or cause downtime
Node.js versions	Read the installed versions and set the default. The default is server-wide and affects every Node site on the server
PHP versions	Install, uninstall, set the default, patch and toggle OPcache. The server default changes only the command-line php and the version new sites get; it does not change existing sites, and a single site's PHP version is a dashboard setting under Site > Site Settings
Cron jobs	List, create, update, delete, run now and read the last output for server cron jobs. Site cron is a separate resource
Firewall rules	List, create, delete, enable and disable rules with a name, protocol, allow or deny, port and optional source IP
Fail2Ban and IP access	List, ban and unban IP addresses, read the SSH restriction status, and whitelist your current IP or xCloud's own IPs
Sudo users	List, create or update and delete sudo users. A password is a secret and private keys are never returned
Verified reboots	Start a tracked reboot and read its operation; only a verified new boot proves it worked. An unconfirmed reboot can be rechecked without rebooting again
Buying a server	Billable, so it needs an approved plan, region and price, a card on file and an idempotency key. It buys xCloud-managed servers only
Dashboard-only	Resizing or deleting a server, a provider backup of the whole server (Server > Backup), bringing your own server, databases and database users, and PHP settings such as memory limit or upload size

Rules Antigravity has to follow

A change that can interrupt a server stops for your approval, and the agent names the server, the service and the impact first.
Buying a server is billable: the agent shows the plan, region and price and waits for your yes, and it never retries a purchase without checking your server list first.
A reboot is only reported as done when xCloud verifies a new boot, and an unconfirmed reboot is investigated, not repeated.
Disabling ssh, nginx, a database or a runtime service needs your explicit confirmation immediately before the call, because it can lock you out or take sites offline.
Resizing or deleting a server, provider server backups, bringing your own server and per-site PHP versions are dashboard steps; the agent gives you the path and the dashboard link xCloud returned.

Example prompts

What Can You Ask Antigravity to Do for Server management?

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

Which PHP versions are installed on the Frankfurt server, and which one is the default? Do not change anything.

Prompt

Install PHP 8.3 on the Frankfurt server and set it as the server default. Tell me what that changes and what it does not.

Prompt

Turn OPcache on for PHP 8.3 on the Frankfurt server and confirm the task finished.

Prompt

List all my xCloud servers with CPU, RAM and disk usage, and flag any server above 80% disk.

Prompt

List the cron jobs on the Frankfurt server with their schedules.

Prompt

Create a server cron job for the WooCommerce Action Scheduler every five minutes. Show me the final command and schedule before creating it.

Prompt

Install Redis on the Frankfurt server and enable the service.

Prompt

Switch the Frankfurt server's default Node.js to the latest LTS major.

Prompt

Reboot the staging server and tell me when it is back.

Prompt

Show me the IP addresses Fail2Ban has banned on the Frankfurt server, and unban 203.0.113.10.

Prompt

Create a new xCloud server on the smallest plan in Singapore. Show me the plan and price first and wait for my approval.

Antigravity and Server management: Frequently Asked Questions

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

If I ask Antigravity to upgrade PHP on a server, what does it actually change?

It changes the server default: the command-line php and the version that new sites get. It does not move existing sites, because each site keeps its own PHP version, which you change in the dashboard under Site > Site Settings. The agent says this before it asks you to approve.

Will Antigravity ask me before it changes a server setting?

Yes, in two layers. Antigravity runs MCP tools you have not allowed in Ask mode, so you approve each call in the panel. xCloud then stops for explicit confirmation on a reboot, a runtime change or a purchase, and the agent names the server and the impact first.

Does the agent ask before it reboots a server?

Yes. A reboot stops for your explicit confirmation, then the agent starts a tracked reboot and reads the operation until xCloud reports a verified new boot. If the result stays unconfirmed it investigates rather than rebooting a second time.

Can an AI agent buy a new server for me?

Yes, but only after you approve it. A new server is billable, so the agent first checks your existing servers, reads the available plans and your card on file, then shows the plan, region and price and waits for your yes. It sends the purchase once, so a retry cannot buy a second server.

If the agent changes the server's PHP default, do my sites change version?

No. The server default changes the command-line php and the version new sites get, and it moves no existing site. Each site keeps its own PHP version, which you change in the dashboard under Site > Site Settings.

Can the agent resize or delete a server?

No. Resizing and deleting a server are dashboard-only, as are a provider backup of the whole server, databases and bringing your own server. The agent can tell you where the control is and give you the server's dashboard link.

Why did the agent say monitoring history is not available?

Monitoring history is a paid-plan feature, so xCloud answers 403 on the free plan. Current CPU, memory and disk readings are still available, and the agent will say that it is a plan limit, not a missing permission.

Other agents