Head to head · File sharing · October 2026 research run

Dropbox API + MCP vs Tigris

Dropbox API + MCP scores 67.1 (B) on agent readiness against Tigris's 58.7 (C), and leads in 4 of 7 scored categories. Tigris leads on reliability and payments & pricing. Both do file sharing.

Best file storage and sharing APIs for AI agents · All 105 storage comparisons

Which one, for what

Dropbox API + MCP B

Best for An agent acting on a person's or team's existing Dropbox files, especially a solo user on the free plan.

Ahead on

  • Schema & documentation, 91 against 54
  • Agent ergonomics, 77 against 53
  • Security & auth, 78 against 57
  • Maintenance & community, 90 against 77

Watch for

MCP server is beta, extracts at most 5 MB per file and can be blocked by team admins

Tigris C

Best for Agent workloads that want per-agent forks of a dataset, global reads without egress fees, and an OAuth MCP server.

Ahead on

  • Reliability, 72 against 60
  • Payments & pricing, 60 against 53

Also in its favour

  • Runs on your own machine

Watch for

No documented rate limits; retry guidance appears only in the storage SDK's changelog

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Dropbox API + MCP +37

Dropbox API + MCP 91

No OpenAPI, but the whole API is a public Stone spec, 276 routes with typed arguments, results and error unions, updated by a bot on 31 October 2026 (25). Docs at docs.dropboxapi.com with llms.txt indexes and a Markdown version of any page (10). Route descriptions say what a call does and how it fails, download_transform_output for example names the errors for an expired or foreign handle (16). Typed fields with length limits and unions in place of free-form JSON (15). 173 examples in files.stone alone and a typed error for every route (15). API v2, deprecated routes marked in the spec, but no human-written changelog beyond the developer blog (10).

Tigris 54

No OpenAPI. The S3 API compatibility page sets Tigris against AWS's S3 operations, so the AWS model is the contract by compatibility, as for wasabi (12). llms.txt with Markdown pages (10). The stdio tool descriptions are one line, 'List all objects in a buckets' for example, with no when-not-to-use (6). String inputs with required fields, no enums or bounds (8). Examples in the docs and a 412 response on the conditional operations page, but no error reference (6). A dated product changelog at /docs/changelog/ with monthly entries (30 June, 31 July, 31 August and 30 September 2026), and changeset changelogs in the SDKs. The S3 API itself carries no version, as for bunny-storage (12). 12 + 10 + 6 + 8 + 6 + 12 = 54.

Agent ergonomics Dropbox API + MCP +24

Dropbox API + MCP 77

About 25 MCP tools, with no toolsets or read-only subset we could find (15). list_folder takes a limit and returns a cursor for list_folder/continue, and search takes max_results (20). Typed error tags such as path/not_found and retry_after an agent can act on (18). Upload sessions resume by offset, and writes can be conditional on a revision; MCP annotations unchecked (12). Official SDKs in Python, JavaScript, Java, .NET and Swift, but content endpoints take their arguments in a Dropbox-API-Arg header (12).

Tigris 53

The stdio MCP server has 10 compact tools, but tigris_list_objects pages through a whole bucket with no limit or prefix (20). The S3 API pages and filters; the MCP list tool doesn't (10). No documented error codes or recovery guidance (5). No readOnlyHint or destructiveHint on the stdio tools in 1.14.1, and the hosted server's definitions aren't published (5). One endpoint and region auto for every location, and official SDKs in TypeScript and Go (13). 20 + 10 + 5 + 5 + 13 = 53.

Security & auth Dropbox API + MCP +21

Dropbox API + MCP 78

OAuth 2.0 with granular scopes per route (files.metadata.read, files.content.write, sharing.write and so on), short-lived access tokens with refresh tokens, and App folder apps limited to one folder (30). Read-only scopes and App folder access, and team admins can block app connections, but no documented confirmation for deletes (15). The MCP server reads file contents from shared folders into the model, and we found no prompt-injection guidance (3). Business teams get an audit log through the team_log routes; personal accounts see linked apps only (12). A paid bug bounty and a separate disclosure programme on Intigriti, named in www.dropbox.com/.well-known/security.txt, which lacks the RFC 9116 Contact and Expires fields. The trust centre lists Dropbox SOC 1, 2 and 3 reports for October 2024 to September 2025 and ISO 27001, 27017, 27018, 27701 and 22301 certificates (18 of 20, as dropbox-sign on the same programme). The 1 October note of 13 hadn't read the certifications.

Tigris 57

Access keys scoped per bucket with ReadOnly, ReadWrite or Editor roles and IAM policies with conditions, revocable and rotatable through the IAM API. No STS or expiring keys, so every key lives until revoked (25). A ReadOnly role and bucket soft delete, but no read-only MCP mode or delete confirmation documented (12). Returns stored bytes, with no guidance on treating them as untrusted (8). No audit log found (0). security.txt at www.tigrisdata.com/.well-known/ (Expires 2027-10-26) and a Report a Vulnerability page (security@tigrisdata.com, acknowledgement 'within a reasonable time', no paid bounty), with a MinIO migration guide that says Tigris is SOC 2 Type II and HIPAA compliant. No report or trust page found. 12, as chroma's SOC 2 Type II claim with a reporting route. 25 + 12 + 8 + 0 + 12 = 57.

Maintenance & community Dropbox API + MCP +13

Dropbox API + MCP 90

Spec updated by a bot on 31 October 2026 and Python SDK v12.2.4 tagged on 22 October 2026 (30). In the 90 days from 3 August, 32 spec updates and four SDK tags, Python v12.2.2 (22 September), v12.2.3 (7 October) and v12.2.4 (22 October) and JavaScript v10.47.0 (22 September) (20). SDK repositories merge the automated spec updates within a day, and the docs point developers to the Dropbox Developer Forum (15). Official SDKs in five languages, current (15). CI, CodeQL and coverage workflows on the Python SDK (10). The JavaScript repository's package.json reaches 10.64.0, but its release workflow tags each release and the newest tag is v10.47.0; npm couldn't be read.

Tigris 77

@tigrisdata/storage 3.23.0 on 8 October 2026 (purgeBucket for soft-deleted buckets), 28 days before this check, and the official CLI 3.17.2 on 3 November 2026 (command outcomes in its usage analytics) (30). In the 90 days from 7 August, five storage releases (3.19.0 and 3.20.0 on 26 August, 3.21.0 on 1 September, 3.22.0 on 30 September, 3.23.0 on 8 October) and product changelog entries on 31 August and 30 September (20). Pull requests merged daily, but external issue replies aren't visible from git (12). Current official SDKs, but the stdio MCP server's only release since November 2025, 1.14.1 on 16 October 2026, updates dependencies, and no registry entry was read (7, held). Renovate and CI in the monorepo (8). 30 + 20 + 12 + 7 + 8 = 77.

Reliability Tigris +12

Dropbox API + MCP 60

Statuspage at status.dropbox.com with 12 components, the API and the MCP Server among them (20). history.atom, read on 1 November 2026, covers the 90 days from 3 August. One incident touches the API, "Dropbox is not working as expected for some users" on 21 August 2026 (13:18 to 15:12 UTC, Desktop Application, Mobile Application and API), partial and so minor. Website routes for some customers on 9 September, telephone support during an AWS outage on 3 and 4 September and Dropbox Protect on 25 and 26 August don't touch the API, and the 22 September and 13 October windows were announced maintenance. Minor incidents only (20). The performance guide says "Dropbox does not publish exact rate limits" (0). The guide says rate-limited responses always carry Retry-After in seconds and that the retries count against the limit, the error guide gives exponential backoff when the header is missing, and too_many_write_operations flags namespace write contention (15). No SLA found (0). The API is GA and the MCP server in open beta per its help page, updated 30 September 2026 (5). The 1 October reading of 12 rested on a window we could only partly read.

Tigris 72

Status page on incident.io with per-region components (20). On 5 November the page's 90-day view and its feed list three incidents since 7 August, each scoped to regions, so read as minor. Tokyo latency on 13 August, performance in Ashburn and San Jose on 22 October, and failed requests and latency in US East on 23 October from 18:39 to 19:40 UTC. The 31 July and 2 August outages have left the window, and incidents the 1 October reading listed up to 2 October no longer appear (20). No rate limits found in the docs or their llms.txt (0). The storage SDK's 3.19.0 changelog entry (26 August 2026) documents opt-in retries that honour Retry-After with exponential backoff on 408, 429 and 5xx, and re-send writes after a status but not after a transport failure. No idempotency keys (12). An SLA, last updated 10 August 2026, commits to 99.9 per cent a month for Standard and Archive and 99.0 per cent for Infrequent Access, with credits of 10 to 30 per cent (10). The S3 API is GA (10). 20 + 20 + 0 + 12 + 10 + 10 = 72.

Payments & pricing Tigris +7

Dropbox API + MCP 53

No x402, MPP or L402 (0). The API and MCP server cost nothing beyond the account's plan, and plan prices are public (15). A free Basic account works with the API and the MCP server (20). A person signs in through OAuth, and production apps need Dropbox's approval (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Tigris 60

No x402, MPP or L402 (0). Per-GB and per-request prices public without a login, re-read on 5 November (20). A free 5 GB, 10,000 Class A and 100,000 Class B requests a month, and the pricing page says 'No card to start' (20). A person signs up in a browser (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Score by category

CategoryWeightDropbox API + MCPTigrisEdge
Reliability16%6072Tigris +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9154Dropbox API + MCP +37
Agent ergonomics13%7753Dropbox API + MCP +24
Security & auth14%7857Dropbox API + MCP +21
Payments & pricing10%5360Tigris +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9077Dropbox API + MCP +13
Transparency & trust7%6565even
Negative events≤15-6-3
TotalB 67.1/100C 58.7/100

Facts side by side

FactDropbox API + MCPTigris
KindHTTP APIHTTP API
VendorDropboxTigris Data
Hosted endpointhttps://api.dropboxapi.com/2https://t3.storage.dev
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuthOAuth or key
PricingYour planFreemium
x402nono
LicenceMITMIT
Tools exposed25none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-312026-10-08
Terms last updated2025-03-01couldn't be read
Privacy policy last updated2027-01-01couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity980 stars, 282k npm/wk, 398k PyPI/wk4 stars, 20 npm/wk
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Dropbox API + MCP

Typed Stone spec of 276 routes with per-route OAuth scopes and error unions, updated 31 October 2026, and a paid bug bounty with SOC 2 and ISO 27001 reports. No numeric rate limits are published, the MCP server is still beta, and October patch releases of the Python SDK removed public methods without dated notice.

Tigris

No egress fees, one endpoint (t3.storage.dev) with region auto for every location, and a published 99.9 per cent SLA. No rate limits or audit logs are documented, access keys never expire, and storage SDK 3.17.1 removed a documented mergeFork option in a patch release without notice.

Before you call either

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. On a 429 wait the Retry-After seconds; too_many_write_operations means write contention, so serialise writes to the namespace
  5. Pin the dropbox Python package and use v12.2.4 or later if you pass scope= to Dropbox(); earlier versions widened the token on refresh

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. Set retry in @tigrisdata/storage 3.19.0 or later, which is off by default, and use @tigrisdata/iam 2.6.0 or later for policies with conditions

Questions

Which is better for AI agents, Dropbox API + MCP or Tigris?

Dropbox API + MCP scores 67.1 (B) on agent readiness against Tigris's 58.7 (C), and leads in 4 of 7 scored categories. Tigris leads on reliability and payments & pricing.

Do Dropbox API + MCP and Tigris need an API key?

Dropbox API + MCP uses an OAuth sign-in. Tigris takes an API key or an OAuth sign-in.

Can an agent call Dropbox API + MCP and Tigris without installing anything?

Yes. Dropbox API + MCP has a hosted endpoint at https://api.dropboxapi.com/2 and Tigris at https://t3.storage.dev.

Other comparisons with Dropbox API + MCP or Tigris

Machine-readable

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.