Terminal
Terminal/Skill
Steps for uploading local files or public URLs to the ImageKit media library without pasting file contents into chat.
By ImageKit
Works with
npx skills add imagekit-developer/skills --skill upload-filesUploads go through DAM (https://imagekit.io/mcp/dam).
Never put file bytes in the conversation or a tool argument. No base64, data URIs, Buffers, or streams. That burns tokens and fails for large files.
An upload is a multipart/form-data POST to ImageKit's upload endpoint, authorized by a short-lived, single-use signature. The DAM server only signs. The file goes straight from where it lives to ImageKit: from the user's machine for a local file, or fetched by ImageKit for a public URL. Your job is to get a signature for each file and make sure the POST runs where the file is.
| Situation | Call |
|---|---|
| You can run shell commands in the user's environment (one file or many, local paths or public URLs) | create_upload_signatures_in_bulk, then run the returned uploadCommand. |
| No shell, and the user wants to pick a file on their computer (the client can show MCP Apps) | upload_file with no parameters. Opens a picker (filename, folder, tags, custom metadata). |
| The user will run the upload themselves elsewhere and needs the signed form fields | create_upload_signature; they POST each file with its formFields. |
Prefer create_upload_signatures_in_bulk whenever there is a shell, even for a single file: the signed tokens never enter the conversation, and one command uploads everything and reports a status line per file.
If they asked you to write upload code for their app, use search_docs — do not upload to their library unless they asked for that.
create_upload_signatures_in_bulkfileName, folder, and upload fields.manifestUrl until expire (60 to 3,600 seconds, default 600). Pass localDirectory so the command knows where the local files are.uploadCommand in the user's shell. It changes into the local directory, fetches the manifest, and uploads up to 16 files at a time.<status> <name>. 200 means uploaded. SKIP <name> means the name was refused locally (empty, contains / or ", or starts with .).manifest unavailable and uploads nothing, so sign again.create_upload_signatureFor when the user runs the upload themselves (their own script or another machine). The result contains the signed tokens.
fileName, plus optional folder, tags, customMetadata, and other upload fields. expire applies to all of them.uploadUrl and, per file, formFields: the exact fields its signature is bound to, including token.uploadUrl with file=@<LOCAL_FILE_PATH>, or file=<PUBLIC_URL> to have ImageKit fetch it, plus that file's formFields exactly as returned. Adding, removing, or re-serializing fields fails the signature check.list_custom_metadata_fields).search_media_library, the upload responses, or the bulk command's status lines./, not a local path. Nested folders are created as needed._internal_original_created_datetime custom metadata key to an ISO 8601 string. It exists only on accounts that enabled the original creation date setting; check list_custom_metadata_fields for it (reserved: true).