MCP tools: Files & artifacts
Last updated 10 days ago
MCP tools: Files & artifacts
A task has two separate stores:
- Cloud Drive — files someone attaches or files away (the input). Read them with
list_files/read_file, pass them on with a file link. File them withattach_file_to_list_item. - Artifacts — results an AI produces and publishes (the output): named, versioned bundles in the task's "Artifacts" box. They are not in
list_files; read them withlist_artifacts/read_artifact.
See also Files & Documents in the guide.
list_files
Cloud Drive files of a task or list. read · follower
Pass exactly one of itemId and listId. Each file comes with, among others, file_id, name, mime, size, readable_as_text, location and item_id (the file item). file_id goes to read_file, item_id to share_file_link. Files in external storage (Unified.to) come from search_files instead.
read_file
Content of a Cloud Drive file. read · follower
Text files (md, txt, json, csv, code …) come back as text, other binary files base64-encoded. Images (PNG, JPEG, WebP, GIF up to 4 MB) come back as an MCP image block a model can look at directly.
share_file_link
Create a link to one file or a whole folder in the Cloud Drive, e.g. to paste into a chat. write · user
All members of the organization can open the link, even without access to the project — guests cannot. If an active link exists, it is returned. You can only share files you can read yourself; if the project has turned file links off, the call fails. Response: url, active, created, opened_count.
get_file_link
Open a shared file link (https://<host>/<org>/f/<id>). read · follower
The response carries name, type, size, date and shared_by. Images, PDFs, videos and other binary files come back as a download_url (valid for 15 minutes). A folder link returns kind: "folder" with its entries. Expired, revoked or foreign links return an error with the reason.
publish_artifact
Attach a result to a task as an artifact, visible to the whole team.
write · userAn artifact is a named bundle of one or more files with an entry point, at most 50 files and 25 MB. If the bundle is byte-identical to the current version, no new version is created (unchanged: true). The response includes artifact_id, slug, version, created.
For files that are merely filed away (inputs, uploads, references), attach_file_to_list_item is the right tool.
list_artifacts
The artifacts of a task. read · follower
Per artifact: ID, name, kind, current version, entry file, the files of the current version and the version history.
read_artifact
Read the content of an artifact. read · follower
Text files come back as text, images as an image block, other binary files base64-encoded.
Was this helpful?
Still need help? Ask the team