Cloudflare R2 vs Dropbox API + MCP

Cloudflare R2

Free egress and a free tier of 10 GB-month plus 1 million writes a month. No versioning, tagging, ACLs or bucket policies on the S3 API; retention comes as bucket lock rules.

Dropbox API + MCP

Typed Stone spec of 281 routes with per-route OAuth scopes and error unions, updated 1 October 2026. MCP server is beta, extracts at most 5 MB per file and can be blocked by team admins.

Cloudflare R2

1. Set region to auto and the endpoint to https://<account-id>.r2.cloudflarestorage.com. us-east-1 also works, other region names fail
2. Ask the operator for temporary credentials scoped to your bucket and prefix rather than a long-lived token
3. For public reads put a custom domain or an r2.dev subdomain on the bucket; presigned URLs only sign the S3 hostname
4. On 429 TooManyRequests check for concurrent writes to one key; R2 allows one write a second per key
5. Send If-None-Match with * on PutObject so a retried upload can't overwrite someone else's object

Dropbox API + MCP

1. Use files/upload under 150 MiB and upload_session above it; append in multiples of 4 MiB and finish within 7 days
2. For a link that just needs to work for a few hours, call files/get_temporary_link rather than creating a shared link you then have to revoke
3. Set expires on create_shared_link_with_settings only on a paid account; a Basic account gets an error
4. Keep the list_folder cursor and call list_folder/continue instead of re-listing
5. On a rate-limit error wait retry_after seconds; too_many_write_operations means write contention, so serialise writes