What your AI tool can do

Once you’ve connected your AI tool, it can create sites, put new versions online, follow deploys and restore earlier versions in your workspace. You don’t need to name the tools below: just say what you want, and your tool picks the right ones.

The tools

Tool	What it does
`check_name`	Checks whether an address like `my-portfolio.cloudzyro.app` is free, and suggests others if it’s taken.
`create_site`	Creates a new site in your workspace and claims its address. The site isn’t online until a version is deployed.
`get_upload_link`	Gives a one-time link for sending a project folder from your computer as a .zip. The link works once and expires after 15 minutes.
`deploy_upload`	Puts the uploaded files online as the site’s new version, after the same checks as an upload in the console.
`deploy_files`	Puts a small site online from files sent directly: up to 500 files and 4 MB in total.
`get_deployment`	Shows how a deploy is going: waiting, building, starting, live, or why it didn’t go live, with the likely cause, a suggested fix and the error lines (secrets removed).
`list_sites`	Lists the sites in your workspace, with whether each is live and its address.
`get_site`	Shows a site’s status, address, plan and latest version.
`list_versions`	Lists a site’s versions and which can be restored (5 on Launch, 10 on Boost).
`restore_version`	Puts an earlier version back online. The current version stays online until the restored one is ready.

Creating sites, deploying and restoring need an owner or admin in the workspace. If you’re a member, your tool can only look.

What your tool can’t do

These are deliberately left to you, in the console at https://console.cloudzyro.com:

Delete sites. Do it from the site’s Settings tab.
See or set environment variables, keys or passwords. Add them on the site’s Environment variables tab. See Set environment variables.
Change plans or buy anything. Use the site’s Billing tab. See Choose a plan for your site.

It also can’t deploy a site that’s connected to GitHub, GitLab, Bitbucket or a Git address. Those sites take new versions only from their repository.

Tips for asking

Be specific about the site. “Deploy this folder to my-portfolio on Cloudzyro” avoids a new site being made when you meant to update one.
Run it from the right folder. Tools that work with files on your computer, like Claude Code, Cursor and Codex, send the folder you’ve opened. Open the folder with your index.html or package.json at the top.
Ask it to follow through. “Tell me when it’s live” makes sure your tool checks the deploy rather than stopping once the files are sent.
Ask it to fix failures. If a deploy doesn’t go live, your tool gets the reason and a suggested fix. “Fix it and deploy again” is often enough.
Name what changed. “Deploy with the message New pricing page” makes the version easier to find on the Versions tab.
Keep secrets out. Tell your tool not to put keys in your code. Your tool knows never to send .env files, and we leave them out of uploads anyway.
Keep data in a database. If your tool says the site saves data in its own files, ask it to use a database instead, then connect one on the site’s Database tab. See Connect a database.

Files meant for one visitor

Cloudflare caches your site’s static files, such as images, CSS, JavaScript, fonts and PDFs, so they load quickly everywhere. Pages themselves (HTML) are never cached, and nor are requests that carry an Authorization header or a typical login cookie.

If your site serves a file at a static-looking address that’s meant for just one signed-in visitor, like an avatar or an invoice, it must be sent with the header:

Cache-Control: private

That stops it being cached and shown to anyone else. It’s worth telling your AI tool about this when it builds sign-in features.