How to integrate Google Drive MCP with LangChain

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Google Drive Logo
LangChain Logo
divider

Introduction

This guide walks you through connecting Google Drive to LangChain 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 my team, add comment to project proposal document, copy template file to today's reports folder through natural language commands.

This guide will help you understand how to give your LangChain 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.

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Google Drive project to Composio
  • Create a Tool Router MCP session for Google Drive
  • Initialize an MCP client and retrieve Google Drive tools
  • Build a LangChain agent that can interact with Google Drive
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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
Add file sharing preferenceModifies sharing permissions for an existing google drive file, granting a specified role to a user, group, domain, or 'anyone'.
Copy fileDuplicates an existing file in google drive, identified by its `file id`.
Create CommentTool to create a comment on a file.
Create Shared DriveTool to create a new shared drive.
Create File or FolderCreates a new file or folder with metadata.
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 a parent folder specified by its id or name; if a parent name is provided but not found, the action will fail.
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 CommentDeletes a comment from a file.
Delete Shared DriveTool to permanently delete a shared drive.
Delete PermissionDeletes a permission from a file by permission id.
Delete ReplyTool to delete a specific reply by reply id.
Download a file from Google DriveDownloads a file from google drive by its id.
Edit FileUpdates an existing google drive file by overwriting its entire content with new text (max 10mb).
Empty TrashTool to permanently delete all of the user's trashed files.
Modify File LabelsModifies the set of labels applied to a file.
Find fileTool to list or search for files and folders in google drive.
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 Changes Start Page TokenTool to get the starting pagetoken for listing future changes in google drive.
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 PermissionGets a permission by id.
Get ReplyTool to get a specific reply to a comment on a file.
Get RevisionTool to get a specific revision's metadata by revision id.
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.
List ChangesTool to list the changes for a user or shared drive.
List CommentsTool to list all comments for a file in google drive.
List File LabelsTool to list the labels on a file.
List Files and FoldersTool to list a user's files and folders in google drive.
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 revisions.
List Shared DrivesTool to list the user's shared drives.
Move FileTool to move a file from one folder to another in google drive.
Stop Watch ChannelTool to stop watching resources through a specified channel.
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)Updates file metadata.
Update File Revision MetadataUpdates metadata of a file revision (e.
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, moving it to a specified folder if a valid folder id is provided, otherwise uploads to root.
Watch Drive ChangesTool to subscribe to changes for a user or shared drive in google drive.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming

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

pip install composio-langchain langchain-mcp-adapters langchain python-dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • composio-langchain provides Composio integration for LangChain
  • langchain-mcp-adapters enables MCP client connections
  • langchain is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_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 your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models

Import dependencies

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Google Drive functionality through MCP

Initialize Composio client

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Google Drive tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

# Create Tool Router session for Google Drive
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['googledrive']
)

url = session.mcp.url
What's happening:
  • We're creating a Tool Router session that gives your agent access to Google Drive tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Google Drive tools as needed

Configure the agent with the MCP URL

client = MultiServerMCPClient({
    "googledrive-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Google Drive MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • get_tools() retrieves all available Google Drive tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model

Set up interactive chat interface

conversation_history = []

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Google Drive related question or task to the agent.\n")

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

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

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
What's happening:
  • We initialize an empty conversation_history list to maintain context across interactions
  • A while loop continuously accepts user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the ainvoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully

Run the application

if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • We call the main() function using asyncio.run() to start the application

Complete Code

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

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['googledrive']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "googledrive-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Google Drive related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

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

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

How to build Google Drive MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Google Drive MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Google Drive MCP with Claude Agent SDK

Google ADK

Google ADK

Use Google Drive MCP with Google ADK

Vercel AI SDK

Vercel AI SDK

Use Google Drive MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Google Drive MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Google Drive MCP with LlamaIndex

CrewAI

CrewAI

Use Google Drive MCP with CrewAI

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 LangChain?

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

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

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

Book a call↗Get started for free