OpenClaw + xCloud

Manage SSL and domains with OpenClaw on xCloud

Managing SSL and domains with OpenClaw means sending a message to your own agent runtime from a chat app and getting back the certificate status, the DNS answer and, after your approval, a renewed certificate on xCloud.

Skill: xcloud:ssl
Toolsets: ssl-certificates, sites, integrations
Free with every xCloud account

Set up OpenClaw All OpenClaw guides

Youshop.example.com shows a certificate warning. Check it.

sites_sslread-only

AgentThe certificate expired 2 days ago. It is xCloud's free certificate and DNS still points at your server. I can renew it. Go ahead?

YouYes.

sites_ssl_renewneeds approval

AgentRenewal accepted. I will poll until it settles, then check the HTTPS URL and message you the new expiry.

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 OpenClaw to Manage SSL and domains on xCloud?

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

1
Install the xCloud skill from ClawHub
This installs the nine xCloud skills into the active workspace skills folder. Add --global to install them into ~/.openclaw/skills for every local agent. The clawhub CLI installs the same listing with clawhub install xcloud.
Terminal
```
openclaw skills install @asif2bd/xcloud
```
2
Add the xCloud MCP server and sign in
Run these on the installation that owns the connector. The --auth oauth flag matters: openclaw mcp login only runs for HTTP servers saved with OAuth, so without it the login is refused. The login prints an authorization URL, and OpenClaw normally captures the redirect on a loopback address and saves the credentials; Settings, MCP, Sign in in the Control UI does the same. On the xCloud approval screen tick the teams and choose Read-only or Full access.
Terminal
```
openclaw mcp add xcloud \
  --url https://app.xcloud.host/mcp \
  --transport streamable-http \
  --auth oauth
openclaw mcp login xcloud
```
3
Check the skill and the connection
The first command lists the skills that are eligible to run in this environment, and xcloud should be among them. The second opens a live connection and reports the tools the server offers. A saved server entry proves nothing until the probe passes. Then ask who am I on xCloud.
Terminal
```
openclaw skills list --eligible
openclaw mcp doctor xcloud --probe
```

Check it worked

Then ask OpenClaw for the job itself, for example:

Prompt

shop.example.com shows a certificate warning to a customer. Check the certificate and tell me what is wrong, in two lines.

In practice

How Does SSL and domains Work from OpenClaw?

OpenClaw lives on a machine or server you run, and you reach it from WhatsApp, Telegram, Slack or Discord. That suits certificate work because the moments you care about are rarely at a desk: a customer writes that the browser shows a warning, or a Cloudflare 526 page appears on a client's shop. You send the message from your phone, something like shop.example.com shows a certificate warning, check it. OpenClaw loads the xCloud skill, which routes SSL questions to the right reads, and calls sites_ssl and sites_sslCertificates through the MCP connection. It answers in the same chat: the provider, the status, the expiry date and whether the certificate is the cause. A 526 is treated as a certificate problem, while a 522 is sent to the firewall check instead.

The skill is what keeps the follow-up careful. Before it installs anything it reads the current state, and if another provider is already configured it tells you that switching needs an explicit override and asks first. When you reply yes, it restates the site and the provider, sends sites_ssl_renew or the install call, then polls ssl-certificates_status because the first success only means xCloud accepted the work. A renewal that does nothing, because the certificate is more than seven days from expiry, is reported as exactly that. For DNS it uses servers_dns_check, one lookup at a time, and says when a record is proxied.

OpenClaw's automations make this a standing watch. A job with a cron expression, an isolated session and an announce channel can audit every site's certificate each Monday and post the list to a group chat. Reading is safe to schedule. Renewing is not something to automate, so answer the report with a message when you want a change. And since a chat message is easy to forward by mistake, never send a custom certificate's private key through WhatsApp or Slack. Use the dashboard for that step.

OpenClaw specific: Run the xCloud MCP login on the installation that owns the connector, because a scheduled automation reuses those saved credentials and a Gateway on another host will not see the xcloud server until it is reloaded. The skill alone is not enough for this job: without the MCP server it falls back to a GET-only REST wrapper, which can read a certificate but cannot install or renew one. Check openclaw mcp doctor xcloud --probe before you rely on a scheduled audit.

What xCloud does for ssl and domains

xCloud lets the agent read a site's certificate status, domains and DNS, then install or renew a certificate from xCloud (Let's Encrypt), your own files or a connected Cloudflare account. Adding or changing a domain on an existing site stays in the dashboard, and the agent gives you the path.

Find the site and read its SSL. The agent resolves the site by name or domain, then reads its current SSL state and the list of certificates before it changes anything. That shows the provider, the status and the expiry date.
Check the domain and DNS. It reads the site's primary and additional domains and asks xCloud whether the domain's DNS record points at the server. Each check is one lookup, so the agent repeats it while a record propagates. A record behind Cloudflare's proxy is reported separately.
Choose the certificate source. You pick xCloud's free Let's Encrypt certificate, your own certificate, or the team's Cloudflare integration. If the site already uses a different provider, the agent tells you that switching needs an explicit override and asks first.
Install or renew, once you approve. The agent restates the site and the provider, then installs or renews the certificate. A renewal only runs when the certificate is within seven days of expiry unless you ask for a forced renewal. For a WordPress site turning on HTTPS for the first time, it asks whether to run the database search-and-replace.
Poll to issuance and verify. Install and renew report success before issuance completes. The agent polls the certificate status until it settles, then checks the site over HTTPS before it calls the job done.
Hand off domain changes. If you want to add, change or remove a domain on an existing site, the agent gives you the dashboard path (Site > Domain) and the site's dashboard link, because the API only reads domains after creation.

Reference

SSL and domains Settings and Limits on xCloud

The facts OpenClaw works within when it manages SSL and domains. Where a row names the dashboard, that step stays yours to take there.

Setting or limit	What applies
Certificate status	A site's SSL state, its certificate list and one certificate's detail and status are all readable
xCloud certificate	Free Let's Encrypt certificate issued and renewed by xCloud. The domain's DNS should already point at the server before you ask
Custom certificate	You supply the PEM certificate and its private key. The key is a secret and is never returned by a read
Cloudflare certificate	Uses the team's connected Cloudflare account. When the zone is connected, xCloud writes the DNS record and the certificate itself at site creation
Switching provider	Needs an explicit force when another provider is already configured, so the agent asks before it replaces a working certificate
Renewal rule	A renewal does nothing unless the certificate is within seven days of expiry; a forced renewal skips that guard. Renewing needs the site SSL permission on your team role
WordPress first HTTPS	An optional database search-and-replace moves existing http:// URLs to https:// when a WordPress site adopts HTTPS for the first time
DNS check	One lookup per call. A proxied Cloudflare record is flagged, and on a Cloudflare-managed site the proxied record is the finished state, not a fault
Domains (read)	The primary domain, additional domains and the domain update status are readable through the API
Domains (write)	Adding, changing or removing a domain on an existing site is dashboard-only: Site > Domain. A staging site goes live under Site > Domain > Go Live
Deleting a certificate	Available through the API, but it can take a site off HTTPS, so the agent restates the target and waits for your approval
Cloudflare 526 errors	A 526 or a certificate warning is an SSL problem, so the agent reads the certificate first. A 522 is different: it usually means ports 80 and 443 are blocked at the origin

Rules OpenClaw has to follow

Installing, renewing, switching or deleting a certificate stops for your approval, and the agent names the site and the provider before it asks.
A success response means xCloud accepted the work, not that the certificate was issued: the agent polls the status and checks the live HTTPS URL.
The agent never replaces a working certificate with a different provider without telling you, and it never turns off the Cloudflare proxy on a site xCloud manages through Cloudflare.
Changing a domain on an existing site is a dashboard step; the agent gives you the path and the dashboard link xCloud returned, not a made-up workaround.
A custom certificate's private key is a secret: it is never returned by a read and should not be pasted into a shared channel.

Example prompts

What Can You Ask OpenClaw to Do for SSL and domains?

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

shop.example.com shows a certificate warning to a customer. Check the certificate and tell me what is wrong, in two lines.

Prompt

Is the DNS for example.com pointing at my server yet? Tell me if Cloudflare's proxy is on.

Prompt

Every Monday at 8am, list the sites whose certificate expires within 30 days and post it here. Change nothing.

Prompt

Check the SSL certificate on shop.example.com and tell me when it expires.

Prompt

Is the DNS A record for example.com pointing at my Frankfurt server yet? Tell me if the Cloudflare proxy is on.

Prompt

Issue a free SSL certificate for example.com once DNS resolves, then confirm the site loads over HTTPS.

Prompt

Renew the certificate on the shop site and tell me the new expiry date.

Prompt

List every domain and additional domain on the shop site and say which is primary.

Prompt

Which of my sites have a certificate that expires in the next 30 days?

Prompt

Use my connected Cloudflare account for the certificate on shop.example.com, and show me what will change first.

Prompt

Visitors get a Cloudflare 526 error on shop.example.com. Check the certificate and tell me what is wrong.

OpenClaw and SSL and domains: Frequently Asked Questions

What people ask before they let OpenClaw manage SSL and domains through xCloud.

Can OpenClaw renew an xCloud SSL certificate from a chat message?

Yes, once the xCloud MCP server is connected. OpenClaw reads the certificate first, then names the site and the provider and waits for your yes in the chat before it renews. With only the skill installed and no MCP server, it can read but not change anything.

Can an OpenClaw automation check my certificates every week?

Yes. Create an automation with a cron expression, an isolated session and an announce channel, and give it a read-only prompt about certificate expiry and DNS. Renewals stay manual, because they need your approval in a message.

Can an AI agent add a domain to an existing site?

No. The API reads a site's domains, additional domains and domain update status, but adding, changing or removing a domain on an existing site is a dashboard step under Site > Domain. A domain is chosen when the site is created. The agent can tell you what is currently set and give you the path.

Which certificate options can the agent install?

Three: xCloud's free Let's Encrypt certificate, a custom certificate you supply, and a certificate through your connected Cloudflare account. The agent checks the current state first and asks before it changes anything. Switching a site from one provider to another needs an explicit override.

Why did the agent say a renewal did nothing?

A normal renewal only fires when the certificate is within seven days of expiry. If you need it earlier, ask for a forced renewal and the agent will confirm before it runs. Renewing also needs the site SSL permission on your team role.

Does the agent set up my DNS records?

It reads and checks them rather than writing them. It can tell you whether a domain's record points at your server and whether the Cloudflare proxy is on. DNS and the certificate are written for you only at site creation, when the domain's zone is on a Cloudflare account you connected to xCloud.

What does the agent do about a Cloudflare 526 error?

It treats it as an SSL problem. It reads the site's certificate status and expiry, and fixes it with an installation or renewal after your approval. A 522 is a different fault, usually closed ports 80 and 443 on the origin, so it is checked against the firewall instead.

Other agents