taylorwilsdon/google_workspace_mcp

Release v1.1.8

Enhanced Gmail Thread Retrieval & SSL Reliability

This release request introduces significant improvements to the Gmail thread functionality and enhances the reliability of all Google Workspace API calls by implementing robust SSL retry mechanisms.

Key Features Added

Batch Thread Retrieval

• New Function: get_gmail_threads_content_batch() – retrieve multiple Gmail threads efficiently in a single call
• Enhanced Performance: optimized batch processing for handling multiple threads simultaneously
• Improved User Experience: clearer usage guidance and examples for batch operations

SSL Error Handling & Retry Logic

• Automatic Retry: exponential backoff for transient SSL errors on read‑only operations
• Smart Detection: distinguishes between read‑only and write operations for appropriate retry behavior
• Enhanced Reliability: all Google Workspace tools now handle SSL certificate and network issues gracefully
• Custom Exception: new TransientNetworkError exception for better error categorization

Infrastructure Improvements

• Docker Updates: added pyjwt>=2.10.1 dependency for enhanced JWT handling
• Enhanced Configuration: improved uv command structure in installation documentation
• Better Logging: added debug logging capabilities via mcp_server_debug.log

Documentation & Installation

• 1‑Click Installation: README now highlights seamless Claude Desktop integration
• Installation Video: added demonstration video showing the installation process
• Download Statistics: added PyPI download badge for transparency
• Improved Examples: richer code samples and usage instructions

Technical Implementation

Error Handling Enhancement

• Applied @handle_http_errors decorator with is_read_only=True to all read operations
• Implemented a 3‑retry mechanism with exponential backoff for SSL errors
• Preserved existing HTTP error handling while adding SSL resilience

Code Quality

• Consistent decorator ordering across all tool functions
• Improved error logging and user feedback
• Clearer separation of concerns between read and write operations

Thanks to @jihunkim0 for their first contributions!