Lightweight Google Drive integration with standalone OAuth authentication. No MCP server required. Full read/write access.

Supporting material availability This catalog copy contains the inline guidance below, but does not include the following supporting paths. They are external prerequisites, not bundled files: <support root /scripts/auth.py <support root /scripts/drive.py Ask for the original supporting material or an existing installation before using a step that depends on these paths; this catalog does not identify a verified download source for them. Resolve each path relative to that installation, inspect its contents, and verify any applicable license and execution prerequisites. Do not run a command or claim a referenced procedure was followed until its required file exists. Do not fabricate the missing scripts or treat an unrelated file with the same name as equivalent. Independent steps fully documented here can proceed within the user’s authorized scope; report any dependent step as unavailable. Google Drive Lightweight Google Drive integration with standalone OAuth authentication. No MCP server required. Full read/write access. Account support and OAuth scopes depend on the missing upstream scripts; verify the actual OAuth application before login. This entry does not establish a general restriction on personal Google accounts. When to Use You need to search, list, upload, download, move, or organize Google Drive files and folders. The task requires direct Drive read/write automation through local scripts in a Workspace account. You want file level Drive operations without introducing an MCP server dependency. First Time Setup Authenticate with Google (opens browser): Check authentication status: Logout when needed: Read Commands All operations via scripts/drive.py . Auto authenticates on first use if not logged in. Resolve scripts relative to the reviewed <support root , not an unrelated repository scripts/ folder. Before writes, confirm exact file/folder IDs, destination and permissions; moving/trashing content may affect collaborators. A read request does not authorize changes, sharing or broader OAuth scopes. Write Commands Search Query Formats The search command supports multiple query formats: Format Example Description Full text "quarterly report" Searches file contents and names Title "title:budget" Searches file names only URL https://drive.google.com/... Extracts and uses file/folder ID Folder ID 1ABC123... Lists folder contents (25+ char IDs) Native query mimeType='application/pdf' Pass through Drive query syntax File ID Format Google Drive uses long IDs like 1ABC123xyz abc123 . Get IDs from: search results find folder results list results Google Drive URLs Download Limitations Regular files (PDFs, images, etc.) download directly Google Docs/Sheets/Slides cannot be downloaded via this tool For Google Workspace files, use export or dedicated tools Token Management Upstream describes token storage using the system keyring; verify actual implementation and fallback behavior before relying on it: macOS : Keychain Windows : Windows Credential Locker Linux : Secret Service API (GNOME Keyring, KDE Wallet, etc.) Service name: google drive skill oauth The upstream integration describes a cloud function refresh flow. Verify its operator, destination, scopes and token handling from the actual scripts before transmitting tokens; do not assume Google operates an endpoint because it is hosted on its infrastructure. Limitations Use this skill only when the task clearly matches the scope described above. Do not treat the output as a substitute for environment specific validation, testing, or expert review. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

google-drive-automation