Connect Google Drive to Claude Code

Let Claude create, organize, and edit your files in Google Drive. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Google Drive to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Google Drive, you add a Google Drive MCP server: a small hosted service that exposes Google Drive's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Google Drive account. No API keys pasted into config files.

claude mcp add --transport http google-drive https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Google Drive once connected?

Full read-write Google Drive access lets Claude create a new doc or sheet, drop it in the right folder, rename and move files, update existing content, and adjust sharing once you approve. The organizing and drafting that used to mean manual upload and filing happen where the files already live.

Create a new document or spreadsheet and place it in a chosen folder
Move, rename, or organize files and folders to tidy a workspace
Update the contents of an existing file in place
Adjust sharing or permissions for a file after you approve
Copy a template into a new project folder and fill it in
Find every file matching a query and propose how to reorganize them

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Google Drive access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Google Drive API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Google Drive changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Google Drive connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Google Drive connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Google Drive account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Google Drive's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Google Drive?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Google Drive account it signs in with. Revoking access is one click in Google Drive.

More on the Google Drive connector

Google Drive connector for claude.ai Dropbox + Claude Code Box + Claude Code SharePoint + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us