# xCloud v2.9.15

> Released November 12, 2026

**Every MCP Tool for Every Team, and Git Apps That Keep Their Data**

Your AI agent can now use every xCloud MCP tool, on every team, white-label included. One-click apps show the version they install and link to the official project. Python, Ruby, Go, Java and Bun apps keep the data folders they need between deploys.

## 🔥 New Features

### 🆕 Use Every xCloud Tool From Your AI Agent

Before, many tools only worked for teams in the beta, and white-label teams could not use them. Your agent often said it could not do everyday jobs. Now every tool works for every team, and agents can do a few more things the dashboard does.

**Who it's for:** Anyone who manages xCloud from an AI agent, including agencies and white-label resellers.

-   Every MCP tool is open to every team. White-label teams get them in their own brand.
-   Your agent can search for the right tool and read step-by-step guides, whichever xCloud MCP address it connects to.
-   An agent can see which WordPress core and plugin files failed the file integrity check, and start a fresh check.
-   An agent can filter a site's access logs by IP, status, path and time, on every team.
-   An agent can turn your team's To-Do list on or off, and choose which options new WordPress sites start with, such as caching and backups (**Site Install Defaults**). It shows you the change first, and nothing changes until you confirm.
-   An agent can read how much Cloudflare Enterprise bandwidth each domain, site or team has used this month.

[How to Connect xCloud MCP to Your AI Agent](/docs/how-to-connect-xcloud-mcp-to-ai-agent/)

### 🆕 See What a One-Click App Installs Before You Install It

You could not see which version a one-click app installs, or where the project lives. Now each app shows its version, category, GitHub stars and official links.

**Who it's for:** Everyone who installs one-click apps.

-   App cards in the catalog show the version beside the name, plus the category and GitHub stars.
-   The app page adds **Website**, **Source code** and **Documentation** links, the license, and stars that open the repository.
-   After install, the credentials card shows the installed version and the same links.
-   Apps made by other projects carry a notice that they are a third-party project, not affiliated with or endorsed by xCloud.
-   The catalog now shows up to three columns, to make room.

[Use One-Click App Templates in xCloud](/docs/how-to-use-one-click-app-templates-in-xcloud/)

### 🆕 Keep Your App's Data Folders Between Deploys

Python, Ruby, Go, Java and Bun apps that xCloud builds kept only `/app/data` between deploys. Apps that store a SQLite file or uploads elsewhere lost that data on every deploy, with no warning. Now xCloud keeps every folder your app needs.

**Who it's for:** Developers who deploy apps from Git.

-   xCloud reads your repository's example env file and lists the folders under **Kept between deploys** on the create form. You can remove a folder or add one, up to five.
-   If an env value points at a folder that is not kept, the form warns you and suggests a path inside a kept folder.
-   Existing sites keep their folders as they are. Their **Environment** page shows the same warning when a value points outside a kept folder.
-   A Java app on an OpenLiteSpeed server now gets a clear message that it needs an Nginx server.

[Deploy Python, Ruby, Go, Java and Bun Apps from Git in xCloud](/docs/deploy-python-ruby-go-java-and-bun-apps-from-git-in-xcloud/)

## 🧑‍💻 For Developers: Public API and MCP

-   **MCP endpoints:** `/mcp`, `/mcp?profile=unified` and `/mcp/v2` now serve every tool to every team. `/mcp/v2` and `?profile=compact` serve the unified tool set (search, execute, docs). `/mcp` stays on the flat tool set by default.
-   **Access log filters:** a filter value that was ignored before now returns a 422 error.
-   **File integrity:** the integrity read and the fresh check work for WordPress sites only. Other sites get a 422 `wordpress_required` error.
-   **One-click catalog:** the catalog and schema endpoints return `app_version`, `links`, `license`, `official` and `github_stars`.
-   **Git deploys:** `POST /api/v1/git/detect` returns `persist` and `data_paths`, and `git/auto` accepts `persist` to choose the kept folders.
-   **Enterprise API:** SSH keys sent to the Enterprise API must belong to your team.

## 🔒 Security

-   **Social sign-in:** when you prove you own an account, Google and GitHub sign-in links made before its email was verified are removed. You see "For your security we removed the social sign-in links on this account." Reconnect them under **Settings** → **Authentication**.
-   **Backup restores and migrations:** if a backup or migration file contains a shortcut to files outside your site, xCloud skips it and tells you which one. Normal sites see no change.
-   **Staging sites:** no other account can take your staging hostname, point its DNS elsewhere or remove it. A staging name cannot be a domain xCloud manages itself, such as `wp1.sh`. Use a name under it, such as `my-site.wp1.sh`. The SSL page of a staging site no longer shows certificate details you don't need.
-   **Team access:** a team member with limited site access can no longer change a site they cannot view while setting up a clone.
-   **Migrations:** No other account can change your migration's progress or cancel it. The domain name of a migration must be a valid domain.
-   **Database settings:** on xCloud Managed servers, only your own database clusters are listed.
-   **Cloud keys:** xCloud only reads the parts of your Google Cloud key file it needs. AWS key pairs and SSH keys must belong to your team.
-   **Site snapshots:** while a snapshot is being made, only the server's admin user can open its database file.

## ⚡ Improvements

-   **PostgreSQL at server creation:** PostgreSQL 17 is now an option in the **Select Database Server** dropdown on Nginx servers, next to MySQL and MariaDB. The separate PostgreSQL checkbox is gone. You can add another database later from server management. [How to Install Managed PostgreSQL and pgAdmin in xCloud](/docs/install-managed-postgresql-and-pgadmin-in-xcloud/)
-   **Environment saves on Docker apps:** saving **Environment** while the app deploys no longer times out or starts a second build. A save that could not reach the server is applied by your next deploy or restart, and the message says so.

## 🐞 Bug Fixes

-   **Docker App Backups**
    -   Backups of a Dockerfile app with Release mode on now work after a new release goes live. Restores now put your data back into the live copy of your app.
    -   A restore now brings data back even when your Docker Compose file stores it without a named volume. Before, it said "Restore completed" but the app kept its old data.
    -   A restore that fails partway, such as on a full disk, now keeps your old data.
-   **Server Creation**
    -   On xCloud Vultr servers, cancelling the "switch plan" box now keeps PostgreSQL picked.
-   **Caching**
    -   Markdown requests from AI crawlers, such as Slim SEO's Markdown for AI, now skip the cache and get Markdown. Before, they got the cached HTML page.
-   **AI Assistant**
    -   **Ask AI why** on an SSL To-Do now finds the right site. When you reply "yes, fix it", the assistant still knows which site or server to fix.
    -   The assistant now reads the site or server you named.
-   **WordPress Install Page**
    -   On phones, the **Security** row and its cards now read properly. Before, the title was squeezed into a narrow column.
-   **MailBox and Checkout**
    -   You can add one free mailbox per request, and it must use the selected site's domain. Set the others to a paid plan.
    -   A mailbox whose payment failed is no longer set up until it is paid.
    -   Checkout now needs a finished card setup before a paid plan starts.
