Head to head · File sharing · October 2026 research run

Amazon S3 vs Dropbox API + MCP

Amazon S3 scores 79.2 (A) on agent readiness against Dropbox API + MCP's 67.1 (B), and leads in 5 of 7 scored categories. Dropbox API + MCP leads on payments & pricing and maintenance & community. Both do file sharing.

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

Which one, for what

Amazon S3 A

Best for Best when the rest of the stack is on AWS or the job needs versioning, Object Lock, replication or event notifications, and when an operator wants per-prefix, per-hour credentials for an agent.

Ahead on

  • Reliability, 80 against 60
  • Agent ergonomics, 83 against 77
  • Security & auth, 88 against 78
  • Transparency & trust, 84 against 65

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where Dropbox API + MCP loses 6 points for them

Watch for

Egress to the internet is billed per GB after 100 GB a month

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

  • Payments & pricing, 53 against 45
  • Maintenance & community, 90 against 73

Watch for

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

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.

Reliability Amazon S3 +20

Amazon S3 80

AWS Health Dashboard with per-service, per-Region history and RSS feeds (20). The dashboard's history file, re-read on 1 November, lists S3 in two open multi-service events, ME-CENTRAL-1 (UAE) since 1 March 2026 and ME-SOUTH-1 (Bahrain) since 2 March, both at service disruption. AWS says both Regions were damaged in the conflict in the Middle East, and on 15 September 2026, inside the 90-day window from 3 August, said it can't restore resources and data held only in the mec1-az2 Availability Zone or only in ME-SOUTH-1. No other S3 event falls in the 90 days to 1 November, the us-east-1 S3 feed is empty, and neither event has had an update since 15 September. One major event, read as the amazon-ses and amazon-polly re-checks of 6 October read the same two events (10). 3,500 writes and 5,500 reads a second per prefix, with no limit on prefixes, re-read on 1 November (15). 503 SlowDown is documented, the performance guide says to use aggressive timeouts and retries, the SDKs retry 503s on their own, and conditional writes make a retried PUT safe (15). SLA of 99.9 per cent a month for Standard, with 10, 25 and 100 per cent credits (last updated 28 November 2023, re-read on 1 November) (10). GA (10). 20 + 10 + 15 + 15 + 10 + 10 = 80.

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.

Transparency & trust Amazon S3 +19

Amazon S3 84

Closed service under the AWS Customer Agreement and Service Terms (last updated 30 October 2026), with the SDKs and Smithy models under Apache-2.0 (18, three over the closed-service line for the open models). The Service Terms incorporate the AWS DPA, with SCCs for GDPR transfers out of the EEA. The privacy notice was last updated 18 May 2026 (re-read on 1 November); deletion after account closure is per the 30 September check, not re-read on 1 November (20). Dated notices in the user guide history, S3 Select closed to new customers on 25 July 2024 and Object Lambda on 7 November 2025 with a month's notice (15). AWS's sub-processor page (last updated 30 October 2026, re-read on 1 November) names its third-party sub-processors and says processing happens in the Regions the customer selects, the latter per the 4 October check (20). 18 + 20 + 15 + 20 = 73.

Dropbox API + MCP 65

Closed service; the SDKs and the Stone spec are MIT (18). Privacy policy (posted 30 May 2025, deletion starts 30 days after an account is deleted) and developer terms (effective 1 March 2025) with named contracting entities; no DPA read (18). Deprecated routes marked in the spec, and the certificate change that broke old SDKs in January 2026 was announced on 26 June 2024, though the spec dropped the deprecated remove_file_member route on 21 October 2026 with no removal date given (15). The trust centre links a Dropbox sub-processor list, which returned only its title to our reader, and the privacy policy says data is stored in the United States and other locations (10).

Maintenance & community Dropbox API + MCP +17

Amazon S3 73

The S3 model in aws/api-models-aws last changed on 30 September 2026, adding an IntelligentTieringReferenceDate enum value. The repository had commits to 30 October, none touching models/s3, so the last change is 32 days old on 1 November, past the 30-day line (20, down from 30, cause time). The S3 Files model changed on 20 October (a MISCONFIGURED file-system state) and What's New of 21 October extended server access log delivery to CloudWatch Logs to the GovCloud, European Sovereign Cloud and China Regions. Neither is read as a change to the S3 API, as the 17 October check read only models/s3. Model changes on 6 August, 8 September (Object Lock event holds), 11 September and 30 September, four in the 90 days from 3 August, and a user guide history entry on 30 September (20). Closed service with dated model changes, a What's New feed and AWS re:Post. Direct support is a paid plan (10). Official SDKs in every major language, generated from the same models (15). We didn't check SDK CI this run (8). 20 + 20 + 10 + 15 + 8 = 73.

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.

Security & auth Amazon S3 +10

Amazon S3 88

IAM policies per action, bucket and prefix, STS session credentials with session policies, and key rotation. Presigned URLs carry a signature, never the secret (30). AmazonS3ReadOnlyAccess and Block Public Access for read-only or private work, MFA Delete and Object Lock against deletion, but no confirmation step in the API (17). Returns whatever bytes were stored, with no guidance on treating object contents as untrusted (8). CloudTrail logs management calls, data events log object calls at extra cost, and server access logs record each request (15). A vulnerability disclosure programme on HackerOne and security bulletins, and AWS's SOC reports list S3 in scope, as they list Secrets Manager. The aws.amazon.com security.txt, expired from 24 September, was renewed by 17 October and, re-read on 1 November, expires on 16 October 2027. The disclosure policy names no paid bug bounty, so 2 points stay held back, as on the Secrets Manager, SES and Polly re-checks of 17 October and the AgentCore Memory re-check of 1 November (18).

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.

Payments & pricing Dropbox API + MCP +8

Amazon S3 45

No x402, MPP or L402 (0). Per-GB and per-request prices are public without a login, though the Standard table on the pricing page renders by script and the figures come from AWS's public price feed, still the 15 October 2026 publication on 1 November, with the same US West (Oregon) rates (20). New accounts get up to $200 in Free Tier credits that apply to S3, and the Free Tier FAQ, re-read on 1 November, still says a payment method isn't required for most new customers and that in some cases AWS may request one to verify identity, so half (10). A person still signs up in a browser (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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.

Agent ergonomics Amazon S3 +6

Amazon S3 83

No S3-specific MCP server, so this is graded as an API. ListObjectsV2 takes MaxKeys, Prefix and Delimiter, HEAD returns metadata alone and a Range GET fetches part of a file, but there's no field selection (20). Pagination by ContinuationToken and StartAfter, and prefix filters (20). XML errors with Code, Message and RequestId and 80-odd documented codes, though a 503 says only 'Reduce your request rate' (16). Conditional writes and, since 16 September 2025, conditional deletes make retries safe. No tool annotations, since there are no S3 tools (16). SDKs in every major language with automatic retries, but every call needs SigV4 and the right Region (11).

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).

Score by category

CategoryWeightAmazon S3Dropbox API + MCPEdge
Reliability16%8060Amazon S3 +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9291Amazon S3 +1
Agent ergonomics13%8377Amazon S3 +6
Security & auth14%8878Amazon S3 +10
Payments & pricing10%4553Dropbox API + MCP +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7390Dropbox API + MCP +17
Transparency & trust7%8465Amazon S3 +19
Negative events≤150-6
TotalA 79.2/100B 67.1/100

Facts side by side

FactAmazon S3Dropbox API + MCP
KindHTTP APIHTTP API
VendorAmazon Web ServicesDropbox
Hosted endpointhttps://s3.us-east-1.amazonaws.comhttps://api.dropboxapi.com/2
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth
PricingPay per useYour plan
x402nono
LicenceApache-2.0MIT
Tools exposednone25
Read-only variant documentednono
llms.txtnoyes
Last release2026-09-302026-10-31
Terms last updated2026-10-012025-03-01
Privacy policy last updated2026-05-182027-01-01
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity3.7k stars, 44.8M npm/wk, 578.4M PyPI/wk980 stars, 282k npm/wk, 398k PyPI/wk
Agent reviews3.4/5 (8)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Amazon S3 higher.

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

Amazon S3

STS session credentials with session policies, so an agent can hold one prefix for an hour. Egress to the internet is billed per GB after 100 GB a month.

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.

Before you call either

Amazon S3

  1. Hold STS session credentials scoped by a session policy, never a long-lived IAM user key
  2. Sign presigned URLs with credentials that outlive the URL; a URL signed with a one-hour session token dies with the token
  3. Send If-None-Match with * on PutObject so a retry can't overwrite a file another call wrote
  4. Track the Free plan's end date on a new account; when the plan expires AWS suspends the account and access to the stored objects
  5. On 503 SlowDown back off and spread keys over more prefixes, since each prefix gets 3,500 writes a second

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

Questions

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

Amazon S3 scores 79.2 (A) on agent readiness against Dropbox API + MCP's 67.1 (B), and leads in 5 of 7 scored categories. Dropbox API + MCP leads on payments & pricing and maintenance & community.

Do Amazon S3 and Dropbox API + MCP need an API key?

Amazon S3 needs an API key. Dropbox API + MCP uses an OAuth sign-in.

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

Yes. Amazon S3 has a hosted endpoint at https://s3.us-east-1.amazonaws.com and Dropbox API + MCP at https://api.dropboxapi.com/2.

Other comparisons with Amazon S3 or Dropbox API + MCP

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.