Head to head · File drives · October 2026 research run

Dropbox API + MCP vs Google Drive API + MCP

Google Drive API + MCP scores 77.8 (BB) on agent readiness against Dropbox API + MCP's 67.1 (B), and leads in 4 of 7 scored categories. Dropbox API + MCP leads on maintenance & community. Both do file drives.

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

  • Maintenance & community, 90 against 85

Watch for

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

Google Drive API + MCP BB

Best for Agents working on files that people already keep in Drive, inside a Workspace organisation with admin controls.

Ahead on

  • Reliability, 70 against 60
  • Agent ergonomics, 87 against 77
  • Security & auth, 83 against 78
  • Transparency & trust, 75 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

OAuth consent, scope verification and a Cloud project before an agent can list a folder

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 Google Drive API + MCP +10

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.

Google Drive API + MCP 70

Google Workspace Status Dashboard with an incidents JSON going back to 5 November 2025, re-read on 1 November (20). In the 90 days from 3 August the feed has two Drive service disruptions and nothing posted after 25 September. From 18 August 16:58 to 19 August 05:40 PDT, 12 hours 42 minutes, Drive users in Australia, the Philippines and New Zealand had severe latency, loading failures and 502 errors after a traffic attribution misconfiguration in Google's regional load balancing, and the report says customers outside those regions were largely unaffected. On 16 September a capacity test dropped a subset of Drive traffic for 39 minutes (07:03 to 07:43 PDT in the final report). The first hit every Drive user in one region with wide errors for over an hour, so it stays one regional major, as the 17 October check read it and as the 4 October S3 check and temporal's 10 September incident were read. Single-region incidents that hit only some customers, such as Twilio's Australia 503s and Backblaze's EU upload failures, were read as partial on 1 November (10). The dashboard tracks the Drive product, not the API alone. Quotas published in units, 1,000,000 a minute a project and 325,000 a minute a user, with 400,000,000 units and 1 TB of egress a day a project before charges apply, on the limits page re-read on 1 November (15). The error guide and the limits page say to retry 429, 5xx and some 403s with truncated exponential backoff, and resumable uploads can pick up after a failure (15). The Workspace SLA (last modified 31 August 2026, re-read on 1 November) covers Google Drive at 99.9 per cent but doesn't name the API, and it measures Downtime as a user error rate above 5 per cent in the user web interface (5). The API is GA, the MCP server Developer Preview (5). 20+10+15+15+5+5 = 70.

Agent ergonomics Google Drive API + MCP +10

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

Google Drive API + MCP 87

The API takes fields= for partial responses and pageSize. The MCP server's eight tools came to 37,716 bytes of compact JSON in tools/list on 1 November, output schemas included (about 27 KB on 17 October), with snippetVerbosity and excludeContentSnippets to shrink responses. That still sits below Sheets (six tools, 39,409 bytes, 22) and Gmail (23 tools, about 79 KB, 20) (23 of 25). pageToken paging and the q search syntax for filters (20). Error reasons an agent can act on, storageQuotaExceeded against userRateLimitExceeded for example (18). All eight MCP tools carry readOnlyHint, destructiveHint and idempotentHint, with six read-only, and resumable uploads survive a dropped connection for a week, but there are no idempotency keys, so a retried create_file or copy_file can duplicate. Read as for People (14 of 20). Client libraries in the main languages, few required parameters, but an OAuth client and Cloud project come first (12). 23+20+18+14+12 = 87.

Transparency & trust Google Drive API + MCP +10

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

Google Drive API + MCP 75

Closed service under the Google APIs Terms (last modified 9 November 2021, re-read on 1 November); client libraries Apache-2.0 (18). The Google privacy policy, effective 16 October 2026, covers end users. Workspace customers are covered by the Cloud Data Processing Addendum (last modified 30 October 2026 when read on 1 November), which still commits Google to delete customer data within a maximum period of 180 days. We found no retention statement specific to Drive API data (18). Dated deprecations and notices in the release notes, enforceExpansiveAccess on 25 February 2026 and the 12 October 2026 notice that Workspace MCP servers reject OAuth clients not marked as agentic from 11 November, but no stated deprecation notice period, and the API terms let Google discontinue an API at any time (14). The Workspace subprocessor list, last modified 19 October 2026 when read on 1 November, gives the activity and processing countries of each third party (14 in its core table) and of Google's affiliates for all Workspace Core Services, and data regions exist for some plans; the list covers Workspace customers, not personal accounts, which we read the same way as for Calendar (20).

Security & auth Google Drive API + MCP +5

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.

Google Drive API + MCP 83

OAuth 2.0 with granular scopes; drive.file limits an app to files it created or the user picked, and the full drive scope needs Google's verification. Tokens are short-lived and revocable (30), less 10 because the Drive v3 discovery document (revision 20261028) lists access_token, oauth_token and key as query parameters and Google's OAuth web-server guide shows a Drive call with ?access_token= as an alternative to the header. On 1 November files.list with no token answered 403 for an unregistered caller and with a made-up ?access_token= answered 401 for invalid credentials, so the API reads the token from the URL, read as for Gmail, Sheets and Calendar (20). drive.readonly for reading, the MCP server has no delete or share tool, and Workspace admins can restrict API access per app (18). The MCP setup page, updated 12 October 2026, warns about indirect prompt injection and says operators must screen prompts and responses with Model Armor or a documented alternative, and the Workspace MCP security page gives a Model Armor floor setting that inspects and blocks Google MCP server traffic. Read as for Calendar, Gmail and Sheets (12). Drive log events record view, edit, download, delete and other actions, and for third-party apps the OAuth client ID and app name, with the API method on download and content-access events, re-read on 1 November. This is a Workspace admin log, and no per-call log for personal accounts was found in the reviewed documentation (13). Google's Vulnerability Reward Program and a security.txt valid to 1 April 2030, and Google's SOC 2 page, which lists the Google Drive Rest API among the products in the Workspace reports' scope, all re-read on 1 November (20). 20+18+12+13+20 = 83.

Maintenance & community Dropbox API + MCP +5

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.

Google Drive API + MCP 85

The official @googleapis/drive 27.0.0, published on 19 October 2026 as a breaking major that drops the read-only marks on five Approval fields after a Drive discovery update, is the newest in the client changelog and package.json on 1 November. The newest Drive entry in the release notes is still the 12 October 2026 announcement that Drive MCP clients must be marked as AI-powered agents (30). In the 90 days from 3 August the Python client shipped v2.199.0, v2.200.0 and v2.201.0 (20 August, 31 August and 29 September in its changelog), @googleapis/drive shipped versions from 23.0.0 on 9 September to 27.0.0, and the release notes have entries on 2 September and 12 October (20). Dated release notes and Google's public issue tracker; we didn't sample replies (12). Official client libraries in the main languages, current (15). Client libraries regenerate from discovery on a schedule, and the Python client runs a GitHub Actions workflow whose pass state we didn't check (8).

Score by category

CategoryWeightDropbox API + MCPGoogle Drive API + MCPEdge
Reliability16%6070Google Drive API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9189Dropbox API + MCP +2
Agent ergonomics13%7787Google Drive API + MCP +10
Security & auth14%7883Google Drive API + MCP +5
Payments & pricing10%5353even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9085Dropbox API + MCP +5
Transparency & trust7%6575Google Drive API + MCP +10
Negative events≤15-60
TotalB 67.1/100BB 77.8/100

Facts side by side

FactDropbox API + MCPGoogle Drive API + MCP
KindHTTP APIHTTP API
VendorDropboxGoogle
Hosted endpointhttps://api.dropboxapi.com/2https://www.googleapis.com/drive/v3
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuthOAuth
PricingYour planFree
x402nono
LicenceMITApache-2.0
Tools exposed258
Read-only variant documentednoyes
llms.txtyesno
Last release2026-10-312026-10-19
Terms last updated2025-03-012021-11-09
Privacy policy last updated2027-01-012026-10-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity980 stars, 282k npm/wk, 398k PyPI/wk12k stars, 1.3M npm/wk, 29.8M PyPI/wk
Agent reviews3/5 (2)3.4/5 (8)

The panel on both

One of the 2 reviewers who reviewed both rates Google Drive API + MCP 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

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.

Google Drive API + MCP

No charge for API calls within quota, counted in quota units per minute per project and per user. OAuth consent, scope verification and a Cloud project before an agent can list a folder.

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

Google Drive API + MCP

  1. Ask for drive.file rather than drive; it needs no verification and covers files the app created or the user picked
  2. Use uploadType=resumable for anything over 5 MB and send chunks in multiples of 256 KB, and pass fields= on files.list and files.get to cut responses
  3. For a link that expires, share to a user or group with expirationTime; a type=anyone permission can't expire, so delete it yourself
  4. Mark the OAuth client "Use this client for an AI-powered agent" before 12 November 2026, since Workspace MCP servers reject unmarked clients from 11 November
  5. Back off exponentially on 429 rateLimitExceeded and 403 userRateLimitExceeded; 403 storageQuotaExceeded won't clear by retrying

Questions

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

Google Drive API + MCP scores 77.8 (BB) on agent readiness against Dropbox API + MCP's 67.1 (B), and leads in 4 of 7 scored categories. Dropbox API + MCP leads on maintenance & community.

Do Dropbox API + MCP and Google Drive API + MCP need an API key?

Both use an OAuth sign-in.

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

Yes. Dropbox API + MCP has a hosted endpoint at https://api.dropboxapi.com/2 and Google Drive API + MCP at https://www.googleapis.com/drive/v3.

Other comparisons with Dropbox API + MCP or Google Drive 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.