Uploads Presign
uploads_presignDestructive
Start a direct file upload: answers where and how to send the file.
Send the file to url the way method says — PUT: the raw bytes as
the body, with the headers named; POST: a multipart form with every
fields entry, then the file as the last field, named file — and then
call POST /uploads/confirm. Until it is confirmed, the upload reserves
its declared size_bytes (the most its file type allows, when none is
declared) of the plan's storage; if url expires with no file sent, the
reservation is released. This is the upload path for a file of any size,
and the one a client that can only send JSON (every MCP client) uses:
the multipart upload routes cannot carry a file in a JSON argument.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Original filename of the file to upload. | |
| size_bytes | No | Size of the file in bytes, if known. Until the upload is confirmed it reserves this much of the plan's storage (the most its file type allows, when omitted), and a larger file is refused. | |
| content_type | No | MIME type of the file (e.g. application/pdf). |