Google Drive

Gated

drive.google.comSourcedUpdated 28 Oct 2026 · yesterday

You can register a Google Cloud OAuth client and connect your own account in under an hour. A public launch with full-Drive scopes (drive, drive.readonly) is harder: those scopes are restricted, so you need brand verification, a demo video, restricted-scope review and a paid CASA security assessment every year. If drive.file (non-sensitive) is enough for your app, you only need brand verification.

Your work: 3–10 days
Waiting on Google Drive: 2–8 weeks
First user connects: Today, in about 30–60 minutes, as a test user in Testing mode

3 not confirmed 13 sources Why this tier How did it go?

.md JSON

Use with your agent

Set up a Google Drive OAuth app for our integration, as far as you can.
Guide: https://oauth-guide.akshatsethi.com/apps/google-drive.md (updated 28 Oct 2026)

Gated. Hands-on work: 3–10 days. Waiting on Google Drive: 2–8 weeks.

Check these exist first:
- Google account and Google Cloud project [human]
- Your OAuth client's redirect URI [agent]

Needed later, not now:
- Verified domain and public homepage (for launch)
- Privacy policy on the same domain (for launch)
- Demo video (for launch)
- CASA security assessment (restricted scopes) (for launch)
- An allowed use case for restricted scopes (for launch)

Steps, in order:
1. [human] Create a Google Cloud project
2. [agent] Enable the Google Drive API. Enable the Google Drive API for the project in the API Library.
3. [human] Set up Google Auth Platform branding
4. [agent] Add Drive scopes under Data Access. Add only the scopes you will use. drive.file is non-sensitive and avoids CASA. drive and drive.readonly are restricted. Watch out: If the scopes your code requests differ from the ones configured here, users see the unverified screen and verification is rejected.
5. [agent] Add test users. Under Audience > Test users, add your own Google account and any testers. You can add up to 100. Watch out: Test users count against the quota for good once added, and their tokens expire after 7 days.
6. [agent] Create a Web application OAuth client. Under Google Auth platform > Clients, click Create Client, choose Web application, and add your redirect URI under Authorized redirect URIs. You can tick 'Use this client for an AI-powered agent' only at creation time. Watch out: The redirect URI must match exactly, including scheme, path and trailing slash.
7. [human] Put client ID and secret in your OAuth client
8. [agent] Connect your own Drive account. Run the OAuth flow as a test user, click through the unverified warning and confirm the API calls work. Watch out: Under Google's granular consent, users can untick individual scopes. Handle missing permissions in your app.
9. [human] Verify domain, publish homepage and privacy policy
10. [human] Publish the app and submit for verification
11. [provider] Wait for Google's Trust & Safety review (wait 3–14 days)
12. [human] Complete the CASA security assessment
13. [human] Renew CASA every 12 months

Rules:
- Do [agent] steps yourself. Steps in Google Drive's dashboard need a browser I'm signed in to; without one, give me the exact clicks and values instead, then carry on with the code.
- At each [human] or [provider] step, stop and tell me exactly what's needed.
- Never put client secrets in chat, code or commits. I paste them into our OAuth client or secret manager myself.
- Request the narrowest scopes that work. Ask me before choosing scopes or changing security settings (scope restrictions, roles, grant types), even where the guide marks the step [agent].
- Claims marked Inferred or low confidence in the guide are unverified. Check them and tell me what you find.
- If the guide doesn't match what you see (a page, field or requirement), tell me and report it so it gets fixed: POST https://oauth-guide.akshatsethi.com/api/reports with {"app": "google-drive", "step": 2, "message": "what you saw"} (step is optional), or call the report_problem MCP tool. Never put secrets or personal data in a report.
- When setup ends (users can connect, or it's waiting on Google Drive's review) or you can't get past a step, report how it went so the guide improves: POST https://oauth-guide.akshatsethi.com/api/reports with {"app": "google-drive", "outcome": "worked" | "waiting" | "stuck", "step": 3, "message": "what happened"}, or call the report_setup MCP tool. Stopping for me at a [human] step isn't stuck: don't report that.
- Finish with what's done, the redirect URI and scopes used, and what's left before public launch.

Paste into Claude Code, Cursor or any agent.

Google Drive

Plan

SetupBefore you start

BuildYour account

BetaTest users or unverified production

LaunchVerified public app

Why gated

Scopes

When you get stuck

Not confirmed

Sources

Feedback

Google Drive

Plan

SetupBefore you start

BuildYour account

BetaTest users or unverified production

LaunchVerified public app

Why gated

Scopes

When you get stuck

Not confirmed

Sources

Feedback