domains / documents / google-drive-file-operations / google-drive-automation
The two copies implement the same high-level task (Google Drive file operations) through fundamentally different mechanisms. The davepoon copy is an MCP-based procedure that requires the Rube MCP server, Composio's Google Drive toolkit, and specific RUBE_* and GOOGLEDRIVE_* tool calls. The sickn33 copy is a standalone, script-based procedure that uses local Python scripts (auth.py, drive.py) with OAuth and explicitly states that no MCP server is required. Because each copy contains material steps and constraints the other lacks (MCP tool sequences vs. local CLI commands), crowning one would hide a real alternative implementation.
| Repository | Path |
|---|---|
| davepoon/buildwithclaude | plugins/all-skills/skills/google-drive-automation/SKILL.md |
| sickn33/agentic-awesome-skills | plugins/agentic-awesome-skills-claude/skills/google-drive-automation/SKILL.md |
| Role | Repository | Path |
|---|---|---|
| peer | davepoon/buildwithclaude | plugins/all-skills/skills/google-drive-automation/SKILL.md |
| peer | sickn33/agentic-awesome-skills | plugins/agentic-awesome-skills-claude/skills/google-drive-automation/SKILL.md |
| adapter | sickn33/agentic-awesome-skills | plugins/agentic-awesome-skills/skills/google-drive-automation/SKILL.md |
| adapter | sickn33/agentic-awesome-skills | skills/google-drive-automation/SKILL.md |
# Google Drive Automation Automate Google Drive file operations (upload, download, search, share, organize) using either an MCP-based or a standalone script-based approach. ## Approach 1: MCP-based (Rube/Composio) **Prerequisites**: - Rube MCP connected (`RUBE_SEARCH_TOOLS` available). - Active Google Drive connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googledrive`. **Setup**: 1. Verify Rube MCP is available. 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googledrive`. 3. Complete Google OAuth if connection is not ACTIVE. **Workflows**: - **Upload/Download**: Use `GOOGLEDRIVE_FIND_FILE` to locate folders, `GOOGLEDRIVE_UPLOAD_FILE` (max 5MB) or `GOOGLEDRIVE_RESUMABLE_UPLOAD` for larger files, and `GOOGLEDRIVE_DOWNLOAD_FILE` for downloads. - **Search**: Use `GOOGLEDRIVE_FIND_FILE` with query strings (e.g., `name contains 'report'`) and handle pagination via `nextPageToken`. - **Sharing**: Use `GOOGLEDRIVE_ADD_FILE_SHARING_PREFERENCE` to set permissions, specifying `type`, `role`, and `email_address` or `domain` as required. - **Folders**: Use `GOOGLEDRIVE_CREATE_FOLDER` to create folders and `GOOGLEDRIVE_MOVE_FILE` to organize files. ## Approach 2: Standalone Scripts (OAuth) **Prerequisites**: - Google Workspace account (personal Gmail not supported). - Local scripts `scripts/auth.py` and `scripts/drive.py` available. **Setup**: 1. Authenticate: `python scripts/auth.py login`. 2. Check status: `python scripts/auth.py status`. **Workflows**: - **Search**: `python scripts/drive.py search "query"` (supports full-text, title, URL, and native query formats). - **List**: `python scripts/drive.py list [FOLDER_ID]`. - **Upload**: `python scripts/drive.py upload FILE_PATH [--folder FOLDER_ID] [--name NEW_NAME]`. - **Download**: `python scripts/drive.py download FILE_ID ./output/path` (note: Google Workspace files cannot be downloaded directly). - **Folders**: `python scripts/drive.py create-folder "Name" [--parent FOLDER_ID]`. - **Move/Copy/Rename**: Use `move`, `copy`, and `rename` subcommands with appropriate file and folder IDs. ## Conflicts - **Repository**: davepoon/buildwithclaude vs. sickn33/agentic-awesome-skills - **Step**: The davepoon copy requires an MCP server and specific tool calls, while the sickn33 copy uses local Python scripts and explicitly excludes MCP dependencies. Choose the approach based on your environment's MCP support and account type (Workspace vs. personal).