Google Drive MCP Server

An MCP (Model Context Protocol) server that enables Claude to interact with your Google Drive. Works with Claude Web via OAuth2 authentication.

Features

• List files - Browse your Drive files and folders

• Search - Full-text search across your Drive

• Read files - Read content from text files, Google Docs, and Sheets

• Create folders - Organize your Drive with new folders

• Create files - Create text files, JSON files, or Google Docs

• Create sheets - Create Google Sheets with optional data

• Move files - Move files and folders to different locations

• Edit docs - Full document editing with formatting, headings, images, links, and lists

Tools

Architecture

• Cloud Functions Gen 2 - Serverless deployment with automatic scaling

• In-memory state - Auth state stored in memory with automatic cleanup

• JWT tokens - Secure access/refresh tokens for MCP authentication

• Single-user - Restricted to a single authorized email (ALLOWED_EMAIL)

• PKCE required - OAuth 2.1 with S256 code challenge

See SETUP.md for detailed setup instructions.

Quick Start

Prerequisites

• Google Cloud account with billing enabled

• gcloud CLI installed and authenticated

• Node.js 20+

1. Clone and Install

2. Create OAuth Credentials

1. Go to Google Cloud Console - Credentials

2. Click Create Credentials → OAuth client ID

3. Application type: Web application

4. Name: Google Drive MCP

5. Leave redirect URIs empty for now (we'll add after deployment)

6. Copy the Client ID and Client Secret

3. Configure OAuth Consent Screen

1. Go to OAuth consent screen

2. User Type: External

3. Fill in required fields

4. Add scopes: drive, spreadsheets, documents, userinfo.email

5. Add yourself as a test user

4. Store Secrets

5. Deploy

The script will output the function URL. Add this as the authorized redirect URI in your OAuth credentials:

6. Connect to Claude Web

1. Go to claude.ai

2. Settings → Integrations

3. Add MCP server with your Cloud Functions URL

4. Click Connect and authenticate with Google

GitHub Actions Deployment

This repo includes automatic deployment via GitHub Actions on push to main.

Required secrets:

• WIF_PROVIDER - Workload Identity Federation provider

• ALLOWED_EMAIL - Authorized user email

See .github/workflows/deploy.yml for details.

Usage Examples

Once connected, you can ask Claude:

• "List my recent Google Drive files"

• "Search my Drive for documents about quarterly reports"

• "Read the content of my meeting notes document"

• "What's in my budget spreadsheet?"

• "Create a folder called 'Projects' in my Drive"

• "Create a file called 'notes.txt' with my meeting notes"

• "Create a Google Doc called 'Project Plan' with an outline"

• "Move the budget spreadsheet to the Finance folder"

• "Create a spreadsheet called 'Expenses' with columns for Date, Description, and Amount"

• "Append today's meeting notes to my Project Doc"

• "Replace all occurrences of '2024' with '2025' in my annual report"

• "Add a bold heading called 'Introduction' to my blog post"

• "Insert a bulleted list of key takeaways"

• "Add a link to the source article"

Security

• OAuth2 with PKCE - Secure authorization flow with S256 code challenge

• Single-user authentication - Only the configured ALLOWED_EMAIL can authenticate

• JWT tokens - Short-lived access tokens (1 hour), long-lived refresh tokens (30 days)

• In-memory state - No persistent storage of auth state (tokens stored only in memory)

• Secret Manager - OAuth credentials stored securely in Google Secret Manager

• No credential storage - Your Google password never touches the server

Development

License

MIT