How to integrate Google Drive MCP with Claude Code

Manage your Google Drive directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

Google Drive logoGoogle Drive
Oauth2

Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.

76 Tools7 Triggers

Introduction

Manage your Google Drive directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Google Drive with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Google Drive to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

What is the Google Drive MCP server, and what's possible with it?

The Googledrive MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Google Drive account. It provides structured and secure access to your files and folders, so your agent can perform actions like uploading files, managing sharing permissions, organizing folders, and collaborating via comments on your behalf.

  • Automated file uploads and creation: Effortlessly ask your agent to create new files or folders, upload documents, or generate files from provided text content in your Google Drive.
  • Advanced sharing and permission management: Let your agent modify sharing preferences for files and folders, granting or revoking access to users, groups, domains, or the public.
  • Collaboration through comments and replies: Have the agent add comments to files, reply to existing comments, or delete comments to facilitate smooth collaboration with your team.
  • Efficient folder and shortcut organization: Direct your agent to create, organize, or nest folders, or generate shortcuts to important files and folders for easier access.
  • File duplication and backup: Instruct your agent to duplicate existing files, creating reliable backups or templates for repeated use.

Connecting Google Drive via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Google Drive) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Google Drive account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['googledrive'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http googledrive-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Google Drive. This URL will be used to connect Claude Code to Google Drive.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Google Drive
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Google Drive MCP to Claude Code

bash
claude mcp add --transport http googledrive-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (googledrive-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Google Drive MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your googledrive-composio entry in the list
  • This confirms that Claude Code can now access Google Drive tools

If everything is wired up, you should see your googledrive-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Google Drive

The first time you try to use Google Drive tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Google Drive
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Google Drive authorization flow
  • Return to the terminal and start using Google Drive through Claude Code

Once authenticated, you can ask Claude Code to perform Google Drive operations in natural language. For example:

  • "Create a new folder named 'Invoices'"
  • "Share last uploaded file with my team"
  • "Add comment to project proposal document"

Complete Code

Here's the complete code to get you started with Google Drive and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['googledrive'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http googledrive-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Google Drive with Claude Code using Composio's MCP server. Now you can interact with Google Drive directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Google Drive operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Google Drive operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

TOOLS & TRIGGERS

Supported Tools and Triggers

Every Google Drive action and event your agent gets out of the box.

Insert File Parent (v2)

Tool to add a parent folder for a file using Google Drive API v2.

Insert Property (v2 API)

Tool to add a property to a file, or update it if it already exists (v2 API).

Copy file with advanced options

Creates a copy of a file and applies any requested updates with patch semantics.

Create Comment

Tool to create a comment on a file in Google Drive.

Create Shared Drive

Tool to create a new shared drive.

Create File or Folder

Creates a new file or folder in Google Drive.

Create a File from Text

Creates a new file in Google Drive from provided text content (up to 10MB), supporting various formats including automatic conversion to Google Workspace types.

Create a folder

Creates a new folder in Google Drive, optionally within an EXISTING parent folder specified by its ID or name.

Create Permission

Tool to create a permission for a file or shared drive.

Create Reply

Tool to create a reply to a comment in Google Drive.

Create Shortcut to File/Folder

Tool to create a shortcut to a file or folder in Google Drive.

Delete Child (v2)

Tool to remove a child from a folder using Google Drive API v2.

Delete Comment

Permanently deletes a comment thread (and all its replies) from a Google Drive file — this action is irreversible.

Delete Shared Drive

Tool to permanently delete a shared drive.

Delete Parent (v2)

Tool to remove a parent from a file using Google Drive API v2.

Delete Permission

Deletes a permission from a file by permission ID.

Delete Property (v2 API)

Tool to delete a property from a file using Google Drive API v2.

Delete Reply

Tool to delete a specific reply by reply ID.

Delete Revision

Tool to permanently delete a file revision.

Download a file from Google Drive

Downloads a file from Google Drive by its ID.

Download file via operation

Tool to download file content using long-running operations.

Edit File

Updates an existing Google Drive file with binary content by overwriting its entire content with new text (max 10MB).

Empty Trash

Tool to permanently and irreversibly delete ALL trashed files in the user's Google Drive or a specified shared drive.

Export Google Workspace file

Exports a Google Workspace document to the requested MIME type and returns exported file content.

Find file

The comprehensive Google Drive search tool that handles all file and folder discovery needs.

Find folder

Tool to find a folder in Google Drive by its name and optionally a parent folder.

Generate File IDs

Generates a set of file IDs which can be provided in create or copy requests.

Get about

Tool to retrieve information about the user, the user's Drive, and system capabilities.

Get App

Tool to get information about a specific Drive app by ID.

Get Changes Start Page Token

Tool to get the starting pageToken for listing future changes in Google Drive.

Get Child Reference (v2)

Tool to get a specific child reference for a folder using Drive API v2.

Get Comment

Tool to get a comment by ID.

Get Shared Drive

Tool to get a shared drive by ID.

Get File Metadata

Tool to get a file's metadata by ID.

Get Property (v2)

Tool to get a property by its key using Google Drive API v2.

Get Parent Reference (v2)

Tool to get a specific parent reference for a file using Drive API v2.

Get Permission

Gets a permission by ID.

Get Permission ID for Email

Tool to get the permission ID for an email address using the Drive API v2.

Get Reply

Tool to get a specific reply to a comment on a file.

Get Revision

Tool to get a specific revision's metadata (name, modifiedTime, keepForever, etc.

Delete folder or file

Tool to delete a file or folder in Google Drive.

Hide Shared Drive

Tool to hide a shared drive from the default view.

Insert Child Into Folder (v2)

Tool to insert a file into a folder using Drive API v2.

List Access Proposals

Tool to list pending access proposals on a file.

List Approvals

Tool to list approvals on a file for workflow-based access control.

List Changes

Tool to list the changes for a user or shared drive.

List Folder Children (v2)

Tool to list a folder's children using Google Drive API v2.

List Comments

Tool to list all comments for a file in Google Drive.

List File Labels

Tool to list the labels already applied to a file in Google Drive.

List Properties (v2 API)

Tool to list a file's properties in Google Drive API v2.

List Permissions

Tool to list a file's permissions.

List Replies to Comment

Tool to list replies to a comment in Google Drive.

List File Revisions

Tool to list a file's revision metadata (not content) in Google Drive.

List Shared Drives

Tool to list the user's shared drives.

Modify File Labels

Modifies the set of labels applied to a file.

Move File

Tool to move a file from one folder to another in Google Drive.

Patch Permission

Tool to update a permission using patch semantics.

Patch Property (v2 API)

Tool to update a property on a file using PATCH semantics (v2 API).

Resumable Upload

Tool to start and complete a Google Drive resumable upload session.

Stop Watch Channel

Tool to stop watching resources through a specified channel.

Trash File

Tool to move a file or folder to trash (soft delete).

Unhide Shared Drive

Tool to unhide a shared drive.

Untrash File

Tool to restore a file from the trash.

Update Comment

Tool to update an existing comment on a Google Drive file.

Update Shared Drive

Tool to update the metadata for a shared drive.

Update File Metadata (PATCH v2)

Tool to update file metadata using the Drive API v2 PATCH method.

Update Property (v2 API)

Tool to update a property on a file using Google Drive API v2.

Update File (Metadata)

Updates file metadata.

Update File Revision Metadata

Updates ONLY the metadata properties of a specific file revision (keepForever, published, publishAuto, publishedOutsideDomain).

Update Permission

Tool to update a permission with patch semantics.

Update Reply

Tool to update a reply to a comment on a Google Drive file.

Upload File

Uploads a file (max 5MB) to Google Drive, placing it in the specified folder or root if no valid folder ID is provided.

Upload File from URL to Drive

Tool to fetch a file from a provided URL server-side and upload it into Google Drive.

Upload/Update File Content

Tool to update file content in Google Drive by uploading new binary content.

Watch Drive Changes

Tool to subscribe to changes for a user or shared drive in Google Drive.

Watch File for Changes

Tool to subscribe to push notifications for changes to a specific file.

FAQ

Frequently asked questions

With a standalone Google Drive MCP server, the agents and LLMs can only access a fixed set of Google Drive tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Google Drive and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Google Drive tools.

Yes, absolutely. You can configure which Google Drive scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Google Drive data and credentials are handled as safely as possible.

Start with Google Drive.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Google Drive tool your agent needs.Free to start.

Start building