Claude Code Explorations: Custom Google Drive Script

​

Disclaimer

• USE THIS DISCUSSION AT YOUR OWN RISK.
• NEVER run code without reviewing every single line.
• There may be multiple ways to achieve the same goal. (e.g. MCP, which I will cover in another post.) What’s discussed here is just one way, not the only way or best way.
• What’s discussed here may not be kept up-to-date

​

Why This Matters: The Power of Custom Scripts

​

Saving Your Scripts to Claude Code’s Memory

• alias: The command name Claude will use (conventionally prefixed with ccode-).
• path: The actual executable script name or path that the alias points to.
• desc: A description of what the script does (Claude uses this to understand its purpose).
• params: A string describing the expected command-line arguments.

{"alias": "ccode-md2gdoc", "path": "ccode-md2gdoc", "desc": "Convert local
markdown file to Google Doc using Google Drive API.", "params": "markdown_file
[--title TITLE] [--folder FOLDER_ID]"}
{"alias": "ccode-gdrive-list", "path": "ccode-gdrive-list", "desc": "List Google
Drive folders and their IDs (e.g., useful for finding a FOLDER_ID for
ccode-md2gdoc).", "params": "[--depth DEPTH] [--folder FOLDER_ID]"}

​

Setting Up Custom Script Aliases

• Located somewhere on your system.
• Made executable.
• Accessible via your system’s PATH, often through symbolic links in a dedicated bin directory.

​

Example Project Structure:

~/claude-code-tools/
├── bin/ # Directory for executable links (added to PATH)
│ ├── ccode-md2gdoc # Symlink to the actual script
│ └── ccode-gdrive-list # Another symlink
└── tools/
    └── gdrive/     # Directory for the actual script code
        ├── md_to_gdoc.py
        └── gdrive_list.py

​

Adding New Commands to the Project

1. Ensure Directories Exist:
   Copy

   mkdir -p ~/claude-code-tools/bin
   mkdir -p ~/claude-code-tools/tools/gdrive
   

2. Make the Script Executable:
   Copy

   chmod +x ~/claude-code-tools/tools/gdrive/md_to_gdoc.py
   

3. Create the Symbolic Link: This creates the ccode-md2gdoc command linked to the script.
   Copy

   ln -sfn ../tools/gdrive/md_to_gdoc.py ~/claude-code-tools/bin/ccode-md2gdoc
   

4. Ensure bin is in PATH: The agent checks if $HOME/claude-code-tools/bin is in the PATH environment variable. If not, it adds it to the appropriate shell configuration file (e.g., ~/.zshrc or ~/.bashrc):
   Copy

   # (Conceptual check: if $HOME/claude-code-tools/bin not in $PATH)
   
   echo 'export PATH="$HOME/claude-code-tools/bin:$PATH"' >> ~/.zshrc # Or
   ~/.bashrc
   
   # (Agent might then suggest sourcing the file or restarting the shell)
   

5. Install Dependencies: The agent identifies and installs necessary libraries for the script.
   Copy

   pip install google-api-python-client google-auth-httplib2 google-auth-oauthlib
   markdown argparse
   

​

Creating Custom Scripts (Example: Google Drive Tools)

​

The Scripts

1. gdrive_list.py: Connects to the Google Drive API to list folders and their IDs. Useful for finding where to save a file.
2. md_to_gdoc.py: Takes a local Markdown file, uploads it to Google Drive, and uses the API to convert it into a Google Doc, optionally placing it in a specific folder.

​

Key Libraries Required (for this example)

1. google-api-python-client, google-auth-httplib2, google-auth-oauthlib: For Google API interaction and authentication.
2. argparse: For handling command-line arguments.
3. markdown: For preprocessing markdown if needed.

​

Code Snippet

    # Build the Drive API client
    drive_service = build('drive', 'v3', credentials=creds)

    # Prepare file metadata
    file_metadata = {
        'name': title,
        'mimeType': 'application/vnd.google-apps.document' # Request conversion to Google Doc format
    }

    # If a folder ID is specified, add it as a parent
    if folder_id and folder_id != 'root':
        file_metadata['parents'] = [folder_id]

    # Prepare the media upload
    media = MediaFileUpload(markdown_file_path,
                            mimetype='text/markdown', # Specify the source format
                            resumable=True)

    # Create the file on Google Drive, triggering the conversion
    file = drive_service.files().create(
        body=file_metadata,
        media_body=media,
        fields='id, name, webViewLink' # Get fields needed for output message
    ).execute()

​

Handling Script-Specific Prerequisites (Example: Google API Setup)

​

Step 1: Create a Google Cloud Project

1. Go to the Google Cloud Console.
2. Create a new project (e.g., “Claude Drive Tools”).

​

Step 2: Enable Google Drive & Docs APIs

1. In your project, go to “APIs & Services” > “Library”.
2. Search for and enable both “Google Drive API” and “Google Docs API”.

​

Step 3: Create OAuth Credentials

1. Go to “APIs & Services” > “Credentials”.
2. Create an “OAuth client ID”.
3. Configure the consent screen (External user type, app name, emails). You can skip scopes and add your email as a test user.
4. Create the OAuth client ID again, this time selecting “Desktop app”.

​

Step 4: Download credentials.json

1. Download the JSON credentials file for the Desktop app client ID.
2. Save it as credentials.json in a location the scripts can access (e.g., ~/claude-code-tools/tools/python/).

​

Using Your Custom Scripts

​

Example Usage (Google Drive):

1. List folders:
   Copy

   ccode-gdrive-list --depth 2
   

2. Convert markdown: (Get FOLDER_ID from the list command)
   Copy

   ccode-md2gdoc report.md --title "Project Report Q1" --folder YOUR_FOLDER_ID
   

​

Example Usage (Claude Code):

Let’s create an initial draft of a blog post to describe how we can extend Claude Code to work on Google Drive documents by setting up these scripts, based on what I have in this repository. You can write the md file locally first, iterate on it, then upload to Google Drive in the appropriate destination.

​

Security Considerations

• Review Code: Always understand any script before configuring Claude Code to use it, especially if it accesses sensitive data or APIs.
• Protect Credentials: Secure API keys, tokens (token.json), and credential files (credentials.json). Use .gitignore.
• Scope Permissions: Be mindful of the permissions granted during authorization flows (like the Google OAuth flow).

​

Extending Further

• Manage Media: Create scripts to organize photos, convert video formats, or batch rename media files.
• Track Finances: Build tools to analyze bank statements, categorize expenses, or track budget progress.
• Health Monitoring: Develop scripts to log and visualize workout data, meal planning, or sleep patterns.
• Home Automation: Create integrations with smart home devices, schedule tasks, or monitor energy usage.
• Learning Tools: Build flashcard generators, language practice tools, or study schedule reminders.
• Social Media: Create tools to download content, schedule posts, or analyze engagement metrics.