Deploy Site From ZIP
deploy_site_zipDeploy an ENTIRE website from a .zip onto the user's AI Server in one step. Give the zip as zip_base64 (a file the user dropped into chat — base64-encode it; only practical up to a few MB) OR zip_url (a public link, fetched SERVER-SIDE with no chat cost — the way to do LARGE files up to 300 MB). zip_url accepts a Google Drive or Dropbox SHARE link directly (the file must be shared 'anyone with the link'); it is auto-converted to a direct download and Drive's large-file confirmation is handled — so the user just uploads to Drive and pastes the link. It uploads the zip to the user's own isolated server, unzips it and PUBLISHES it live at /data/site over HTTPS.
If the zip is ALREADY a static site (index.html at the root) it is published as-is — instant, no
build. If it is a source project it is BUILT on the server and the static output is published:
Next.js → STATIC EXPORT (output:'export' is injected automatically) from out/; Vite → dist/;
Create-React-App → build/. Sites are served statically: NO Node/SSR process runs at runtime, so
Next.js features that REQUIRE a live server are NOT supported (getServerSideProps/SSR, API routes
/api/*, ISR/revalidate, middleware, Server Actions, next/image default optimization). If the
project needs those, the static build fails and this returns a clear explanation; the fix is to
make the app statically exportable or use a runtime host. Everything under /data/site is REPLACED
(a version snapshot is taken first, so site_restore can undo it). Build cap ~10 min, zip ≤ 300 MB
(for anything above a few MB use zip_url — a 300 MB base64 will not fit the chat context).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| site | No | ||
| server | No | ||
| zip_url | No | ||
| zip_base64 | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||