Getting Claude to Actually Work WITH Google Drive

Mar 10 • ⭐ Wins

I want to share what I feel could be a big win I just had. Especially as I think many people believe they can just plough ahead with AI tools, only to hit frustrating tech challenges!

A bit of context first, because it shapes the whole problem.

I’m a Claude Pro subscriber and primarily use Claude via the MacOS Desktop app, rather than in a browser. Like many, I have been looking to take more advantage of Claude Cowork mode, which is relatively new. And get it working with my (free account) Google ecosystem.

If you use Claude Chat via the web interface or desktop, the native Google Drive connector works reasonably well for ‘fetching’ and ‘reading’ files. It's not perfect, but it connects and does a reasonable job of making it seem as if Claude and Google are working together.

Important points:

Claude Desktop and Claude via a browser are not the same
Claude Chat and Claude Cowork are not the same

The nuances between each mean you’re likely to hit different obstacles at different times depending on what you’re doing.

Cowork runs inside a sandboxed Linux VM, and direct web fetching to Google's domains is blocked by design. Paste a Google Docs URL and Claude just stares at it. That's not a bug - it's how the sandbox is built.

So the browser connector and the Desktop connector behave differently, and that gap is where this whole challenge lives.

Worth noting: even if you're happy to stay in the browser, the native Google Drive connector is read-only across both modes. There's no built-in write capability.

No creating Docs
No updating Sheets
No folder management.

(I believe) That gap exists regardless of whether you're using the Desktop app or in a browser session.

First stop: Troubleshoot possibilities with Claude’s native Google Drive connector... It shows as "Connected" in settings. Looks fine.

But in Cowork sessions, any attempt Claude made to collect the desired tools proved fruitless!

A workaround was to download the Google Drive app to my MacOS (and set it to streaming so that you don’t clog up your desktop storage). Then you can choose ‘Drive’ files and folders that Claude can work with. But you must do that at the beginning of a task session!

After a full OAuth re-authorisation, a session restart, and quite a bit of back-and-forth with Claude itself as it tried to diagnose the issue, we confirmed: the connector only initialises properly when you select your Google Drive folder at the very start of a new task. If you miss that step, the tools don't load. It's a session-initialisation quirk, not a connection problem.

That covers reading Google Docs in Desktop. But it doesn't help with Sheets, and it still doesn't help with writing anything back to Drive - in any mode!

The Sheets and ‘write’ (to Google) problem needed a different approach.

Why not Zapier?

At this point, I could have gone down the Zapier route. Easy integration, well-documented. But I don’t use Zapier for anything else, and I wasn't prepared to add another paid subscription just to fill a gap.

In contrast, I’m already a premium Make.com account holder with multiple Google OAuth (connections) configured. Make has multiple AI Agents and MCP features, so why not explore what else I can do in Make instead?

Make.com to the rescue

I built a simple ‘Google Apps’ AI Agent in Make and armed it with the Google Drive, Docs, and Sheets 'Make an API Call' tools (which is different from giving it all the individual tools). Then used those API call tools to set up a dedicated Google Apps Make MCP that I can easily share with Claude.

The ‘Make an API Call’ is the key feature that made my solution genuinely useful. Once that was in place, I wasn't locked into a fixed set of pre-built operations. Claude can now call these full APIs dynamically, passing parameters at runtime based on the task's actual needs.

Double whammy win!

The solution I landed on now solves the ‘write to Google’ problem Claude faces, regardless of whether it’s working on your desktop or in a browser. Or whether you’re using Chat or Cowork.

The result is I now have just 3-5 tools Claude can use anytime to execute virtually any Google Drive, Docs, or Sheets task I need done.

Create folders in Drive
Create text files in Drive
Full Google Drive API access
Full Google Docs API access
Full Google Sheets API access

What does this actually mean in practice?

Reading and writing Google Docs and Sheets from Cowork
Creating folder structures
Searching Drive by filename

All authenticated through OAuth I already had in place.

No Zapier. No extra subscription. No pre-wired scenario for each specific use case - Claude figures out the parameters, Make handles the auth and API calls.

It felt like an age trying to get there, and I won't pretend the troubleshooting was fun. But the setup is done and should now work across every Chat/Cowork task going forward.

If you're in a similar spot - Claude and Google not playing nicely with each other, go find an ‘make an API call’ option. I found it in Make, but you could make your own, depending on your tech stack.

Once you do, Claude and Google will soon be working together on your behalf and boosting your productivity like never before!

Happy to share more details on the Make AI Agent/MCP tool setup if anyone wants the step-by-step path.

4 comments

Getting Claude to Actually Work WITH Google Drive