Add files to a staging session
add_filesAdd files to an open begin_deploy session; call it as often as needed, then commit_deploy publishes them together. Paths, extensions and encodings are checked on every call. A 100-250 KB text file usually fits in one call with encoding:'gzip+base64' (gzip locally, then base64); prefer that over add_file_chunk. If your shell can reach mcp.vibedeploy.be, one tar(.gz) POST to begin_deploy's uploadUrl is faster still.
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": {
"deployId": "<deployId>",
"files": "<files>"
},
"name": "add_files"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| files | Yes | Files to stage, same shape as in deploy_site. Re-adding a path overwrites the staged version. 500 MB per session in total. | |
| deployId | Yes | Session id returned by begin_deploy. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| deployId | Yes | ||
| warnings | No | ||
| filesAdded | Yes | Files written by this call. | |
| totalBytes | Yes | Total bytes staged so far across all add_files calls. | |
| totalFiles | Yes | Total files now in the scratch dir. | |
| remainingBudget | Yes | Bytes still available before hitting the 500 MB cap. |