Can AI agents automate Google Drive?

Google Drive is automatable today through Drive API v3. The HTTPS JSON REST service creates, copies, updates, downloads, exports, searches, shares, labels, comments on, and watches files and shared drives. OAuth 2.0 user consent is the normal access path. A service account can use files or folders shared directly with it or, after super-admin approval, act under domain-wide delegation. Google publishes official client libraries in common languages. The googleworkspace/cli `gws` client dynamically exposes the Drive discovery surface as structured JSON, with schema introspection, dry-run, auto-pagination, and a `drive +upload` helper; its README states it is not an officially supported Google product. Google also operates a remote Drive MCP server at drivemcp.googleapis.com with eight tools for search, metadata, permissions, recent files, read, create, copy, and download. The MCP path inherits user permissions but remains Developer Preview, so it is useful rather than production-complete. Google warns that Drive content can cause indirect prompt injection. Native Workspace admin, Vault, and DLP controls sit outside this API. Workflow-connector catalogs and computer-use viability were not established.

Best path today: api · Overall automatability: 8/10