Google Drive MCP integration for AI agents.
Connect AI agents to Google Drive file discovery, metadata, exports, shared drives, permissions, comments, and revisions.
- ACTION CONTRACTS
- 43
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Google Drive integration exposes
The Google Drive Agent App helps an agent identify files and retrieve metadata or exports without browsing folders manually. File IDs provide a stable boundary for subsequent reads, comments, permission inspection, or revision work.
Drive permissions can expose a large knowledge surface. Agents should begin with a narrow file query or known file ID, distinguish My Drive from shared drives, and avoid changing permissions or deleting files without direct confirmation.
VERIFIED ACTION SAMPLE
Real Google Drive capabilities.
Showing 12 of 43 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
about.getREVIEWGet Drive account information such as user details, quota, and supported capabilities.
INPUTS: fields
accessproposals.listREVIEWList pending access proposals for a specific Drive file.
INPUTS: fileId / includeSharedDrives / pageSize / pageToken
approvals.listREVIEWList approvals associated with a specific Drive file.
INPUTS: fileId / includeSharedDrives / pageSize / pageToken
apps.getREVIEWGet metadata for a specific Google Drive app by app ID.
INPUTS: appId
changes.getStartPageTokenREVIEWGet the page token for monitoring future Drive changes.
INPUTS: driveId / supportsAllDrives / includeItemsFromAllDrives
changes.listREVIEWList file and drive changes for incremental sync workflows.
INPUTS: pageToken / pageSize / driveId / spaces / includeLabels
comments.createREVIEWCreate a comment on a Drive file, optionally with anchor or quoted file content.
INPUTS: fileId / content / anchor / quoted_file_content_value / quoted_file_content_mime_type
comments.deleteREVIEWPermanently delete a comment thread from a Drive file.
INPUTS: fileId / commentId
comments.getREVIEWGet a specific comment on a Drive file by comment ID.
INPUTS: fileId / commentId / includeDeleted
comments.listREVIEWList comments on a Drive file with pagination.
INPUTS: fileId / fields / pageSize / pageToken / includeDeleted
comments.updateREVIEWUpdate the content of an existing Drive file comment.
INPUTS: fileId / commentId / fields / content / resolved
drives.createREVIEWCreate a new shared drive.
INPUTS: name / requestId / hidden / themeId / colorRgb
INPUT CONTRACTS
Know what the action needs before it runs.
about.get
fieldsOPTIONAL- The fields to include in the response.
accessproposals.list
fileIdOPTIONAL- The ID of the file.
includeSharedDrivesOPTIONAL- When true, includes files from shared drives.
pageSizeOPTIONAL- The maximum number of items to return per page (1–100).
pageTokenOPTIONAL- The token for continuing a previous list request on the next page.
approvals.list
fileIdOPTIONAL- The ID of the file.
includeSharedDrivesOPTIONAL- When true, includes files from shared drives.
pageSizeOPTIONAL- The maximum number of items to return per page (1–100).
pageTokenOPTIONAL- The token for continuing a previous list request on the next page.
apps.get
appIdREQUIRED- The ID of the Google Drive app to retrieve.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Document retrieval
Find a named file in a bounded location, verify its owner and modified time, and export only the required representation.
Access review
List permissions for a selected document and produce a review report without changing access.
Source collection
Collect metadata for a defined set of project documents before a human selects what the agent may read.
SAFETY BOUNDARY
Operate Google Drive with explicit limits
- Constrain file searches by location, type, owner, or modified time.
- Treat exported document content as potentially sensitive.
- Require confirmation for permission, move, trash, or delete actions.
- Preserve file IDs and modified timestamps for verification.
CONNECTION MODEL
OAuth 2.0
Google Drive uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 0
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 43
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Google Drive.