Sign in Book a demo
Back to Tools
Productivity & Docs OAuth
Build Your Agent View Drive Documentation
google-drive logo

Google Drive MCP Tools for AI Agents

Let an agent search, upload, rename, move, and share Google Drive files and folders through Arcade.

Available Tools

20 tools available in this integration

GoogleDrive.CheckFileAccess

Check whether this app can already read each of several Drive files, in one batched

GoogleDrive.CreateFolder

Create a new folder in Google Drive.

GoogleDrive.DownloadFile

Download a blob file (non-workspace file) from Google Drive as base64 encoded content.

GoogleDrive.DownloadFileChunk

Download a byte range of a file's raw content from Google Drive, as base64.

GoogleDrive.DownloadFileThumbnail

Download the thumbnail Google Drive made of a file, as a base64 encoded image.

GoogleDrive.GenerateGoogleFilePickerUrl

Generate a URL where the user can grant this app access to specific Drive files.

GoogleDrive.GetFile

Get a Google Drive file: the user sees it in a preview where they can view it, save it,

GoogleDrive.GetFileTreeStructure

Get the file/folder tree structure of the user's entire Google Drive.

GoogleDrive.ListFilePermissions

List permissions on a Google Drive file or folder.

GoogleDrive.MoveFile

Move a file or folder to a different folder within the same Google Drive.

GoogleDrive.RemoveAllCollaborators

Remove all user collaborators (and optionally groups) from a Google Drive file.

GoogleDrive.RemoveOtherCollaborators

Remove all user collaborators (and optionally groups) from a Google Drive file.

GoogleDrive.RenameFile

Rename a file or folder in Google Drive.

GoogleDrive.RevokeFileAccess

Revoke access for specific people or groups on a Google Drive file.

GoogleDrive.SearchFiles

Search for files in Google Drive.

GoogleDrive.SetGeneralAccess

Change the 'General access' (link sharing) setting on a Google Drive file.

GoogleDrive.ShareFile

Share a file or folder in Google Drive with specific people by granting them permissions.

GoogleDrive.UpdateFile

Rename a file or folder in Google Drive.

GoogleDrive.UploadFile

Upload a file to Google Drive from a URL.

GoogleDrive.WhoAmI

Get comprehensive user profile and Google Drive environment information.

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "find the latest project brief, check who can access it, and share it with the launch team." Arcade picks the right Google Drive actions without guessing file IDs or folder IDs.

Up to 100x fewer tokens

Google Drive searches return lightweight file metadata and tree information before the agent downloads content, so it can find the right document without loading an entire Drive into the model.

Complete the workflow end to end

Search Drive, inspect the file tree, check access, share or move the file, and return the resulting permissions through one toolkit designed around the complete file-management task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing Google Drive

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For Google Drive, you can implement some of these policies:

Access when tools are listed for a user
  • Hide GoogleDrive.RemoveAllCollaborators from agents unless the roles your IDP marks as Drive administrators are active, so an agent cannot remove every collaborator from a shared file.
  • Restrict GoogleDrive.RevokeFileAccess to agents operating under your access-management role, so routine agents cannot cut off named people or groups from shared files.
  • Deny GoogleDrive.SetGeneralAccess to agents outside your Drive-owner role, so an agent cannot turn a private file into a link-accessible document.
  • Hide GoogleDrive.RemoveOtherCollaborators from agents unless the roles your IDP marks as Drive access administrators are active, so routine agents cannot remove other people from shared files.
  • Restrict GoogleDrive.UpdateFile to agents operating under your Drive content-manager role, so unapproved automation cannot rename controlled files or folders.
Pre-execution before each tool call
  • Require human approval before GoogleDrive.ShareFile runs, so an agent cannot grant a customer, vendor, or external group access to your files without review.
  • Block GoogleDrive.UploadFile when the source URL is outside your approved domains, so an agent cannot import untrusted content into your Drive.
  • Require human approval before GoogleDrive.MoveFile changes a file's folder, so an agent cannot remove records from a controlled or legal-hold location.
  • Require human approval before GoogleDrive.RemoveOtherCollaborators runs, so an agent cannot silently remove a colleague, customer, or vendor from a shared file.
  • Block GoogleDrive.UpdateFile when it changes the name of a file or folder in your controlled records areas, so an agent cannot obscure or misfile records through an unreviewed rename.
Post-execution after the tool returns
  • Redact credentials, access tokens, and other secret patterns from GoogleDrive.DownloadFile results before file contents reach the model.
  • Strip filenames and folder names matching your confidential-project patterns from GoogleDrive.GetFileTreeStructure results, so private initiative names do not reach the model.
  • Redact personal profile fields, organization details, and account identifiers from GoogleDrive.WhoAmI results before the model sees them.
  • Deny the output of GoogleDrive.DownloadFileThumbnail for files in your confidential folders, so private document previews never reach the model.
  • Redact file contents from GoogleDrive.GetFile results when the file is marked Confidential or subject to legal hold before the model sees its preview.

How to use Google Drive with your agent

Connect this toolkit to your MCP client and give an agent access to the user's Drive. Follow the walkthrough to configure authentication and run your first file task.

Your questions, answered

A Google Drive MCP server exposes Drive capabilities as structured tools that an AI agent can call through the Model Context Protocol. After a user authorizes their Google account, the agent can search files, read metadata, download content, and manage files or permissions allowed by that authorization.

Google Drive does not provide the first-party MCP server used here. Arcade provides the MCP gateway, per-user OAuth, agent-optimized actions, approval workflows, redaction, and access controls across clients and frameworks.

Arcade agents can search Drive, inspect the full file tree, check access, preview and download files or thumbnails, upload files from URLs, create folders, rename and move files, and manage sharing and general access. They can also list permissions, share files, revoke access, and remove collaborators.

Arcade requests the Google OAuth scopes required by the actions you enable. Read-only workflows need Drive read or metadata access, while uploading, organizing, or changing sharing and permissions requires write access; grant the narrowest scopes that support your workflow.

Yes. Each user authorizes their own Google Drive account through OAuth. Actions run under that user's authorization, so the agent can access only the files and permissions that user has approved.

Yes. Contextual Access policies can require human approval before consequential Google Drive actions such as sharing a file, changing link access, revoking access, removing collaborators, or moving content. The call proceeds only after the policy's conditions have been satisfied.

Arcade proxies Google Drive API calls and does not persist your content as part of normal tool execution. OAuth credentials are brokered and stored encrypted at rest, and the model never receives them.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade refreshes access while the user's Google authorization remains valid. If access is revoked, rotated, or can no longer be refreshed, actions stop until the user reconnects their Google account.

Google Drive API quotas and rate limits still apply to actions performed through Arcade, including per-user and per-project request quotas. Drive may also limit large downloads or uploads, so high-volume workflows should handle pagination, retries, and quota errors.

Ready to actually ship your agent?

Connect your agent to Google Drive with managed OAuth, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the Google Drive Quickstart