xCloud for AI agents

AI Agent Hosting Management with xCloud

AI agent hosting management means an AI agent such as Claude Code, Cursor, Codex or OpenClaw deploys, monitors and fixes your servers and sites for you. xCloud makes this work: it exposes an MCP server, an installable skills package and a Public API, so any agent can run your hosting while you approve the changes.

  • Free with every xCloud account
  • OAuth in the browser, no token to paste
  • Read-only option; risky changes ask first

YouWhich of my sites have pending WordPress updates? Back each one up, then update, and tell me what changed.

sites_wordpress_updatesread-only

AgentThree sites have updates: shop (4 plugins), blog (2 plugins, 1 theme), docs (WordPress core). Back up all three and apply the updates?

YouYes.

sites_backup, sites_wordpress_updateneeds approval

AgentBackups finished. 7 updates applied, all three homepages answer 200. The docs site is on WordPress 7.0 now.

. Keep a human in the loop: xCloud stops and asks before anything that creates, deploys, updates, reboots, deletes or buys.

Agents

Which AI Agents Can Manage Hosting with xCloud?

Eighteen agents have a dedicated xCloud guide. Each row shows how that agent connects and how it authenticates; open the guide for the exact commands, example prompts and a page per hosting job.

AgentMade byHow it connects to xCloudAuthenticationGuide
Claude CodeAnthropicxCloud MCP server, plus the Agent SkillsOAuth sign-in, or an API key for headless useClaude Code guide
ClaudeAnthropicxCloud MCP serverOAuth sign-inClaude guide
Claude CoworkAnthropicxCloud MCP serverOAuth sign-inClaude Cowork guide
CursorCursorxCloud MCP server, plus the Agent SkillsOAuth sign-in, or an API key headerCursor guide
CodexOpenAIxCloud MCP server, plus the Agent SkillsOAuth sign-in, or an API key from the environmentCodex guide
OpenCodeAnomaly (open source)xCloud MCP serverOAuth sign-in, or an API key for headless useOpenCode guide
Hermes AgentNous ResearchxCloud MCP server, plus the Agent SkillsOAuth sign-in, or an API key for headless useHermes Agent guide
OpenClawOpen sourcexCloud MCP server, plus the Agent SkillsOAuth sign-in with openclaw mcp loginOpenClaw guide
WindsurfCognition (formerly Codeium)xCloud MCP serverOAuth sign-in, or an API key for headless useWindsurf guide
GitHub CopilotGitHubxCloud MCP server, plus the Agent SkillsOAuth sign-inGitHub Copilot guide
Gemini CLIGooglexCloud MCP serverOAuth sign-in, or an API key for headless useGemini CLI guide
ChatGPTOpenAIxCloud MCP serverOAuth sign-inChatGPT guide
ChatGPT dotsOpenAIxCloud MCP serverOAuth sign-inChatGPT dots guide
GrokxAIxCloud MCP serverOAuth sign-in, or an API key for headless useGrok guide
Grok BotxAIxCloud MCP serverOAuth sign-in, or an API key on a Team BotGrok Bot guide
KiroAmazon Web ServicesxCloud MCP server, plus the Agent SkillsOAuth sign-in, or an API key for headless useKiro guide
AntigravityGooglexCloud MCP serverOAuth sign-in, or an API key for headless useAntigravity guide
ZedZed IndustriesxCloud MCP serverOAuth sign-in, or an API key for headless useZed guide

Using an agent that is not listed? Any MCP-compatible client can use the xCloud MCP server, and any agent with a skills directory can load the xCloud Agent Skills. xCloud MCP · AI Agent Skills

Three ways in

How Do AI Agents Connect to xCloud?

An agent reaches xCloud through the hosted MCP server, the Public API, or the xCloud Agent Skills package layered on top of either. All three are free with every account. The MCP server exposes one tool per customer-facing Public API operation and leaves out eleven internal ones (the health check, API token management and the native apps' sign-in and push plumbing); the skills add workflow know-how and, on their own, only a read-only REST fallback.

SurfaceUsed byAuthenticationWhat you getLearn more
xCloud MCP serverClaude Code, Claude, Cursor, Codex, OpenCode, Hermes Agent, OpenClaw, Windsurf, GitHub Copilot, Gemini CLI, ChatGPT, ChatGPT dots, Grok, Grok Bot, Kiro, Antigravity, Zed and any client that speaks MCP Streamable HTTPOAuth sign-in in the browser; an API key with the mcp:invoke scope and the abilities it needs for clients without a browserOne tool per customer-facing Public API operation (188 today; eleven internal ones are left out) plus two search tools; a compact five-tool profile for clients that cap toolsxCloud MCP
xCloud Agent SkillsClaude Code (plugin), OpenClaw (ClawHub), and any agent with a skills directory through the portable Agent Plugins packageUses the MCP connection when one exists; otherwise a read-scoped API token for the GET-only REST wrapperNine Markdown skills that teach the agent xCloud's workflows: routing, dry run, confirmation, polling, diagnosis and retryAI Agent Skills
xCloud Public APIYour own code: scripts, CI jobs, dashboards and long-running agent loopsPersonal access token with scoped abilities, sent as a Bearer headerThe same operations as REST, with an OpenAPI 3.0 spec to generate a typed client fromAPI reference

Two minutes

How Do I Connect Any AI Agent to xCloud?

Three steps: give the agent the MCP server URL, approve access in your browser, then ask. Agents with a skills directory can add the xCloud skills on top of that connection. Every agent guide repeats these steps with the exact command for that tool.

  1. 1

    Point your agent at the xCloud MCP server

    Every MCP client takes the server URL, and that connection is what reads, deploys and updates. Agents with a skills directory can then add the xCloud skills from ClawHub, the Claude Code marketplace or the portable package; the skills teach the workflows and do not replace the connection.

    Terminal
    # The MCP server URL, pasted into any MCP client
    https://app.xcloud.host/mcp
    
    # Optional, on top of that connection: the xCloud skills
    # Claude Code plugin
    /plugin marketplace add xCloudDev/xcloud-agent-skills
    /plugin install xcloud@xcloud-agent-skills
    # OpenClaw, from ClawHub
    openclaw skills install @asif2bd/xcloud
  2. 2

    Approve access in your browser

    xCloud opens a sign-in page. Tick the teams the connection may act on and choose Read-only or Full access. Clients without a browser use an API key that carries the mcp:invoke scope and the read or write abilities it needs.

    Terminal
    # Headless clients: an API key instead of OAuth
    claude mcp add xcloud --transport http https://app.xcloud.host/mcp \
      --header 'Authorization: Bearer YOUR_TOKEN'
  3. 3

    Ask, then approve the plan

    Describe the outcome in plain words. The agent finds the right xCloud tool, runs reads and routine actions such as backups and scans straight away, and stops to ask before anything that creates, deploys, updates, reboots, deletes or buys.

    Prompt
    You: Deploy github.com/acme/shop to my Frankfurt server
         on a staging hostname, and back up the shop site first.
    
    Agent: Detected a Node.js app on the main branch. Dry run passed.
      - Backup of shop.example.com: done
      - New site shop-staging.acme.xcloud.site: ready to create
    Approve the deployment?
The xCloud MCP setup page in the dashboard: the server URL and tabs for Claude Code, Claude Desktop, Cursor and other clients
The same setup lives in your dashboard under Settings, Developers, MCP, with a tab per client.
The xCloud authorization screen for an MCP client: the signed-in account, a list of teams to tick, and the choice between Full access and Read-only
The approval screen: tick the teams the connection may act on and choose Read-only or Full access.

Verify in one line: ask your agent "Who am I on xCloud?". It should answer with your real account, not a guess. Full walkthrough: How to connect xCloud MCP to your AI agent.

What it can do

What Can an AI Agent Do with xCloud?

A connected agent reaches the operations the xCloud Public API exposes, grouped into nine areas. 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 for your approval. A few steps, such as restoring a backup or editing a backup schedule, stay in the dashboard, and each job guide says which.

  • Deploy

    Git repositories, Docker Compose and Dockerfile apps, one-click apps, branch staging and new WordPress sites, with a dry run before anything is created.

  • Troubleshoot

    Find the cause of a 500, 502 or 503 from status, recent events, bounded web-server logs, WordPress health and services, instead of guessing.

  • Performance

    Diagnose a slow site from monitoring history, cache state, existing PageSpeed results, traffic and the PHP version.

  • Servers

    Inventory and monitoring, services, Node.js and PHP versions, firewall and Fail2Ban, cron jobs, verified reboots and approved server purchases.

  • Sites

    Domains, cache, backups including Docker apps, staging environments, deployment events, SSH and SFTP, access logs and site cron.

  • WordPress

    Site health, plugin and theme updates, vulnerability checks and fleet summaries, broken-link scans, PageSpeed, WP_DEBUG and magic login links.

  • SSL

    Certificate status and HTTPS checks, Let's Encrypt and xCloud certificates, custom and Cloudflare certificates, installation and renewal.

  • Billing

    Plans, prices, invoices, bills, subscriptions, masked payment methods, approved invoice payments and mailbox or mail-delivery add-ons.

  • Account

    Who you are, which teams the connection may act on, incident alerts, Git and Cloudflare integrations, API tokens and WordPress blueprints.

Jobs

Which Hosting Jobs Can an AI Agent Do Through xCloud?

Every agent guide has a page for each of the ten jobs below, with the exact setup, the tools involved, a settings reference, example prompts and the limits that apply.

Reference

What Does the xCloud MCP Server Expose?

One tool per customer-facing Public API operation, grouped into toolsets, plus two search tools that help the agent find the right operation and answer questions from the documentation. Narrow a connection to the areas you need, or use the compact profile for clients that cap tools.

ToolsetToolsWhat it covers
servers61Create and list servers, monitoring stats, PHP and Node.js versions, services such as Redis and Docker, cron jobs, firewall rules, Fail2Ban, sudo users, reboots, staging hostname suggestions.
sites60Create, list and inspect sites, deploy from Git (native or Docker Compose), staging environments for Git sites, deploy diagnosis and correction, domains, DNS checks, SSL, cache purges, backups, cron jobs, events and logs.
billing10Current plan, billing overview, bills and invoices.
addons-mailbox9Mailbox plans, purchase, list, inspect, delete, verify DNS.
oneclick-apps7Browse the one-click catalogue, check server compatibility, install, poll status, fetch credentials, stop or redeploy.
vulnerabilities6Per-site findings and counts, the team-wide rollup, rescans, ignore and unignore a finding.
wordpress-actions5Update or activate plugins and themes, refresh the inventory, toggle WP_DEBUG, generate a magic login link.
sites-wordpress4List plugins and themes, the updates summary and the site health status.
broken-links4Trigger a broken-link scan and read its findings.
addons-mail-delivery4Mail Delivery plans, purchase and subscriptions.
alerts3List incident alerts, read one, mark it read.
pagespeed3Trigger a PageSpeed scan, latest snapshot, history.
ssl-certificates3Inspect, check and delete a certificate.
integrations3Connected Cloudflare and Git providers and their repositories.
catalog2The app catalogue and hosting pricing.
user2The current user and the teams the connection may act on.
blueprints1List blueprints.
payments1Pay an invoice.
xcloud_agent_search1Finds the right operation and the order to call things in. The assistant uses it when it is not sure which tool fits.
xcloud_docs_search1Answers a question from the xCloud documentation, so "how does the edge cache work?" is answered without a tool call against your account.

Server URL https://app.xcloud.host/mcp · compact profile https://app.xcloud.host/mcp?profile=compact · live toolset list · Public API reference

Unattended

Can an AI Agent Run xCloud on a Schedule Without Me?

Yes, where the agent runtime has its own scheduler. OpenClaw automations run a prompt on a cron expression, and Hermes Agent runs scheduled tasks; both call xCloud through the MCP connection, with the xCloud skills as an optional layer on top. The confirmation step still applies: a scheduled job can read, run PageSpeed and vulnerability scans and report on its own; a backup belongs in a request you are watching, because a Docker backup stops the app while it captures; and a broken-link scan and anything that creates, deploys, updates, reboots, deletes or buys waits for a person.

OpenClaw automations

A weekday job can check every site for pending WordPress updates and open vulnerabilities, read the latest PageSpeed results and post the summary to Telegram, leaving the updates and any backup for a message you can approve. Connect the MCP server first (openclaw mcp add with --auth oauth, then openclaw mcp login), add the xCloud skill from ClawHub on top if you want the workflow know-how, then create the automation.

Terminal
openclaw automations create "0 9 * * 1-5" \
  "Use xCloud to list sites with pending WordPress updates and open vulnerabilities, read the latest PageSpeed result for each, and summarise what needs approval. Change nothing and start no backup." \
  --name "Morning hosting check" --session isolated

Hermes Agent scheduled tasks

Hermes keeps memory across sessions and runs scheduled tasks, so a daily health report over the xCloud MCP connection needs no new prompt from you.

YAML
mcp_servers:
  xcloud:
    url: "https://app.xcloud.host/mcp"
    auth: oauth

Keep a human approving the queue. xCloud refuses the operations that cost money or break something unless the call carries an explicit confirmation. See the OpenClaw guide and the Hermes Agent guide.

Frequently Asked Questions

Short answers to what people ask before they connect an agent. Every answer is also on the agent guides.

What is AI agent hosting management?

It is when an AI agent, rather than a person clicking through a dashboard, deploys, monitors and repairs your servers and sites. With xCloud the agent calls the MCP server or the Public API, guided by the Agent Skills where they are installed, picks the right operation and runs it under the access you granted. Reads and routine actions such as backups, cache purges and scans run straight away; creating, deploying, updating, rebooting, deleting or buying is previewed first and waits for your approval. Changes need one of those two connections; the skills on their own only read.

Which AI agents can manage hosting with xCloud?

xCloud has guides for 18 agents: Claude Code, Claude, Claude Cowork, Cursor, Codex, OpenCode, Hermes Agent, OpenClaw, Windsurf, GitHub Copilot in VS Code, Gemini CLI, ChatGPT, ChatGPT dots, Grok, Grok Bot, Kiro, Antigravity and Zed. Any other client that speaks MCP Streamable HTTP works the same way, and an agent with a skills directory can load the Agent Skills on top of that connection.

Do I need an API key for my AI agent?

Usually not. Most clients sign in with OAuth: the browser opens, you choose the teams and the access level, and the connection is live. An API key is only needed for clients that cannot open a browser, and it must carry the explicit mcp:invoke scope plus the read or write abilities for the operations it will use; full access alone does not enable MCP.

What is the difference between xCloud MCP, the Agent Skills and the Public API?

The MCP server is a hosted endpoint at app.xcloud.host/mcp that exposes xCloud as tools for MCP clients. The Agent Skills are Markdown files, installed as a Claude Code plugin, from ClawHub or as a portable package, that teach an agent xCloud's workflows on top of those tools. The Public API is the REST layer underneath both, for code you write yourself.

Is OpenClaw the same as MCP?

No. OpenClaw is an open-source personal agent that extends itself with skills, so the usual path is the xCloud skill from ClawHub. OpenClaw can also act as an MCP client and connect to the xCloud MCP server directly. MCP, the Model Context Protocol, is the open standard Claude, Cursor, Codex and the other clients use to call the hosted server.

Claude Code, Claude Cowork and the Claude connector: which one do I need?

Use Claude on the web or desktop if you chat with Claude and want to add xCloud as a custom connector. Use Claude Code if you work in the terminal and want the claude mcp add command and the skills plugin. Use Claude Cowork if you delegate desktop tasks; it shares the connectors you set up in your Claude account.

Can an AI agent change my sites without asking?

Not for the operations xCloud gates. Reads run straight away, and routine actions such as cache purges, backups, service restarts, PageSpeed and vulnerability scans run without a prompt. Anything that creates, deploys, updates, reboots, deletes or buys is refused by xCloud unless the call carries an explicit confirmation, and the tool tells the agent to get your approval first. You can also start Read-only and widen access later.

Can an AI agent run xCloud on a schedule without me?

Yes, if the agent runtime has a scheduler. OpenClaw automations and Hermes Agent scheduled tasks can check sites, run PageSpeed and vulnerability scans and report on their own through the xCloud connection. A backup belongs in a request you are watching, because a Docker backup stops the app while it captures, and changes that need confirmation wait for a person, which is how it should stay.

Is xCloud MCP free to use with AI agents?

Yes. The MCP server, the Agent Skills and the Public API are included with every xCloud account, including the free plan, on managed and self-managed servers. There is no separate plan, no add-on and nothing to upgrade. Your AI assistant may have its own usage cost from its provider.

Which hosting jobs can an AI agent do through xCloud?

Deploy from Git, run Docker apps, install one-click apps, manage WordPress, back up and stage sites, manage SSL and domains, manage servers, troubleshoot a broken site, speed up a slow site and secure sites and servers. Each agent guide has a page for every one of these ten jobs.

Connect Your Agent to xCloud

Pick the agent you already use, paste one URL or one install command, and run your hosting by asking.