DigitalOcean Spaces vs Google Drive API + MCP

DigitalOcean Spaces

Per-bucket access keys with read or read-write-delete grants, an 800 operations a second limit per bucket and a 99.9 per cent SLA are all published. The MCP server manages keys and CDN endpoints only, not objects, and the S3 reference documents no error codes. A payment method is required before any bucket is created.

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.

DigitalOcean Spaces

1. Set the endpoint to https://<region>.digitaloceanspaces.com and, in AWS SDKs other than Python's, set region to us-east-1 when creating a bucket
2. Ask for a limited access key with a Read or Read/Write/Delete grant on one bucket. A full access key can create, configure and delete every bucket
3. Do the object work through the S3 API. The MCP server and doctl cannot upload, list, move or delete files
4. Retry with exponential backoff on 503 Slow Down, and keep below 800 operations a second per bucket
5. Fetch presigned links from the origin host, not the CDN. The docs say presigned requests through the CDN are not cached and can double the bandwidth charge
6. Avoid many tiny objects. Each bills as at least 4 KiB on Standard and 128 KiB on Cold Storage, which also has a 30-day minimum

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
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. Pass fields= on files.list and files.get to cut the response, and page with pageToken
5. Back off exponentially on 429 rateLimitExceeded and 403 userRateLimitExceeded; 403 storageQuotaExceeded won't clear by retrying