Book a demo
Book a demo
Login
NewImprovedFixedSecurity

v2.8.8

Agent-Ready Deployments, Multi-Team Access, and Smarter Infrastructure Management

xCloud v2.8.8 introduces a significantly upgraded MCP and Public API experience, multi-team API access, deployment diagnosis and recovery, Git staging through the API, smarter backup recovery, and reliability improvements across WordPress, xSpeed, OpenClaw, Git deployments, SSL, and server provisioning.

Release at a Glance

  • 7 major new features
  • 6 customer-facing improvements
  • 7 bug fixes and security updates

🔥 New Features

A More Capable xCloud MCP and Public API

xCloud MCP can now help agents find the right operation, answer product questions, validate inputs before execution, and recover failed deployments. The unified MCP endpoint supports both the complete tool set and a compact profile for clients that prefer a smaller surface.

  • Diagnose why a Git deployment failed and see the actions needed to fix it.
  • Correct deployment settings and retry a failed deployment on the same site.
  • Preview site creation — and check a Docker Compose repository — before any resources are created.
  • Manage supported server services and change Node.js versions through the API and MCP.

Multi-Team API Tokens and MCP Access

One connection. Every team you choose. Grant one API token or one MCP connection access to the teams you select, keep one as its default, and switch to another granted team on any request, without creating more tokens or reconnecting your AI client.

  • Before, a token or MCP connection worked with exactly one team; agencies needed a separate token per client or had to authorize again for each team.
  • Now you authorize once and pick the teams. The Public API selects a team with the X-Team-Id header; an MCP agent passes the optional team argument.
  • Only the teams you grant are reachable. Each team’s existing roles and permissions still apply, and a request for an ungranted team is refused rather than redirected.
  • Existing single-team tokens keep working without changes.

Read the guide: Manage multiple xCloud teams with one API token or MCP connection.

Git Staging Environments Through the Public API

Create a Git-backed staging environment for an existing production site through the Public API. Temporary xCloud staging domains and custom domains are supported through the same provisioning workflow used by the dashboard.

Cloudflare-Assisted Git Deployments

Git deployment requests can now use a connected Cloudflare integration to configure DNS and supported SSL settings automatically, reducing the manual work required to bring a new site online.

Automatic Backup Health Recovery

xCloud can now detect sites that have stopped producing expected backups and automatically repair supported configuration problems, improving backup reliability even when no failed task is visible.

Safer Deploy Scripts

New sites now stop a custom deploy script as soon as a command fails, preventing a partially failed build from being reported as successfully deployed. Existing sites keep their current behavior and can enable the stricter mode from Git settings.

Flexible Server Checkout

Opening an app- or stack-specific sales link now lets you change the server specification without losing the selected app, stack, or checkout context.

✨ Improvements

  • Git deployments detect more project types, keep your resolved build settings, and work more reliably with private Docker Compose repositories.
  • WordPress creation now previews database requirements up front and returns clearer progress and dashboard links.
  • Sites powered by xSpeed now correctly show page caching as active in site lists.
  • Production PHP configurations now hide visible PHP errors from visitors by default.
  • OpenLiteSpeed restarts are safer — harmless pre-existing warnings no longer block a restart.
  • OpenClaw setup no longer hangs during model selection.

🐛 Bug Fixes and Security

  • Fixed WordPress provisioning on servers that do not yet have a database service.
  • Fixed xSpeed installation failures caused by another plugin’s output corrupting the generated web-server configuration.
  • Made deployment retries more dependable — corrected Dockerfile paths are now used, and a deploy is no longer lost if the first connection to the server fails.
  • Restored Git deployment webhooks for older sites.
  • Fixed Public API site filters that could return a server error for status or type filters, and database credential collisions for www site variants.
  • Fixed SSL issuance for manual DNS setups, and outdated OpenLiteSpeed TLS notices that could not be dismissed cleanly.
  • Fixed server creation failures on Hetzner caused by SSH key name collisions, plus a range of smaller MCP fixes across validation, search, and deployment responses.