How to connect to the Google Drive MCP with Claude Code (5 steps)

Developers store a surprising amount of the context they need to write good code in Google Drive: API specs, architecture diagrams, onboarding docs, sprint briefs, product requirements, etc. 

To help your developers access this context within a terminal like Claude Code, you can connect the AI coding tool with the Google Drive MCP.

We’ll help you do just that via Merge Agent Handler's Google Drive MCP server.

How it works

Merge Agent Handler acts as a secure bridge between your agent and Google Drive's API. 

When you configure a Tool Pack and Registered User, Merge generates a unique MCP URL that Claude Code accesses via HTTP, combined with an API key for authentication. 

Here’s how the command looks (we’ll show you how to get your MCP URL and API key in the following section):

 {
 "mcpServers": {
   "agent-handler": {
     "command": "npx",
     "args": [
       "-y",
       "mcp-remote@latest",
       "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
       "--header",
       "Authorization: Bearer ${AUTH_TOKEN}"
     ],
     "env": {
       "AUTH_TOKEN": "yMt*****"
     }
   }
 }
}

Claude Code sends requests to that MCP URL, Merge handles the OAuth token management and API calls to Google Drive on the backend, and your agent gets back structured results it can reason over.

This means you don't manage Google OAuth tokens in your local environment or wire up Drive credentials into your codebase. Merge handles all of that.

Related: How to connect to the Gmail MCP server with Claude Code

Prerequisites

• A Merge Agent Handler account
• Claude Code installed (run claude --version to confirm)
• A Google account with access to the Drive you want to connect

1. Create a Tool Pack

Log into Merge Agent Handler and navigate to Tool Packs. Create a new pack and give it a name relevant to the use case, like Coding Assistant. 

Under connectors, select Google Drive.

From here you choose which tools to enable. For a typical development workflow, enabling file search, file read, and folder list covers most cases. If you want your agent to create or update files, enable those write tools as well.

Save the Tool Pack. You'll come back to this page to grab your MCP URL in step 4.

2. Add a Registered User

Inside your Tool Pack, create a Registered User. This is the identity context under which your agent will operate. Think of it as the user account your agent acts on behalf of when it calls Google Drive.

Give the Registered User a name that maps to your environment (e.g., dev-local or your own name). Once created, Merge generates a unique MCP URL scoped to this user. Copy it; you'll need it in step 5.

3. Authenticate Google Drive

From the Registered User detail page, click Authenticate next to Google Drive. 

This kicks off a standard Google OAuth flow. 

Sign in with the Google account that has access to the Drive files you want Claude Code to reach, and grant the requested permissions.

Once the OAuth flow completes, the Registered User is linked to your Google Drive. Merge stores and manages the access token from here on. You won't need to re-authenticate unless you revoke access.

Related: How to use the Notion MCP in Claude Code

4. Gather your credentials

You need two things before configuring Claude Code:

1. MCP URL: found on the Tool Pack detail page under the Registered User you just created. It looks like <code class="blog_inline-code">https://ah-api.merge.dev/mcp/...</code>

2. API key: found in Settings > API Keys in your Merge Agent Handler dashboard. Create one if you don't have one yet

Keep both handy for the next step.

5. Add the Google Drive MCP connector

Run the following command in your terminal, substituting your actual MCP URL and API key:

 {
 "mcpServers": {
   "agent-handler": {
     "command": "npx",
     "args": [
       "-y",
       "mcp-remote@latest",
       "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
       "--header",
       "Authorization: Bearer ${AUTH_TOKEN}"
     ],
     "env": {
       "AUTH_TOKEN": "yMt*****"
     }
   }
 }
}

Verify it registered correctly: <code class="blog_inline-code">claude mcp list</code>

Google Drive is now available as a tool in every Claude Code session!

To test it, open a Claude Code session and ask something like: "Search my Google Drive for the API spec doc and summarize the authentication section."

{{this-blog-only-cta}}

Google Drive MCP FAQ

In case you have any more questions on connecting and using the Google Drive MCP in Claude Code, we’ve addressed several more below.

What can you do once the Google Drive MCP is connected to Claude Code?

With Google Drive connected, Claude Code can:

• Search and retrieve documents: pull up specs, READMEs, architecture docs, or any Drive file by name or content without leaving the terminal

• Read file contents: have Claude summarize, extract, or reason over the contents of Docs, PDFs, and other files stored in Drive

• List folder contents: browse project folders to find the right file when you're not sure of the exact name

• Create and update files: write code output, summaries, or generated content directly to Drive (if write tools are enabled in your Tool Pack)

• Cross-reference docs while coding: ground Claude's suggestions in your team's actual documentation rather than generic training data

This is particularly useful on teams where product requirements, API contracts, or architecture decisions live in Shared Drives. Instead of asking "what does this endpoint do?" and waiting for a teammate to respond, Claude Code can look it up in the source doc directly.

Why use Merge Agent Handler vs. a self-hosted MCP server?

You can self-host a Google Drive MCP server using community packages like @modelcontextprotocol/server-gdrive. That works, but it requires you to manage OAuth credentials locally, handle token refresh, and maintain the server yourself.

Merge Agent Handler takes a different approach: it's a managed MCP layer that adds enterprise-grade security controls, real-time observability, and multi-user support on top of the integration. 

You can scope exactly which files and folders each Registered User can access, monitor what your agents are reading and writing, and swap in other connectors (Slack, Jira, GitHub, and more) without touching your Claude Code configuration.

Why is it important to connect a Google Drive MCP to Claude Code?

Google Drive is where teams store the context that makes code meaningful: API specs, architecture decisions, product requirements, onboarding docs, sprint briefs.

That content exists in Drive but is invisible to Claude Code by default; your developers either context-switch to a browser to find it or paste it in manually.

Connecting Google Drive via MCP closes that gap.

Claude Code can search, read, and reference Drive files directly in the terminal, grounding its suggestions in your team's actual documentation rather than generic assumptions. Instead of asking a teammate what an endpoint does or what the agreed-upon data model is, Claude can look it up in the source doc and answer immediately. 

This translates to faster code reviews that reference the actual spec, onboarding that pulls real internal docs rather than hallucinated ones, and agent workflows that can read from Drive and write back without leaving the terminal.