deploy
Deploy a folder as a tool and make it live at https://.. Send the whole folder in files, which MUST include a top-level Dockerfile whose process listens on $PORT (8080). Creates the tool on the first deploy; afterwards it replaces the running container. If you got these files from pull, pass the release number you pulled as base so a deploy someone else made in the meantime is not silently overwritten.
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": {
"tool": "<tool>",
"files": "<files>"
},
"name": "deploy"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| base | No | The release number these files were pulled from. The deploy is refused with STALE_BASE if a newer release is live. | |
| name | No | Human name for the tool, used when it is created (e.g. 'CRCS Finance'). | |
| note | No | Why this release exists; shown in the release list. | |
| tool | Yes | The tool's short name, for example 'finance', or 'acme/finance' to select its workspace. | |
| files | Yes | The folder: relative path -> the file's text content, e.g. {"Dockerfile": "FROM python:3.12-slim\n...", "app.py": "..."}. No leading slash and no '..' in paths. | |
| base64 | No | Optional binary files: relative path -> base64 of the bytes. | |
| workspace | No | Workspace slug to act in. Use this when you belong to several workspaces; whoami lists them. |