TL;DR
Connecting Claude to Google Drive via the Model Context Protocol (MCP) lets your AI assistant read, search, and manage files directly without manual copy-pasting.
Composio gives Claude access to 76 ready-to-use Drive tools, find, create, move, share, and monitor files, with authentication and routing handled automatically, getting you connected in under 10 minutes.
The Composio free tier includes 100,000 tool calls per month with no credit card required.
Google Drive is often where important project files, reports, documentation, and shared resources live. Connecting it to Claude Code through Composio lets your agent work with those files directly instead of making you jump between tools.
With 76 Google Drive tools available out of the box, Claude can find and create files, organize folders, manage permissions, handle comments, upload and download content, monitor changes, and more. In this guide, we'll look at what you can do with Google Drive in Claude and share practical prompts you can try for each workflow.
How to connect Google Drive MCP with Claude Cowork
Prerequisites
Claude Desktop with access to Cowork.
Access to the Google Drive account you want to connect.
Composio MCP.
Open Customize
Claude Desktop → Customize → Connectors → +
Add the Composio MCP server
Connectors → Add custom connector → Paste https://connect.composio.dev/mcp → Connect
Authorize in your browser
Click Connect → Browser opens → Authorize Composio → Continue
Connect your Google Drive account
Return to Cowork → Ask the agent to connect to Google Drive or give it a Google Drive-related task → Authenticate Google Drive when prompted → Authorize access
For example:
"Create a new folder named 'Invoices'"
"Share last uploaded file with your team"
"Add comment to project proposal document"
That's it. Composio's tools are now available in Cowork, and your Google Drive account is ready to use.
How to connect Google Drive to Claude Code using Composio
Add the Composio MCP to Claude
Open Composio → Generate MCP URL → Add the Composio MCP to Claude
Start Claude Code
Open your terminal → Run claude → Claude Code starts
Open your MCP list
Open Claude Code → Run /mcp → View your available MCP servers
Select Composio and click Authenticate
Open MCP list → Select Composio → Click Authenticate
Authorize Composio
Authentication opens the Composio OAuth page → Authorize Composio → Complete the OAuth flow → Return to Claude Code
Connect your Google Drive account
Ask Claude to connect to your account → Open the authentication link → Authorize Google Drive → Start using Google Drive with Claude Code
Start connecting Google Drive to Claude today through the Composio Google Drive toolkit, with no credit card and no Cloud Console configuration required.
What can you do with Google Drive in Claude Code?
Connecting Google Drive to Claude through Composio gives your agent access to a broad set of Google Drive actions. Instead of switching between your terminal, Claude, and Google Drive, you can ask Claude to find files, create folders, upload content, manage sharing permissions, work with comments, organize files, and monitor changes directly from your conversation.
The integration includes 76 tools covering everyday file management as well as more advanced Google Drive operations. Here are some of the most useful ways to put those tools to work.
Find files and folders
Claude can search your Google Drive to locate files and folders without requiring you to know their exact location. Composio provides dedicated Find file and Find folder tools, alongside metadata tools that let Claude retrieve additional information about the results.
If your Drive spans dozens of project folders and shared directories, searching by exact location quickly becomes impractical. Describe what you're looking for in natural language and Claude will locate the file before performing the next action on it.
Prompt to try:
"Find the latest project proposal in my Google Drive and give me the file name, location, and last modified date."
Create files and folders
Claude can create new files and folders in Google Drive using Composio's Create File or Folder, Create a File from Text, and Create a folder tools. You can specify where a new item should live instead of manually creating and organizing it in Drive.
The text-to-file tool is especially useful for agent workflows. Claude can generate content during a coding or research session and then turn that output into a new Drive file. It supports content up to 10MB and can convert supported formats into Google Workspace file types.
Prompt to try:
"Create a folder called 'Q3 Research' in Google Drive, then create a document inside it containing a summary of our findings from this session."
Upload files to Google Drive
Composio gives Claude several ways to upload files, including Upload File, Resumable Upload, and Upload File from URL to Drive. Standard uploads support files up to 5MB, while resumable uploads are available for workflows that require a resumable transfer process.
Claude can also fetch a file from a URL and upload it to Drive server-side. This can be useful when your workflow produces downloadable assets, reports, exports, or other files that you want stored centrally without manually downloading and re-uploading them.
Prompt to try:
"Upload the generated report to my 'Client Reports' folder in Google Drive and tell me where you saved it."
Download and export files
Claude can retrieve files from Drive with Download a file from Google Drive. For Google Workspace documents, the Export Google Workspace file tool can export a document into a requested MIME type.
A Claude Code session can open by pulling a file from Drive, process it, and write the result straight back. Drive becomes part of the pipeline rather than a separate manual step.
Prompt to try:
"Find the latest project brief in Google Drive, export it to PDF, and download the exported version."
Copy files
The Copy file with advanced options tool lets Claude create copies of existing Drive files while applying requested updates using patch semantics. This is useful when you want to use an existing document as the starting point for a new deliverable.
For recurring workflows, you could keep templates in Drive and ask Claude to duplicate them for each new project. The copy can then be renamed, moved, or have its metadata updated with other available tools.
Prompt to try:
"Find our 'Client Report Template', make a copy called 'Acme Q3 Report', and move the copy into the Acme client folder."
Move and organize files
Claude can reorganize your Drive with tools such as Move File, Insert File Parent (v2), Delete Parent (v2), and Insert Child Into Folder (v2). These give an agent more control over where files are located and how they relate to folders.
That opens up useful organization workflows. Claude could find files matching particular criteria and move them into the correct project folders, or help clean up a Drive structure after a project is completed.
Prompt to try:
"Find all files related to the Q2 campaign and move them into the 'Marketing/Q2 Campaign' folder. Show me what you plan to move before making any changes."
Manage file metadata and properties
Claude can retrieve and modify file metadata using Get File Metadata, Update File (Metadata), and Update File Metadata (PATCH v2). Composio also exposes Google Drive v2 property tools for inserting, listing, retrieving, patching, updating, and deleting properties.
Teams tagging deliverables by client, sprint, or status can have Claude read and update metadata and custom properties, feeding that classification data directly into downstream automation.
Prompt to try:
"Get the metadata for the latest sales report and show me its file ID, name, MIME type, modified date, and parent folder."
Manage sharing permissions
Claude can work with Google Drive permissions using Create Permission, Get Permission, List Permissions, Patch Permission, Update Permission, Delete Permission, and Get Permission ID for Email.
This allows sharing to become part of an automated workflow. After Claude creates or finds a file, for example, it can inspect who currently has access and then make an authorized permission change rather than requiring you to open Google's sharing interface manually.
Prompt to try:
"Find the 'Q3 Strategy' file and list everyone who currently has access. Do not change any permissions."
Create and manage comments
Composio exposes tools for Create Comment, Get Comment, List Comments, Update Comment, and Delete Comment. Claude can therefore interact with discussion threads attached to Google Drive files.
During document review cycles, Claude can pull all open comments from a file, surface unresolved feedback, and add a targeted comment for a specific collaborator — without anyone needing to open the document manually.
Prompt to try:
"Find the project proposal, list all of its comments, and summarize the feedback that still needs to be addressed."
Reply to comments
Claude can also interact with individual replies through Create Reply, Get Reply, List Replies to Comment, Update Reply, and Delete Reply. That gives it access to the conversation underneath a Drive comment rather than only the top-level comment.
For collaborative documents, this means Claude can inspect the context of a discussion before helping you respond. You can use it to summarize long comment threads or, after reviewing the proposed wording, post a reply.
Prompt to try:
"Find the latest comment thread on the project proposal, summarize the discussion, and draft a reply. Wait for my approval before posting it."
Work with file revisions
Claude can inspect Drive version information with Get Revision and List File Revisions. Composio also provides Update File Revision Metadata and Delete Revision for supported revision-management operations.
If a spec document changes unexpectedly or a collaborator overwrites content, Claude can list available revisions and retrieve modification details so you can identify the right version before taking action.
Prompt to try:
"List the available revisions of the project plan and show me their modification details. Don't delete or update anything."
Edit and update file content
The integration includes Edit File, Upload/Update File Content, and related update tools. Edit File overwrites an existing Drive file's entire content with new text and supports content up to 10MB.
Because some of these operations replace existing content, they are better suited to deliberate workflows where the target file has already been identified. You can have Claude find the file first, confirm it with you, and then perform the update.
Prompt to try:
"Find 'weekly-status.txt' in Google Drive and show me its file details. Then ask for confirmation before replacing its content with this week's status update."
Create and manage shortcuts
The Create Shortcut to File/Folder tool lets Claude create Drive shortcuts pointing to existing files or folders. This is useful when the same resource needs to be easily accessible from multiple areas of your Drive without creating duplicate copies.
For example, a shared project document could remain in its primary project folder while Claude creates a shortcut inside another team's workspace.
Prompt to try:
"Find our current brand guidelines and create a shortcut to them inside the 'Marketing Resources' folder."
Work with Shared Drives
Claude can perform several Shared Drive operations, including Create Shared Drive, Get Shared Drive, List Shared Drives, Update Shared Drive, Hide Shared Drive, Unhide Shared Drive, and Delete Shared Drive.
Workspace admins managing access across multiple teams can have Claude list available Shared Drives, retrieve drive-level details, and perform authorized administrative actions without leaving their agent workflow.
Prompt to try:
"List the Shared Drives I can access and give me their names and IDs. Don't make any changes."
Manage file labels
Claude can inspect and change Google Drive labels using List File Labels and Modify File Labels. Labels provide another way to organize and classify files beyond their folder structure.
Operations teams that classify documents by status, department, or project type can have Claude inspect and update Drive labels as part of a broader file-management workflow, checking what's already applied before making any changes.
Prompt to try:
"Find the latest client proposal and list all Google Drive labels currently applied to it."
Manage trash and deleted files
Composio includes Trash File, Untrash File, Delete folder or file, and Empty Trash. These cover both recoverable deletion workflows and permanent deletion operations.
Because permanent deletion and emptying the trash are destructive actions, it is useful to build confirmation into your prompts. Claude can identify the relevant files first and show you what would be affected before you authorize the deletion.
Prompt to try:
"Find files in the 'Old Campaign' folder that I might want to remove and show me the list. Do not trash or permanently delete anything until I confirm."
Monitor changes in Google Drive
The Watch Drive Changes tool allows Claude-powered workflows to subscribe to changes affecting a user or Shared Drive. Composio also provides Get Changes Start Page Token and List Changes for working with Drive's change history.
These capabilities are useful when building agents that need to respond to Drive activity rather than only acting when manually prompted. For example, a workflow could track when project files change and use those events as part of a larger automation.
Prompt to try:
"Set up a watch for changes in my Google Drive so my workflow can detect when files are updated."
Watch individual files for changes
If you only care about one important file, Watch File for Changes provides a more targeted option. Instead of monitoring general Drive activity, an agent can subscribe to push notifications associated with a specific file.
This could support workflows around important specifications, reports, or shared project documents. When the watched resource changes, another part of your application can decide what should happen next.
Prompt to try:
"Find the 'Product Requirements' file and set up a watch for changes to that file."
Stop watching Drive resources
Composio also exposes Stop Watch Channel, which allows an existing resource watch channel to be stopped. This gives applications a way to clean up subscriptions that are no longer required.
It is particularly useful when monitoring is temporary. A project-specific agent could watch a resource while work is active and stop the channel after the project is completed.
Prompt to try:
"Stop the Google Drive watch channel with this channel ID: [CHANNEL ID]."
Work with access proposals and approvals
Claude can use List Access Proposals to retrieve pending access proposals for a file and List Approvals to inspect approvals used in workflow-based access control.
These tools can help with environments where document access requires more structured governance. Instead of manually checking individual files, an agent can retrieve pending access information and present it as part of an administrative workflow.
Prompt to try:
"Find the project finance document and list any pending access proposals. Don't approve or modify anything."
Generate file IDs
If you're building custom multi-step agent workflows, this tool gives you more precise control over resource creation. The Generate File IDs tool creates IDs that can be supplied in subsequent Google Drive create or copy requests. This is a more technical capability, but it can be useful when building multi-step agent workflows that need identifiers before creating resources.
Claude Code can handle this as part of a larger sequence rather than requiring you to manually manage IDs. The generated values can then be passed into supported Google Drive operations.
Prompt to try:
"Generate three Google Drive file IDs and return them to me without creating any files yet."
Inspect your Drive and system capabilities
The Get about tool retrieves information about the authenticated user, their Drive, and relevant system capabilities. Claude can use this information to understand the Drive environment before attempting more complex operations.
Composio also exposes Get App, which retrieves information about a specific Google Drive app by ID. These tools are primarily useful for diagnostics, integrations, and advanced agent workflows.
Prompt to try:
"Get information about my connected Google Drive account and summarize the available Drive capabilities."
Work with Google Drive API v2 relationships
If you're building custom Drive pipelines that need precise folder-structure control, these lower-level v2 tools give you more granularity than the standard find, move, and folder operations. Composio exposes several Google Drive API v2 tools, including Get Child Reference (v2), List Folder Children (v2), Insert Child Into Folder (v2), Delete Child (v2), Get Parent Reference (v2), Insert File Parent (v2), and Delete Parent (v2).
Developers building custom Drive pipelines, where precise parent-child relationship management matters, will reach for these when the higher-level find, move, and folder tools aren't granular enough.
Prompt to try:
"List the child references for the folder with ID [FOLDER ID] using the Google Drive v2 tools and return their IDs."
Build multi-step Google Drive workflows
The biggest advantage of exposing these tools to Claude Code is that they can be combined. A task does not have to stop at finding a file. Claude can find a document, inspect its metadata, check its permissions, create a copy, move that copy into another folder, and then share it with the appropriate people.
That turns Google Drive into an actionable part of an agent workflow rather than a passive source of files. For sensitive or destructive actions, you can explicitly instruct Claude to pause for confirmation before modifying permissions, overwriting content, trashing files, or permanently deleting anything.
Prompt to try:
"Find our latest client report, create a copy, rename it for this month, move it into the current month's reporting folder, and show me the existing permissions. Ask for my confirmation before changing sharing permissions."
Give Claude Code or Cowork the ability to work directly with your Google Drive files, folders, permissions, comments, and more. Connect Google Drive through Composio and start building agent workflows with 76 ready-to-use tools. Get started with the free tier in Composio.
FAQs
Is Composio's free tier enough for personal Google Drive workflows?
The free tier provides 100,000 tool calls per month with unlimited connections and no credit card required. For a solo consultant or freelancer using Claude to query Drive files daily, this covers standard usage without hitting the limit.
Can I revoke Claude's access to Google Drive without deleting my account?
Yes. Go to your Google Account security settings, navigate to the section showing your connections to third-party apps and services, and delete the connection. If you used Composio, you can also remove access directly from the Composio dashboard.
Glossary
MCP (Model Context Protocol): A standardized way for AI assistants like Claude to connect to external tools and data sources without custom code for each connection.
OAuth 2.0: The system Google uses to let apps access your Drive without sharing your password directly. It issues two types of tokens: a short-lived access token used for each request, and a longer-lived refresh token that obtains new access tokens without requiring you to log in again. For unverified Google apps in Testing mode, refresh tokens expire after 7 days.
MCP server: The software layer that sits between Claude Desktop and an external tool like Google Drive, translating Claude's requests into the tool's API calls.
Tool Router: Composio's routing layer that inspects incoming requests from Claude and directs them to the correct integrated toolkit based on your authenticated connections, without requiring separate MCP servers for each tool.
Zero Data Retention (ZDR): A Composio Pro add-on that prevents Composio from storing your request and response payloads, billing at $0.0001 per tool call.
Connect Link: Composio's setup step that connects your Drive account in a browser session and stores credentials automatically, so your agent can start acting on files without manual Cloud Console configuration.