Google Drive MCP Server — Full Setup Walkthrough

You've got a 40-page strategy document in Google Drive. Or a budget spreadsheet with 15 tabs. Or a folder of meeting notes you want summarized. Every time you need Claude's help with them, you're downloading, copying, and pasting. The Google Drive MCP server cuts that whole process out.

What the Google Drive MCP server can do

It exposes two main tools: search (find files by name or content query) and read_file (retrieve the content of a specific file by ID or URL). It works with Google Docs, Sheets, Slides, plain text files, and PDFs stored in Drive.

What you can actually ask Claude with this running: "Summarize the document at this Drive URL," "Find all files with 'Q3 budget' in the name," "Extract the data from rows where the status column says 'Pending' in my spreadsheet."

What it can't do: write to files (read-only), access Shared Drives with restricted permissions, or handle files larger than Google's export size limits.

The setup — more steps than most, but manageable

The Google Drive MCP server needs OAuth credentials because Google requires user authorization for Drive access. Here's the full process:

Step 1: Create a Google Cloud project

Go to console.cloud.google.com and create a new project. Call it something like "Claude MCP Integration." Then navigate to "APIs & Services" → "Enable APIs" and enable the Google Drive API.

Step 2: Create OAuth credentials

In the same "APIs & Services" section, go to "Credentials" and create an OAuth 2.0 Client ID. Set the application type to "Desktop app." Download the credentials JSON file — save it somewhere safe on your machine, like ~/.config/mcp/gcp-oauth.keys.json.

Step 3: Add the config entry

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "gdrive": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-gdrive"],
      "env": {
        "GDRIVE_OAUTH_PATH": "/Users/yourname/.config/mcp/gcp-oauth.keys.json",
        "GDRIVE_CREDENTIALS_PATH": "/Users/yourname/.config/mcp/gdrive-credentials.json"
      }
    }
  }
}

Step 4: Authenticate

Run the server once from the command line to complete the OAuth flow:

npx -y @modelcontextprotocol/server-gdrive

This opens a browser window asking you to authorize the app for your Google account. After you approve, the credentials get saved to the path you specified. Restart Claude Desktop and you're done — future launches authenticate automatically.

Real use cases worth knowing about

Here's the thing — most articles just describe the setup. Here are actual workflows people use this for.

Meeting note summaries: Keep a folder of meeting notes in Drive. Ask Claude to "summarize all meeting notes from October" and it'll read them all and give you a single executive summary.

Sheet data extraction: You have a spreadsheet tracking project statuses. Ask "which projects in my Q4 tracker have status 'At risk'?" Claude reads the sheet and filters the data without you opening it.

Document comparison: "Compare my current proposal draft at [URL] with the original brief at [URL] and tell me what I've changed." Claude reads both and gives you a diff in plain English.

Does Google Drive MCP work with Shared Drives?

It can access Shared Drives as long as your Google account has permission and the OAuth scope includes it. The default scope is drive.readonly, which covers Shared Drives your account can read. If you're getting permission errors on Shared Drive files, check whether your account has individual file access vs. full Shared Drive access.