Niches · File storage & sharing

Get a file from the agent's sandbox or another service into storage

Four or more companies' docs show a full fit.

12companies, full fit
1companies, fit with a limit
14companies carry the tag
17share of the category's work
6first-hand accounts

What counts as done

The file stored byte-for-byte at the named path without the model emitting its contents as a tool argument, through an upload URL, a local path or a server-side fetch, in no more than three calls.

Measured, for our own tests: a 25 MB binary arrives with a matching checksum. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: save this deck to Box, upload the PDF I just made to OneDrive, put this attachment in the shared drive, copy the CSV into the bucket

Does the job 13

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Amazon S3 A
Amazon Web Services, Inc.
A presigned PUT, or multipart upload of up to 10,000 parts, takes bytes outside the model, and CopyObject copies server-side. source
Azure Blob Storage BB
Microsoft Corporation
A SAS-signed Put Blob or Put Block List (block blobs to about 190.7 TiB) takes bytes outside the model, and Copy Blob From URL copies server-side. source
Backblaze B2 A
Backblaze, Inc.
Presigned PUT and per-part upload URLs from the MCP or S3 API keep bytes out of the model, with server-side copy. The MCP's inline put is capped near 1 MiB over HTTP (acc-09, open), so the URL path is the one to use. source
Bunny Storage B
BunnyWay d.o.o.
PUT raw bytes to the HTTP API from the sandbox with the zone password and a SHA-256 Checksum header, or use S3 multipart up to 10,000 parts; a bad checksum is refused (BadDigest). source
Cloudflare R2 A
Cloudflare, Inc.
Presigned PUT URLs and multipart upload (10,000 parts, objects to 4.995 TiB) keep bytes out of the model; CopyObject and UploadPartCopy copy server-side, and CRC64NVME full-object checksums are supported. source
DigitalOcean Spaces B
DigitalOcean, LLC
Presigned PUTs and S3 multipart (10,000 parts, 5 TB) keep bytes out of the model. Presigned PUTs through the CDN are capped at 7.91 MiB, so they go to the origin host. source
Dropbox API + MCP B
Dropbox, Inc.
save_url fetches a file from a URL server-side (15-minute limit), and upload sessions take 150 MiB per request with sessions lasting 7 days, so a sandbox can stream a local file without the model emitting it. source
Fastio C
VividEngine, LLC (doing business as Fast Technologies)
Web upload imports from a public HTTPS URL server-side, and chunked upload takes CRC-32C, SHA-256 or MD5 hashes; single calls stop at 4 MB, so larger files go chunked. source
Google Cloud Storage A
Google LLC (Google Cloud EMEA Limited and other regional entities by billing address)
Signed PUT URLs and resumable uploads keep bytes out of the model. The MCP server's writes are text-only and capped at 8 MiB, so binaries go through REST. source
Google Drive API + MCP BB
Google LLC
Resumable uploads from the sandbox keep bytes out of the model, and files.copy copies server-side. acc-12, a community server failing on attachment URLs, is closed; the preview MCP's create_file schema isn't published. source
OneDrive and SharePoint files (Microsoft Graph) B
Microsoft Corporation
createUploadSession returns an uploadUrl that a sandbox can PUT to in byte ranges under 60 MiB, keeping bytes out of the model. acc-03, acc-10 and acc-11 were failures in a community MCP server, all closed. source
Tigris C
Tigris Data Inc.
Presigned PUT URLs from the S3 API or the MCP's sharing tools let a sandbox upload without the model carrying the bytes, through standard AWS SDKs at t3.storage.dev. source
Wasabi Hot Cloud Storage B
Wasabi Technologies LLC
Presigned PUT URLs and S3 multipart through standard AWS SDKs keep bytes out of the model, and Wasabi documents MD5 and CRC checksums on upload. source

Does the job, with a limit 1

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Box API + MCP B
Box, Inc.
Chunked upload sessions over REST, and the MCP's get_upload_url keeps bytes out of the model, but that tool is off until an admin enables it and works only in code-executing clients. acc-08 saw binary passed as text corrupted. source

Doesn't do this job 1

Listings in the category that do something else, with the reason.

ListingWhy
ONLYOFFICE Apps MCP Server D
Ascensio System SIA
upload_file accepts only txt and md, so a binary such as a PDF or deck can't be stored byte-for-byte through the server. source

What stops agents finishing

  • the only MCP upload takes base64 or text in the tool argument
  • the HTTP transport caps the request body below the documented upload limit
  • the sandbox cannot reach or see the URL the tool returns

Around it

Before: code-sandboxes.run, mailbox-access.get-attachment. After: file-storage.share-temp-link.

Where this comes from

Weight 17 of 100 in File storage & sharing: 6 of 36 links; MCP server issues on Box, B2 and Microsoft Graph

The same as data: /api/v1/use-cases/file-storage.agent-upload.json, or the MCP tool get_use_case with id file-storage.agent-upload. Other jobs in this category: /api/v1/niches?category=file-storage.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.