How to integrate Google Drive MCP with Claude Agent SDK

This guide walks you through connecting Google Drive to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Google Drive agent that can create a new folder named 'invoices', share last uploaded file with your team, add comment to project proposal document through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Google Drive account through Composio's Google Drive MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
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

This guide walks you through connecting Google Drive to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Google Drive agent that can create a new folder named 'invoices', share last uploaded file with your team, add comment to project proposal document through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Google Drive account through Composio's Google Drive MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Google Drive with

ChatGPTOpenAI Agents SDKClaude CodeClaude CoworkCodexOpenCodeCursorVS CodeOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Google Drive
  • Configure an AI agent that can use Google Drive as a tool
  • Run a live chat session where you can ask the agent to perform Google Drive operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

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 step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Google Drive account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Google Drive functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Google Drive
  const session = await composio.create(USER_ID, {
    toolkits: ['googledrive'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Google Drive
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Google Drive tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Google Drive
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

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

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['googledrive']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Google Drive tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Google Drive through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
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.

FRAMEWORKS

How to build Google Drive MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Google Drive MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Google Drive MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Google Drive MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Google Drive MCP with Claude Cowork

Codex logo

Codex

Use Google Drive MCP with Codex

Cursor logo

Cursor

Use Google Drive MCP with Cursor

OpenClaw logo

OpenClaw

Use Google Drive MCP with OpenClaw

Hermes logo

Hermes

Use Google Drive MCP with Hermes

CLI logo

CLI

Use Google Drive MCP with CLI

Google ADK logo

Google ADK

Use Google Drive MCP with Google ADK

LangChain logo

LangChain

Use Google Drive MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Google Drive MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Google Drive MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Google Drive MCP with LlamaIndex

CrewAI logo

CrewAI

Use Google Drive MCP with CrewAI

OpenCode logo

OpenCode

Use Google Drive MCP with OpenCode

VS Code logo

VS Code

Use Google Drive MCP with VS Code

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 Agent SDK 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
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies