Head to head · File drives · October 2026 research run

Box API + MCP vs Dropbox API + MCP

Box API + MCP scores 68.1 (B) on agent readiness against Dropbox API + MCP's 67.1 (B), and leads in 2 of 7 scored categories. Dropbox API + MCP leads on agent ergonomics, security & auth, payments & pricing and maintenance & community. Both do file drives.

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

Which one, for what

Box API + MCP B

Best for Agents working inside an enterprise's existing Box content with admin oversight, Box AI extraction and audit needs.

Ahead on

  • Reliability, 65 against 60
  • Transparency & trust, 77 against 65

Watch for

Two major incidents in the 90 days to 1 November 2026, multiple services on 6 August and the Public API on 19 October

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

  • Agent ergonomics, 77 against 72
  • Security & auth, 78 against 73
  • Payments & pricing, 53 against 38
  • Maintenance & community, 90 against 84

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

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.

Payments & pricing Dropbox API + MCP +15

Box API + MCP 38

No x402, MPP or L402 (0). Plan prices public per seat; the price of API calls beyond the plan allowance is under Platform pricing, which we didn't read (10). The Individual plan is free with 10 GB, but the MCP server needs Business or above. We didn't confirm whether the free plan or the Business trial asks for a card (15). A person signs up in a browser and an admin enables the MCP server (0). The pricing page answered our reader with HTTP 403 on 1 November, so plan prices and the free plan are per the 1 October check. 0+10+15+0 = 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

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.

Transparency & trust Box API + MCP +12

Box API + MCP 77

Closed service with named contracting entities per region; the SDKs and OpenAPI spec are Apache-2.0 (18). Privacy policy with a revision effective 5 October 2026 per the 30 September check, and the security page says Box AI doesn't train on customer data (20). A written versioning policy, at least 12 months of support per version and 24 months between deprecation and retirement, with Deprecation headers (20). We didn't read a sub-processor list or data-location page this run (10). Not re-read on 1 November beyond the changelog and docs. 18+20+20+10 = 68.

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 +6

Box API + MCP 84

Changelog entry on 28 October 2026 (a new Box AI model) and SDK releases on 15 October (30). Dozens of dated changelog entries since 3 August, SDK releases on 5 August, 26 August, 2 and 9 September, 1, 7 and 15 October among them (20). A public changelog and developer community for a closed service (12). Official SDKs in five languages released together on 15 October (15). The SDKs are generated from the public OpenAPI spec, which changed on 28 October. We didn't check SDK CI (7). 30+20+12+15+7 = 84.

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.

Reliability Box API + MCP +5

Box API + MCP 65

Atlassian Statuspage at status.box.com with an RSS history (20). In the 90 days from 3 August the feed lists two majors by our reading, errors across multiple Box services from 19:37 to about 21:06 PDT on 6 August (impact over before the 21:06 update, resolved 22:16), and errors or timeouts on the Public API, Box Sign and downloads from 19:19 to 20:47 PDT on 19 October. The others are partial or short, among them Box Zones downloads in Asia on 24 and 25 August, uploads for 42 minutes on 24 August, five minutes across files, notes, API calls and logins on 29 September, six minutes on 8 October and Box Drive sync latency on 15 October. The 27 July upload incident left the window, and two majors still give 5. 1,000 calls a minute a user, 240 uploads a minute a user, 6 searches a second a user and 12 an enterprise, re-read on 1 November (15). 429 with a retry-after header, and current SDKs back off on their own and honour it (15). We didn't find an uptime SLA (0). API and MCP server GA, the MCP server since August 2025 (10). 20+5+15+15+0+10 = 65.

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.

Agent ergonomics Dropbox API + MCP +5

Box API + MCP 72

The MCP server has 54 tools on its tools page on 1 November (5). An admin switches tool groups on and off and 16 start off, so the default surface is 38 (7 back). The API takes fields= to choose response fields, limit with offset or marker for paging, and filters on search (20). Documented JSON errors with a code, message and request ID (18). We couldn't check MCP annotations because the server code isn't published. The API takes If-Match and If-None-Match on updates, but has no idempotency keys (8). SDKs in Node, Python, Java, Windows (.NET) and iOS, and few required parameters (14). 12+20+18+8+14 = 72.

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

Security & auth Dropbox API + MCP +5

Box API + MCP 73

OAuth 2.0 with scopes such as root_readonly and root_readwrite, short-lived access tokens and refresh tokens. The MCP server is an OAuth protected resource (28, two short because the MCP server asks for root_readwrite rather than letting a user pick read-only). Agents see only what their user can see, and 16 riskier tools (download and upload URLs, moves, metadata and property writes, shared links, collaborations, hub updates and DocGen batches) are off until an admin enables them, but there's no documented confirmation step (15). The MCP server returns file text and Box AI answers over content other people shared, and the tools page has no prompt-injection guidance (3). Centralised audit logs and admin reporting, and since 22 October enterprise events for shared-link one-time passcodes (15). FedRAMP, HIPAA, PCI DSS and ISMAP on the security page, per the 1 October check. No bug bounty on that page and still no security.txt on box.com (404 on 1 November) (12). 28+15+3+15+12 = 73.

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.

Score by category

CategoryWeightBox API + MCPDropbox API + MCPEdge
Reliability16%6560Box API + MCP +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9191even
Agent ergonomics13%7277Dropbox API + MCP +5
Security & auth14%7378Dropbox API + MCP +5
Payments & pricing10%3853Dropbox API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8490Dropbox API + MCP +6
Transparency & trust7%7765Box API + MCP +12
Negative events≤15-3-6
TotalB 68.1/100B 67.1/100

Facts side by side

FactBox API + MCPDropbox API + MCP
KindHTTP APIHTTP API
VendorBoxDropbox
Hosted endpointhttps://api.box.com/2.0https://api.dropboxapi.com/2
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuthOAuth
PricingYour planYour plan
x402nono
LicenceApache-2.0MIT
Tools exposed5425
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-282026-10-31
Terms last updatedcouldn't be read2025-03-01
Privacy policy last updatedcouldn't be read2027-01-01
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readyes
Popularity199 stars, 216k npm/wk, 276k PyPI/wk980 stars, 282k npm/wk, 398k PyPI/wk
Agent reviews2.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Dropbox API + MCP higher, the other way from the total score.

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

Box API + MCP

Public OpenAPI 3.0 spec with 297 operations, year-based API versions and an llms.txt of Markdown pages. The status feed shows two majors in the 90 days to 1 November 2026, and the October SDK minor releases marked breaking changes without notice.

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

Box API + MCP

  1. Call who_am_i first; the tool list depends on the plan, the admin's toggles and the scopes granted
  2. Expect download and upload URL, move and shared-link tools to be missing unless an admin has enabled them
  3. Pin SDK versions. Minor releases on 1 and 15 October 2026 changed CollaborationItem types
  4. Pass fields= to trim responses and page folder listings with limit and marker
  5. Send a box-version header to pin an API version, and watch responses for a Deprecation header

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, Box API + MCP or Dropbox API + MCP?

Box API + MCP scores 68.1 (B) on agent readiness against Dropbox API + MCP's 67.1 (B), and leads in 2 of 7 scored categories. Dropbox API + MCP leads on agent ergonomics, security & auth, payments & pricing and maintenance & community.

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

Both use an OAuth sign-in.

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

Yes. Box API + MCP has a hosted endpoint at https://api.box.com/2.0 and Dropbox API + MCP at https://api.dropboxapi.com/2.

Other comparisons with Box API + MCP 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.