How to Use Claude with Google Drive — Without Giving It Everything

Connecting Claude to Google Drive is one of the most useful AI integrations you can set up. It can summarize documents, extract data from reports, and draft files on your behalf. It can also read every contract, invoice, and personal document you've ever saved — if you let it.

The integration itself isn't the problem. The problem is how most people set it up — by granting broad OAuth scopes with no policy layer in between. This guide shows you how to connect Claude to Google Drive through Stow, so the AI gets the access it needs and nothing more.

What the Setup Should Look Like

Every request Claude makes to your Drive should pass through a permission and policy layer first:

Without that middle layer, Claude has the same level of access as a logged-in user. That's a much larger attack surface than most people realize.

Why Direct Drive Access Is a Problem

A direct Claude → Google Drive connection creates several risks that aren't obvious until something goes wrong:

Step 1: Connect Google Drive in Stow

Start inside your Stow dashboard:

• Navigate to Connected Services
• Click Add New Service
• Select Google Drive from the directory
• Click Connect via OAuth and authorize through your Google account

Once authorized, Google Drive is connected to Stow. Claude still can't touch your files yet — that's controlled entirely by the permission toggles you set next.

Step 2: Configure Google Drive Permissions

After connecting, you land on the Google Drive configuration page. This is the most important step — every toggle here is enforced by Stow before any request reaches your Drive.

Manage sharing & access is off by default for a reason. An AI that can modify sharing permissions on your Drive files can inadvertently expose documents to unintended people. Keep this off unless you have a specific, reviewed reason to enable it.

Step 3: Connect Claude to Stow

Wire Claude Desktop into the Stow MCP layer:

• Open Claude Desktop and click Customize in the sidebar
• Go to Connectors → Add Custom Connector
• Name it (e.g., "Stow") and paste the connector URL: https://mcp.stowprotect.com
• Click Add, then Connect — Claude initiates the OAuth flow automatically

Step 4: Start Using Drive in Claude

With the integration live, you can use prompts like:

When Claude attempts an action flagged as Approval Required — like updating an existing file — it pauses in your Stow dashboard until you review and confirm. Nothing changes in your Drive without that step completing.

The Permission Boundaries That Matter Most

Google Drive permissions fall into three risk tiers. Understanding these helps you configure Stow correctly:

What Gets Logged

Every Drive action Claude attempts is recorded in your Stow Activity Log — no guessing, no blind trust.

No File Content Is Ever Stored

Even with full activity logging, your document content stays private. Stow's Zero-Retention policy means:

• File contents are stripped before reaching the database
• Drive responses are sanitized to metadata only
• OAuth tokens are masked and never persisted in plain text

The Right Way to Give Claude Drive Access

Claude can be genuinely useful with your Drive — summarizing long documents, generating new content, extracting data from reports. But that usefulness doesn't require unrestricted file access. With Stow, you define exactly what Claude can touch — and everything else stays off limits.