bkend MCP does NOT have dedicated storage tools. Use this workflow:
Search docs: search_docs with query "file upload presigned url"
Get examples: search_docs with query "file upload code examples"
Generate code: AI generates REST API code for file operations
Searchable Storage Docs
Doc ID
Content
7_code_examples_data
CRUD + file upload code examples
REST Storage API
Method
Endpoint
Description
POST
/v1/files/presigned-url
Generate presigned URL
POST
/v1/files
Register metadata (complete upload)
GET
/v1/files
File list
GET
/v1/files/:fileId
File detail
PATCH
/v1/files/:fileId
Update metadata
DELETE
/v1/files/:fileId
Delete file
POST
/v1/files/:fileId/download-url
Generate download URL
Multipart Upload (Large Files)
Method
Endpoint
Description
POST
/v1/files/multipart/init
Initialize multipart upload
POST
/v1/files/multipart/presigned-url
Get part upload URL
POST
/v1/files/multipart/complete
Complete multipart upload
POST
/v1/files/multipart/abort
Abort multipart upload
Upload Flow (Single File)
1. POST /v1/files/presigned-url -> { url, fileId }
2. PUT {url} with file binary + Content-Type header
3. POST /v1/files with { fileId, filename, contentType, size, visibility }
Multipart Upload Flow (Large File)
1. POST /v1/files/multipart/init -> { uploadId }
2. POST /v1/files/multipart/presigned-url -> [{ partNumber, url }]
3. PUT each part URL with file chunk
4. POST /v1/files/multipart/complete -> { file }
Official Documentation (Live Reference)
For the latest storage documentation, use WebFetch: