Google Drive with CrewAI

How to integrate Google Drive MCP with CrewAI

Trusted by

GET STARTED FOR FREE GET A DEMO

30 min · no commitment · see it on your stack

Introduction Also integrate Google Drive with TL;DR What is CrewAI What is the Google Drive MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Composio SDK Step-by-step Guide Complete Code Conclusion How to build Google Drive MCP Agent with another framework Explore Other Toolkits FAQ

Connect Google Drive without Auth hassles

We manage OAuth, API Key, token refresh, and scopes, you just build.

Try for Free

Introduction

This guide walks you through connecting Google Drive to CrewAI 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 CrewAI 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

ChatGPT Antigravity OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenCode Cursor VS Code OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI LlamaIndex

TL;DR

Here's what you'll learn:

Get a Composio API key and configure your Google Drive connection
Set up CrewAI with an MCP enabled agent
Create a Tool Router session or standalone MCP server for Google Drive
Build a conversational loop where your agent can execute Google Drive operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

Agent Roles: Define specialized agents with specific goals and backstories
Task Management: Create tasks with clear descriptions and expected outputs
Crew Orchestration: Combine agents and tasks into collaborative workflows
MCP Integration: Connect to external tools through Model Context Protocol

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.

Supported Tools & Triggers

Tools

Triggers

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 optionsCreates a copy of a file and applies any requested updates with patch semantics.

Create CommentTool to create a comment on a file in Google Drive.

Create Shared DriveTool to create a new shared drive.

Create File or FolderCreates a new file or folder in Google Drive.

Create a File from TextCreates 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 folderCreates a new folder in Google Drive, optionally within an EXISTING parent folder specified by its ID or name.

Create PermissionTool to create a permission for a file or shared drive.

Create ReplyTool to create a reply to a comment in Google Drive.

Create Shortcut to File/FolderTool 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 CommentPermanently deletes a comment thread (and all its replies) from a Google Drive file — this action is irreversible.

Delete Shared DriveTool to permanently delete a shared drive.

Delete Parent (v2)Tool to remove a parent from a file using Google Drive API v2.

Delete PermissionDeletes 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 ReplyTool to delete a specific reply by reply ID.

Delete RevisionTool to permanently delete a file revision.

Download a file from Google DriveDownloads a file from Google Drive by its ID.

Download file via operationTool to download file content using long-running operations.

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

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

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

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

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

Generate File IDsGenerates a set of file IDs which can be provided in create or copy requests.

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

Get AppTool to get information about a specific Drive app by ID.

Get Changes Start Page TokenTool 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 CommentTool to get a comment by ID.

Get Shared DriveTool to get a shared drive by ID.

Get File MetadataTool 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 PermissionGets a permission by ID.

Get Permission ID for EmailTool to get the permission ID for an email address using the Drive API v2.

Get ReplyTool to get a specific reply to a comment on a file.

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

Delete folder or fileTool to delete a file or folder in Google Drive.

Hide Shared DriveTool 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 ProposalsTool to list pending access proposals on a file.

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

List ChangesTool 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 CommentsTool to list all comments for a file in Google Drive.

List File LabelsTool 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 PermissionsTool to list a file's permissions.

List Replies to CommentTool to list replies to a comment in Google Drive.

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

List Shared DrivesTool to list the user's shared drives.

Modify File LabelsModifies the set of labels applied to a file.

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

Patch PermissionTool 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 UploadTool to start and complete a Google Drive resumable upload session.

Stop Watch ChannelTool to stop watching resources through a specified channel.

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

Unhide Shared DriveTool to unhide a shared drive.

Untrash FileTool to restore a file from the trash.

Update CommentTool to update an existing comment on a Google Drive file.

Update Shared DriveTool 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 MetadataUpdates ONLY the metadata properties of a specific file revision (keepForever, published, publishAuto, publishedOutsideDomain).

Update PermissionTool to update a permission with patch semantics.

Update ReplyTool to update a reply to a comment on a Google Drive file.

Upload FileUploads 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 DriveTool to fetch a file from a provided URL server-side and upload it into Google Drive.

Upload/Update File ContentTool to update file content in Google Drive by uploading new binary content.

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

Watch File for ChangesTool to subscribe to push notifications for changes to a specific file.

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:

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

Step-by-step Guide

Prerequisites

Before starting, make sure you have:

Python 3.9 or higher
A Composio account and API key
A Google Drive connection authorized in Composio
An OpenAI API key for the CrewAI LLM
Basic familiarity with Python

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
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.

Install dependencies

bash

pip install composio crewai crewai-tools[mcp] python-dotenv

What's happening:

composio connects your agent to Google Drive via MCP
crewai provides Agent, Task, Crew, and LLM primitives
crewai-tools[mcp] includes MCP helpers
python-dotenv loads environment variables from .env

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates with Composio
USER_ID scopes the session to your account
OPENAI_API_KEY lets CrewAI use your chosen OpenAI model

Import dependencies

python

import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")

What's happening:

CrewAI classes define agents and tasks, and run the workflow
MCPServerHTTP connects the agent to an MCP endpoint
Composio will give you a short lived Google Drive MCP URL

Create a Composio Tool Router session for Google Drive

python

composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["googledrive"])

url = session.mcp.url

What's happening:

You create a Google Drive only session through Composio
Composio returns an MCP HTTP URL that exposes Google Drive tools

Initialize the MCP Server

python

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )

What's Happening:

Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.

Create a CLI Chatloop and define the Crew

python

print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")

What's Happening:

Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

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

python

from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["googledrive"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Google Drive through Composio's Tool Router. The agent can perform Google Drive operations through natural language commands.

Next steps:

Add role-specific instructions to customize agent behavior
Plug in more toolkits for multi-app workflows
Chain tasks for complex multi-step operations

How to build Google Drive MCP Agent with another framework

ChatGPT

Use Google Drive MCP with ChatGPT

Antigravity

Use Google Drive MCP with Antigravity

OpenAI Agents SDK

Use Google Drive MCP with OpenAI Agents SDK

Claude Agent SDK

Use Google Drive MCP with Claude Agent SDK

Claude Code

Use Google Drive MCP with Claude Code

Claude Cowork

Use Google Drive MCP with Claude Cowork

Codex

Use Google Drive MCP with Codex

Cursor

Use Google Drive MCP with Cursor

OpenClaw

Use Google Drive MCP with OpenClaw

Hermes

Use Google Drive MCP with Hermes

CLI

Use Google Drive MCP with CLI

Google ADK

Use Google Drive MCP with Google ADK

LangChain

Use Google Drive MCP with LangChain

Vercel AI SDK

Use Google Drive MCP with Vercel AI SDK

Mastra AI

Use Google Drive MCP with Mastra AI

LlamaIndex

Use Google Drive MCP with LlamaIndex

OpenCode

Use Google Drive MCP with OpenCode

VS Code

Use Google Drive MCP with VS Code

Explore Other Toolkits

Google Docs

Oauth2

Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze.

Google Super

Oauth2Api Key

Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization.

Affinda

Api Key

Affinda is an AI-powered document processing platform that automates data extraction from resumes, invoices, and more. It streamlines document-heavy workflows by turning files into structured, actionable data.

TOOLKIT MARKETPLACE

FAQ

What are the differences in Tool Router MCP and Google Drive MCP?

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.

Can I use Tool Router MCP with CrewAI?

Yes, you can. CrewAI 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.

Can I manage the permissions and scopes for Google Drive while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for free Get a demo↗

Harsha GaddipatiCo-founder, Slashy

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

Abhi AryaCo-founder, Opennote

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 has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

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

Ryan YuFounder, Extra Thursday

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

Tomisin JenrolaFounder & CEO, SwarmZero

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

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

How to integrate Google Drive MCP with CrewAI

Table of Contents

Connect Google Drive without Auth hassles

Introduction

Also integrate Google Drive with

TL;DR

What is CrewAI?

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

Supported Tools & Triggers

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import dependencies

Create a Composio Tool Router session for Google Drive

Initialize the MCP Server

Create a CLI Chatloop and define the Crew

Complete Code

Conclusion

How to build Google Drive MCP Agent with another framework

ChatGPT

Antigravity

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

Cursor

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

OpenCode

VS Code

Explore Other Toolkits

Google Docs

Google Super

Affinda

FAQ

What are the differences in Tool Router MCP and Google Drive MCP?

Can I use Tool Router MCP with CrewAI?

Can I manage the permissions and scopes for Google Drive while using Tool Router?

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability