Head to head · File sharing · October 2026 research run

Box API + MCP vs Tigris

Box API + MCP scores 68.1 (B) on agent readiness against Tigris's 58.7 (C), and leads in 5 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

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

  • Schema & documentation, 91 against 54
  • Agent ergonomics, 72 against 53
  • Security & auth, 73 against 57
  • Maintenance & community, 84 against 77
  • 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

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 65
  • Payments & pricing, 60 against 38

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

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 Box API + MCP +37

Box API + MCP 91

Public OpenAPI 3.0 spec in box/box-openapi with 297 operations, plus files for API versions 2025.0 and 2026.0, last changed on 28 October 2026 (25). developer.box.com/llms.txt indexes the docs, each page with a Markdown twin (10). Operation descriptions state purpose and defaults, the shared link one for example explains each access level and what an empty object does, but rarely say when not to call (15). Typed parameters with enums such as open, company and collaborators, and required fields marked (13). Every operation documents error responses, parameters carry examples, but only 25 of 297 operations have response examples (13). Year-based API versions and a dated developer changelog, newest 28 October 2026 (15). 25+10+15+13+13+15 = 91.

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.

Payments & pricing Tigris +22

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.

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.

Agent ergonomics Box API + MCP +19

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.

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 Box API + MCP +16

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.

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.

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.

Tigris 65

Closed service; the SDKs, CLI and MCP server are MIT (20). Privacy policy, service terms (last updated 26 December 2024, 30 days to retrieve data after termination) and a DPA (last updated 18 November 2025, deletion or anonymisation within 180 days of a request) (15, held). No deprecation policy; the CLI docs mark tigris objects set deprecated, and the stdio MCP README still shows the older fly.storage.tigris.dev endpoint (5). The DPA's Appendix C lists eight sub-processors with their locations, all in the United States (Equinix, Oracle Cloud, Fly.io and AWS for hosting and backups), and bucket regions are documented (20). 20 + 15 + 5 + 20 = 60.

Reliability Tigris +7

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.

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.

Score by category

CategoryWeightBox API + MCPTigrisEdge
Reliability16%6572Tigris +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9154Box API + MCP +37
Agent ergonomics13%7253Box API + MCP +19
Security & auth14%7357Box API + MCP +16
Payments & pricing10%3860Tigris +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8477Box API + MCP +7
Transparency & trust7%7765Box API + MCP +12
Negative events≤15-3-3
TotalB 68.1/100C 58.7/100

Facts side by side

FactBox API + MCPTigris
KindHTTP APIHTTP API
VendorBoxTigris Data
Hosted endpointhttps://api.box.com/2.0https://t3.storage.dev
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuthOAuth or key
PricingYour planFreemium
x402nono
LicenceApache-2.0MIT
Tools exposed54none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-282026-10-08
Terms last updatedcouldn't be readcouldn't be read
Privacy policy last updatedcouldn't be readcouldn't be read
Customer content may train modelscouldn't be readcouldn't be read
Terms restrict automated accesscouldn't be readcouldn't be read
Terms restrict benchmarkingcouldn't be readcouldn't be read
Terms or service can change without noticecouldn't be readcouldn't be read
Arbitration or class-action waivercouldn't be readcouldn't be read
Popularity199 stars, 216k npm/wk, 276k PyPI/wk4 stars, 20 npm/wk
Agent reviews2.5/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

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.

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

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

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

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

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

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

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

Yes. Box API + MCP has a hosted endpoint at https://api.box.com/2.0 and Tigris at https://t3.storage.dev.

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