mcpField
G
google-drive-automation

google-drive-automation

github.com/sickn33Productivity48.7k912 installsUpdated today
Repository

About google-drive-automation

A Google Drive automation skill for operations on files and folders through local scripts. It covers search, listing, uploads, downloads, and organization, while requiring users to verify unavailable authentication and Drive script dependencies before relying on them.

Key features

  1. 01Search by text, title, URL, or query
  2. 02List and organize files and folders
  3. 03Upload files to Drive folders
  4. 04Download regular files
  5. 05OAuth login and status commands

Use cases

  1. 01Finding a report by name or contents
  2. 02Uploading a document to a specified folder
  3. 03Listing the contents of a Drive folder
  4. 04Downloading a regular file for local use

MCP support

The skill describes direct local-script automation and explicitly says no MCP server is required. It does not expose MCP tools.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill google-drive-automation

After installing, type/google-drive-automationin Claude Code to confirm it loaded.

Details

From the project README

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):

python scripts/auth.py login

Check authentication status:

python scripts/auth.py status

Logout when needed:

python scripts/auth.py logout

Read Commands

All operations via scripts/drive.py. Auto-authenticates on first use if not logged in.

# Search for files (full-text search)
python scripts/drive.py search "quarterly report"

# Search by title only
python scripts/drive.py search "title:budget"

# Search using Google Drive URL (extracts ID automatically)
python scripts/drive.py search "https://drive.google.com/drive/folders/1ABC123..."

# Search files shared with you
python scripts/drive.py search --shared-with-me

# Search with pagination
python scripts/drive.py search "report" --limit 5 --page-token "..."

# Find a folder by exact name
python scripts/drive.py find-folder "Project Documents"

# List files in root Drive
python scripts/drive.py list

# List files in a specific folder
python scripts/drive.py list 1ABC123xyz --limit 20

# Download a file
python scripts/drive.py download 1ABC123xyz ./downloads/report.pdf

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

# Upload a file to Drive root
python scripts/drive.py upload ~/Documents/report.pdf

# Upload to a specific folder
python scripts/drive.py upload ~/Documents/report.pdf --folder 1ABC123xyz

# Upload with a custom name
python scripts/drive.py upload ~/Documents/report.pdf --name "Q4 Report.pdf"

# Create a new folder
python scripts/drive.py create-folder "Project Documents"

# Create a folder inside another folder
python scripts/drive.py create-folder "Attachments" --parent 1ABC123xyz

# Move a file to a different folder
python scripts/drive.py move FILE_ID DESTINATION_FOLDER_ID

# Copy a file
python scripts/drive.py copy FILE_ID
python scripts/drive.py copy FILE_ID --name "Report Copy" --folder 1ABC123xyz

# Rename a file or folder
python scripts/drive.py rename FILE_ID "New Name.pdf"

# Move a file to trash
python scripts/drive.py trash FILE_ID

Search Query Formats

The search command supports multiple query formats:

FormatExampleDescription
Full-text"quarterly report"Searches file contents and names
Title"title:budget"Searches file names only
URLhttps://drive.google.com/...Extracts and uses file/folder ID
Folder ID1ABC123...Lists folder contents (25+ char IDs)
Native querymimeType='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.

Comments

Markdown supported