What can you do with the Google Drive integration?

LiveContext exposes 44 operations on Google Drive, covering file, drive, comment and permission. Common uses include real-time sync, storage cleanup and file organization.

Which OAuth scopes does Google Drive require?

It depends on the operation: each one declares the scopes Google Drive requires for it. The most common are https://www.googleapis.com/auth/drive (26 operations), https://www.googleapis.com/auth/drive.readonly (17 operations) and https://www.googleapis.com/auth/drive.file (1 operation).

LiveContext

All integrations

Google Drive integration

Cloud file storage and synchronization service API for managing files, folders, and sharing. Upload, download, organize files, manage permissions, export Google Workspace documents, and access storage information. Perfect for building file management applications, backup tools, document collaboration systems, and cloud storage integrations.

44 toolsOAuthAPI docs

Connect Google Drive How integrations work

Common Google Drive use cases

real-time sync
storage cleanup
file organization
permanent deletion
access audit
fixing typos
collaboration
change detection
comment moderation
collaboration review

What you can do with Google Drive

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

File, 12 operations

POSTcopy_file
Creates a duplicate copy of a file in Google Drive. Can specify a new name and destination folder for the copy.
POSTcreate_file
Creates a new file's metadata in Google Drive (empty Google Doc/Sheet/Slides, a folder, or an empty binary file). Does not upload file content.
DELETEdelete_file
Permanently deletes a file from Google Drive, bypassing the trash. This action is irreversible and immediately removes the file.
GETdownload_file
Downloads the binary content of a file from Google Drive. Works with uploaded files like PDFs, images, and documents. Use export_file for Google Docs formats.
DELETEempty_trash
Permanently deletes all files in the user's trash. This action is irreversible and frees up storage quota.
GETexport_file
Exports Google Workspace files (Docs, Sheets, Slides) to downloadable formats like PDF, DOCX, XLSX, or plain text.
GETgenerate_file_ids
Generates unique file IDs for use in batch upload operations. Pre-generating IDs enables parallel uploads with predictable identifiers.
GETget_file
Retrieves metadata for a specific file including name, size, type, permissions, and modification history. Does not download file content.
GETlist_files
Lists files and folders in Google Drive. Supports powerful search queries to filter by name, type, parent folder, modification date, and shared status.
PATCHmove_file
Moves a file from one folder to another by updating its parent references. Files can exist in multiple folders simultaneously.
PATCHupdate_file
Updates a file's metadata. Can rename files, change descriptions, star or unstar, and move to or restore from trash.
POSTwatch_file
Creates a subscription to receive push notifications when a file changes. Enables real-time sync without polling.

Drive, 7 operations

POSTcreate_drive
Creates a new shared drive for team collaboration. Requires Google Workspace account with shared drive creation enabled.
DELETEdelete_drive
Permanently deletes a shared drive. Drive must be empty unless using admin access with allowItemDeletion.
GETget_drive
Retrieves metadata for a specific shared drive including name, capabilities, and restrictions.
POSThide_drive
Hides a shared drive from the user's default Drive view. The drive remains accessible and can be unhidden.
GETlist_drives
Lists all shared drives the user has access to. Shared drives are shared spaces owned by an organization.
POSTunhide_drive
Restores a previously hidden shared drive to the user's default Drive view.
PATCHupdate_drive
Updates shared drive settings like name, theme, or restrictions. Requires organizer role or admin access.

Comment, 5 operations

POSTcreate_comment
Creates a new comment on a file. For Google Docs, can anchor comments to specific text.
DELETEdelete_comment
Deletes a comment from a file. Only the comment author or file owner can delete.
GETget_comment
Retrieves a specific comment by ID including its content, author, and any replies.
GETlist_comments
Lists all comments on a file. Supports filtering by modification time and including deleted comments.
PATCHupdate_comment
Updates the text content of an existing comment. Only the comment author can edit.

Permission, 5 operations

DELETEdelete_permission
Deletes a permission, immediately revoking the grantee's access to the file.
GETget_permission
Retrieves a specific permission for a file by its ID. Returns the permission type, role, and grantee details.
GETlist_permissions
Lists all permissions on a file showing who has access and their access level. Useful for auditing sharing and managing collaborators.
POSTshare_file
Shares a file with a user or group by creating a permission. Controls access level (viewer, commenter, editor) and notification settings.
PATCHupdate_permission
Updates an existing permission to change access level. Can upgrade/downgrade roles or set expiration.

Reply, 5 operations

POSTcreate_reply
Creates a reply to an existing comment. Can also resolve or reopen the comment thread.
DELETEdelete_reply
Deletes a reply from a comment thread. Only the reply author or file owner can delete.
GETget_reply
Retrieves a specific reply by ID with its content and author information.
GETlist_replies
Lists all replies to a specific comment. Useful for displaying threaded discussions.
PATCHupdate_reply
Updates the text content of an existing reply. Only the reply author can edit.

Revision, 4 operations

DELETEdelete_revision
Permanently deletes a file revision. Some revisions like the current head cannot be deleted.
GETget_revision
Retrieves metadata for a specific file revision or downloads its content.
GETlist_revisions
Lists all saved revisions of a file. Shows version history with timestamps and authors.
PATCHupdate_revision
Updates revision settings like keep-forever to prevent auto-deletion or publish status for Google Docs.

Change, 3 operations

GETget_changes_start_page_token
Gets a starting page token for future change requests. Use this token to track changes from the current point in time.
GETlist_changes
Lists changes to files and folders since a given page token. Essential for building sync applications.
POSTwatch_changes
Creates a subscription to receive push notifications when any file changes. Enables real-time sync without polling.

About, 1 operation

GETget_about
Retrieves information about the user's Drive including storage quota, user profile, and supported import/export formats.

Channel, 1 operation

POSTstop_channel
Stops receiving push notifications on a channel. Use when you no longer need real-time updates.

Folder, 1 operation

POSTcreate_folder
Creates a new folder in Google Drive. Folders are special files with a specific mimeType for organizing other files.

OAuth scopes Google Drive requires

Each operation declares the scopes Google Drive requires for it.

https://www.googleapis.com/auth/driveneeded by copy_file, create_comment, create_drive and 23 more
https://www.googleapis.com/auth/drive.readonlyneeded by download_file, export_file, get_about and 14 more
https://www.googleapis.com/auth/drive.fileneeded by generate_file_ids

Google Drive API rate limits

10 requests per second
1,000,000,000 requests per day

Google Drive v3 uses quota-unit accounting: 1,000,000 units/minute/project, 325,000 units/minute/user/project, 400,000,000 units/day/project. Per-method cost varies (read=5, list=100, download=200, update=50, generateIds=5). Per-user upload cap: 750 GB/day, max file 5 TB. Exceeding minute quota returns 403 'User rate limit exceeded'.

These are the limits Google Drive documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Google Drive documentation for current values.

Use Google Drive from Claude Code, Cursor or Codex

Connect Google Drive in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Google Drive operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Google Drive

Create your workspace
Sign up free. Nothing to install.
Connect Google Drive once
Add your Google Drive connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Google Drive integration FAQ

What can you do with the Google Drive integration?: LiveContext exposes 44 operations on Google Drive, covering file, drive, comment and permission. Common uses include real-time sync, storage cleanup and file organization.
Which OAuth scopes does Google Drive require?: It depends on the operation: each one declares the scopes Google Drive requires for it. The most common are https://www.googleapis.com/auth/drive (26 operations), https://www.googleapis.com/auth/drive.readonly (17 operations) and https://www.googleapis.com/auth/drive.file (1 operation).
What are the Google Drive API rate limits?: Google Drive documents 10 requests per second and 1,000,000,000 requests per day. Google Drive v3 uses quota-unit accounting: 1,000,000 units/minute/project, 325,000 units/minute/user/project, 400,000,000 units/day/project. Per-method cost varies (read=5, list=100, download=200, update=50, generateIds=5). Per-user upload cap: 750 GB/day, max file 5 TB. Exceeding minute quota returns 403 'User rate limit exceeded'. Limits are set by Google Drive and can depend on your plan.