Docs menu
Get started
What is Opus GrowthQuickstartAdd to your AIHow it worksSafety and approvalCreditsPlansFAQAI apps
All AI appsChatGPTClaudeGrokPerplexityClaude CodeCodexGemini CLIOpenClawCursorVS CodeWindsurfOther MCPConnect ad platforms
Google AdsMeta AdsLinkedIn AdsMicrosoft AdvertisingTikTok AdsChatGPT AdsAgencies and MCCConnect data sources
Search ConsoleGoogle AnalyticsYouTubeBusiness ProfileTag ManagerWebsites and SEO
AI ServerWordPressSEO IntelligenceClick fraudTool reference
All toolsGoogle AdsMeta AdsTikTok AdsLinkedIn AdsMicrosoft AdvertisingChatGPT AdsSearch ConsoleGoogle AnalyticsYouTubeBusiness ProfileTag ManagerWordPressAI ServerSEO IntelligenceClick fraudCross-channelAccount and billingLanguage
Deploy Site From ZIP
Deploy an ENTIRE website from a .zip onto the user's AI Server in one step.
- Type
- Makes changes
- Credits
- 1
- Platform
- AI Server
- Approval
- Preview first, applied after you approve
What it does
Deploy an ENTIRE website from a .zip onto the user's AI Server in one step. The zip comes as zip_base64 (a file dropped into chat, base64-encoded; practical up to a few MB) OR zip_url (a public link, fetched SERVER-SIDE with no chat cost; up to 300 MB). zip_url accepts a Google Drive or Dropbox SHARE link directly (shared as 'anyone with the link'); it is converted to a direct download and Drive's large-file confirmation is handled. 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).
MCP: deploy_site_zip
How to use it
You don't call tools by name. Write what you want in ChatGPT, Claude or another assistant connected to Opus Growth, in your own words; it picks this tool when it fits.
Parameters
| Name | Type | Required | Default | |
|---|---|---|---|---|
| zip_base64 | string | Optional | · | Exact zip base64 value for deploy site zip. Supply text in the provider's required format; when it selects an existing resource, use the exact identifier returned by the relevant list or search operation. |
| zip_url | string | Optional | · | Zip url URL used by deploy site zip. |
| server | string | Optional | · | Name of the connected hosting server to target when more than one server is available. |
| site | string | Optional | · | Identifier, key, or domain of the hosted site to target when more than one site is available. |
| page_token | string | Optional | · | Continuation token returned as next_page_token by a previous call. Leave empty for the first page; pass it unchanged to retrieve the cached next page. |
Related tools
add_siteSet Up Site Contact-Form Emailconfigure_site_smtpCreate Free Trial Websitecreate_trial_siteList Hosting Serverslist_serversList Websites On Serverlist_sitesRemove Website From Serverremove_siteInstall Site Starterscaffold_siteBlock Website Pathssite_block_pathsBackground Command Statussite_command_status