Dropbox API + MCP vs Tigris

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.

Tigris

No egress fees, and one endpoint (t3.storage.dev) with region auto for every location. 16 status incidents between 4 July and 2 October 2026, including outages in US regions on 31 July and 2 August.

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

Tigris

1. Point the AWS SDK at https://t3.storage.dev with region auto; the stdio MCP README still shows the older fly.storage.tigris.dev endpoint
2. Ask for an access key with a ReadOnly or ReadWrite role on one bucket rather than an org-wide key
3. Keep presigned URLs short; Tigris accepts up to 90 days
4. Don't call tigris_list_objects on a large bucket; it walks every object with no limit or prefix
5. Use @tigrisdata/iam 2.6.0 or later before writing policies with conditions