Deploy a site from a public archive URL
deploy_from_urlFetch a public tar(.gz) archive over HTTPS and deploy its files to an existing site in one call (begin_deploy, upload and commit_deploy combined). Use deploy_from_url when the files are already published at a public URL, such as a repository archive that holds only the built site (no dotfiles), or when your sandbox reaches the allowed hosts (listed under archiveUrl) but not mcp.vibedeploy.be; otherwise use deploy_site or update_site. In replace mode one top-level folder that wraps every file (as in repository archives) is removed, and a site that already has files needs confirm:"I-want-to-replace-all-files". A failed call never leaves a staging session open.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>",
"archiveUrl": "<archiveUrl>",
"mode": "<mode>"
},
"name": "deploy_from_url"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | Yes | replace: the archive becomes the whole site (other files are removed). patch: the archive's files are added or overwritten, the rest stays. | |
| name | Yes | Name of an existing site (see list_sites). This tool does not create sites. | |
| confirm | No | Required only for mode "replace" on a site that already has files. Pass exactly "I-want-to-replace-all-files" to acknowledge that the live files will be deleted and replaced with the archive's files. | |
| archiveUrl | Yes | Public HTTPS URL of a tar or tar.gz archive (max 100 MB, 60 s). Allowed hosts, also for every redirect: github.com, codeload.github.com, *.githubusercontent.com, gist.github.com, gitlab.com, bitbucket.org, codeberg.org, *.amazonaws.com, *.r2.cloudflarestorage.com, *.backblazeb2.com, *.workers.dev, *.pages.dev, transfer.sh, 0x0.st, mcp.vibedeploy.be. GitHub, GitLab and Codeberg archive links (e.g. https://github.com/<owner>/<repo>/archive/refs/heads/main.tar.gz) are accepted, but the normal file rules apply: any dotfile except .well-known/ (such as .gitignore, .github/, .gitlab-ci.yml) or any file type outside the allowlist (such as .ts, .tsx, .yml) rejects the whole archive with INVALID_FILE_TYPE. Replace mode removes only the one wrapping folder, so the built site must sit at the repository root. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| mode | Yes | ||
| name | Yes | ||
| siteId | Yes | ||
| manageUrl | Yes | Dashboard page where the user manages this site (domains, versions, settings). | |
| archiveUrl | Yes | ||
| bytesFetched | Yes | ||
| filesDeployed | Yes | ||
| strippedPrefix | No | Top-level folder removed from every archive path (replace mode, when one folder wraps all files). |