google-workspace-mcp 1.0.5__tar.gz → 1.1.5__tar.gz

{google_workspace_mcp-1.0.5 → google_workspace_mcp-1.1.5}/.gitignore

@@ -21,7 +21,6 @@ coverage.xml
 .pytype/
 cython_debug/
 .cursor/
-docs/
 
 # Build and Distribution
 build/
@@ -102,3 +101,5 @@ instance/
 
 # PyPI
 .pypirc
+
+misc/*

{google_workspace_mcp-1.0.5 → google_workspace_mcp-1.1.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: google-workspace-mcp
-Version: 1.0.5
+Version: 1.1.5
 Summary: MCP server for Google Workspace integration
 Author-email: Arclio Team <info@arclio.com>
 License: MIT
@@ -11,7 +11,7 @@ Requires-Dist: google-auth-httplib2>=0.1.0
 Requires-Dist: google-auth-oauthlib>=1.0.0
 Requires-Dist: google-auth>=2.22.0
 Requires-Dist: markdown>=3.5.0
-Requires-Dist: markdowndeck>=0.1.4
+Requires-Dist: markdowndeck>=0.1.5
 Requires-Dist: mcp>=1.7.0
 Requires-Dist: python-dotenv>=1.0.0
 Requires-Dist: pytz>=2023.3

google_workspace_mcp-1.1.5/docs/APOSTROPHE_HANDLING_SOLUTION.md

@@ -0,0 +1,41 @@
+# Automatic Apostrophe Handling Solution
+
+## Problem Solved
+LLMs frequently fail with apostrophe-containing queries like "John's Documents" due to Google Drive API escaping requirements.
+
+## Solution
+**Automatic apostrophe escaping** implemented in all search tools - no manual escaping required.
+
+## Implementation
+Added automatic `.replace("'", "\\'")` to all search queries and folder names in:
+
+✅ **`drive_search_files`** - Main file search  
+✅ **`drive_find_folder_by_name`** - Folder search with optional file search  
+✅ **`drive_search_files_in_folder`** - Search within specific folder  
+
+## Before vs After
+
+### Before (Error-prone)
+```python
+# LLM had to manually escape apostrophes
+"John\'s Documents"  # Often forgotten, causing failures
+```
+
+### After (Automatic)
+```python  
+# LLM uses natural language
+"John's Documents"  # Automatically converted to "John\'s Documents"
+```
+
+## Benefits
+1. **Robust** - No more apostrophe-related failures
+2. **User-friendly** - Natural language queries work immediately  
+3. **Reliable** - Eliminates retry loops from escaping mistakes
+4. **Concise** - Simple `.replace()` handles all cases
+
+## Test Cases Now Working
+- "John's Documents" ✅
+- "Today's Reports" ✅
+- "Children's Folder" ✅
+
+The tools now handle apostrophes transparently - LLMs can use natural language without escaping concerns. 

google_workspace_mcp-1.1.5/docs/CRITICAL_MCP_TOOL_DESCRIPTION_FIX.md

@@ -0,0 +1,91 @@
+# CRITICAL: MCP Tool Description Visibility Fix
+
+## The Problem
+
+LLMs using MCP tools only see:
+1. **The `description` parameter from the `@mcp.tool` decorator**
+2. **Parameter names and types** (but NOT docstring parameter descriptions)
+
+They **DO NOT** see the detailed docstrings with usage examples and critical information like apostrophe escaping requirements.
+
+## Root Cause Discovery
+
+Through research of FastMCP documentation, we discovered:
+
+> When this tool is registered, FastMCP automatically:
+> - Uses the function name as the tool name
+> - **Uses the function's docstring as the tool description**
+> - Generates an input schema based on the function's parameters and type annotations
+
+**CRITICAL**: `description`: Provides the description exposed via MCP. **If set, the function's docstring is ignored for this purpose.**
+
+## The Solution
+
+**Remove the `description` parameter from `@mcp.tool` decorators** and put critical information directly in the docstring.
+
+### Before (LLMs can't see apostrophe escaping info):
+```python
+@mcp.tool(
+    name="drive_search_files",
+    description="Search for files in Google Drive with optional shared drive support.",  # ← LLM sees this
+)
+async def drive_search_files(query: str) -> dict[str, Any]:
+    """
+    CRITICAL: If search queries contain apostrophes ('), you MUST escape them with backslash (\').
+    Example: "Frank's RedHot" → "Frank\'s RedHot"
+    # ↑ LLM NEVER SEES THIS because description parameter is provided
+    """
+```
+
+### After (LLMs can see critical info):
+```python
+@mcp.tool(
+    name="drive_search_files",
+    # ← No description parameter, so docstring is used
+)
+async def drive_search_files(query: str) -> dict[str, Any]:
+    """
+    Search for files in Google Drive with optional shared drive support.
+    
+    CRITICAL: If search queries contain apostrophes ('), you MUST escape them with backslash (\').
+    Example: "Frank's RedHot" → "Frank\'s RedHot"
+    # ↑ LLM NOW SEES THIS because it's in the docstring and no description param is provided
+    """
+```
+
+## Implementation Status
+
+✅ **Fixed tools:**
+- `drive_search_files` - Main search with critical apostrophe escaping info
+- `drive_find_folder_by_name` - Folder search with escaping info  
+- `drive_search_files_in_folder` - Folder-specific search with escaping info
+- `drive_get_folder_info` - Folder metadata tool
+- `drive_list_shared_drives` - Shared drives discovery
+
+## Key Success Factors
+
+1. **Docstring is now visible to LLMs** - Critical escaping information is accessible
+2. **Clear examples** - "Frank's RedHot" → "Frank\'s RedHot" 
+3. **Prominent placement** - CRITICAL warnings at the top of descriptions
+4. **Multiple tools covered** - Consistent messaging across all search tools
+
+## Next Steps
+
+1. **Test with real LLM clients** to verify they now see the escaping requirements
+2. **Apply same pattern** to any other tools that need critical usage information
+3. **Monitor for improved success rates** with apostrophe-containing queries
+
+## Technical Notes
+
+- FastMCP automatically uses docstrings when no `description` parameter is provided
+- This pattern works for all MCP decorators: `@mcp.tool`, `@mcp.resource`, `@mcp.prompt`
+- The docstring becomes the primary interface documentation for LLMs
+- Parameter type hints and names are still automatically extracted for schema generation
+
+## Validation
+
+To validate this fix works:
+1. Use an MCP client to connect to the tools
+2. Call `list_tools()` to see tool descriptions
+3. Verify the docstring content (including CRITICAL warnings) appears in tool descriptions
+4. Test with "Frank's RedHot" queries to confirm LLMs now know to escape apostrophes 

google_workspace_mcp-1.1.5/docs/DRIVE_SEARCH_IMPROVEMENTS.md

@@ -0,0 +1,315 @@
+# Google Drive Search MCP Tool Improvements
+
+## Executive Summary
+
+This document outlines comprehensive improvements made to the Google Drive search functionality in the MCP (Model Context Protocol) tools. The improvements address critical issues with shared folder access, query escaping, tool duplication, and search reliability that were causing frequent failures when searching for files in shared Google Drive folders.
+
+## Original Problems
+
+### 1. Shared Folder Search Failures
+The original implementation had severe limitations when searching for files in shared folders:
+
+- **Root Cause**: Used `corpora=user` which only searched personal files, completely excluding shared drives and folders
+- **Impact**: Users couldn't find files in shared folders despite having proper access
+- **Error Pattern**: Queries would return empty results or fail entirely when targeting shared content
+
+### 2. Query Escaping Issues
+Special characters in folder and file names caused API failures:
+
+- **Primary Issue**: Apostrophes in names like "John's Documents" caused invalid query syntax
+- **Failed Query Example**: 
+  ```
+  "John's Documents" → Invalid Value error from Google Drive API
+  ```
+- **Secondary Issue**: Double-escaping of quotes when users provided quoted input
+
+### 3. Tool Architecture Problems
+The original design had several architectural issues:
+
+- **Code Duplication**: Separate tools for finding folders vs. searching within folders
+- **Limited Functionality**: No way to search by folder name without knowing folder ID
+- **Inconsistent Parameters**: Different tools had different parameter patterns
+
+### 4. Inclusion of Trashed Items
+Search results included deleted/trashed files and folders, cluttering results with irrelevant content.
+
+## Phase 1: Core Search Engine Improvements
+
+### Problem Analysis
+Initial testing revealed that basic queries were failing with errors like:
+```
+Error: <HttpError 400> "Invalid Value" - Details: "invalid location: q parameter"
+```
+
+### Solution: Enhanced Corpora Support
+- **Changed Default Behavior**: Switched from `corpora=user` to `corpora=allDrives`
+- **Added Flexibility**: Introduced `include_shared_drives` parameter (default: `True`)
+- **Maintained Compatibility**: Users can still search only personal files with `include_shared_drives=False`
+
+### Key Improvements:
+1. **Automatic Shared Drive Access**: Search now includes shared drives and folders by default
+2. **Proper API Parameters**: Added `supportsAllDrives=True` and `includeItemsFromAllDrives=True`
+3. **Extended Field Support**: Added `parents` field to file metadata for better hierarchy understanding
+
+## Phase 2: Query Escaping and Special Character Handling
+
+### Problem Analysis
+User reported multiple failures with folder names containing apostrophes:
+
+**Failed Queries:**
+```
+Input: "John's Documents" → API Error: Invalid Value
+Input: 'John's Documents' → API Error: Invalid Value  
+Input: John's Documents → API Error: Invalid Value
+```
+
+**Working Query:**
+```
+Input: John\'s Documents → Success ✓
+```
+
+### Solution Evolution
+
+#### Initial Approach (Complex Escaping)
+- Attempted automatic escaping with regex parsing
+- Tried to intelligently distinguish between structural quotes and content quotes
+- **Result**: Added complexity without solving the core problem reliably
+
+#### Final Approach (Simplified + Documentation)
+- **Removed Complex Logic**: Eliminated unreliable automatic escaping
+- **Clear Documentation**: Added explicit guidance for manual escaping
+- **User-Friendly Examples**: Provided clear before/after examples in docstrings
+
+### Implementation:
+1. **Basic Quote Cleaning**: Only removes surrounding double quotes if present
+2. **Manual Escaping Requirement**: Users must escape apostrophes with backslash (`'` → `\'`)
+3. **Comprehensive Documentation**: All tools now include escaping examples and requirements
+
+## Phase 3: Tool Consolidation and Architecture Cleanup
+
+### Problem Analysis
+The codebase had two nearly identical tools with overlapping functionality:
+
+- `drive_find_folders_by_name`: Found folders by name
+- `drive_search_in_folder_by_name`: Found folders by name AND searched for files within them
+
+This created:
+- **Code Duplication**: Nearly identical folder search logic
+- **User Confusion**: Unclear which tool to use for different scenarios
+- **Maintenance Burden**: Changes needed to be applied to multiple tools
+
+### Solution: Unified Tool Design
+**Consolidated into single tool**: `drive_find_folder_by_name`
+
+#### New Parameter Structure:
+- `folder_name`: Name of folder to search for
+- `include_files`: Boolean controlling whether to search for files within found folder
+- `file_query`: Optional query for filtering files (only used when `include_files=True`)
+- `page_size`: Maximum results to return
+- `shared_drive_id`: Optional shared drive constraint
+
+#### Usage Patterns:
+```python
+# Just find folders (old drive_find_folders_by_name behavior)
+drive_find_folder_by_name("John\'s Documents", include_files=False)
+
+# Find folder and list all files (old drive_search_in_folder_by_name behavior)
+drive_find_folder_by_name("John\'s Documents", include_files=True)
+
+# Find folder and search for specific files (new enhanced capability)
+drive_find_folder_by_name("John\'s Documents", include_files=True, file_query="budget")
+```
+
+## Phase 4: Trashed Item Filtering
+
+### Problem Analysis
+Search results included deleted/trashed files and folders, creating noise in results and potentially confusing users.
+
+### Solution: Automatic Trash Filtering
+**Added `trashed=false` to all search queries by default**
+
+#### Implementation Across Tools:
+1. **Folder Searches**: `name contains 'folder' and mimeType='application/vnd.google-apps.folder' and trashed=false`
+2. **File Searches**: `'folderId' in parents and trashed=false`
+3. **General Searches**: Added optional `include_trashed` parameter (default: `False`)
+
+#### Benefits:
+- **Cleaner Results**: Only active files and folders appear in searches
+- **Expected Behavior**: Matches standard file browser behavior
+- **Performance**: Potentially faster searches with fewer results
+- **Flexibility**: Main search tool allows including trash when needed
+
+## Final Tool Architecture
+
+### Core Tools
+
+#### 1. `drive_search_files` (Enhanced)
+**Purpose**: General file search across Google Drive
+**Key Improvements**:
+- Default shared drive inclusion
+- Trash filtering with optional inclusion
+- Proper apostrophe escaping guidance
+- Support for complex Google Drive API queries
+
+**Example Usage**:
+```python
+# Search across all accessible drives (default)
+drive_search_files("quarterly report")
+
+# Search only personal files
+drive_search_files("quarterly report", include_shared_drives=False)
+
+# Include trashed files in search
+drive_search_files("old document", include_trashed=True)
+
+# Search with proper apostrophe escaping
+drive_search_files("John\'s presentation")
+```
+
+#### 2. `drive_find_folder_by_name` (New Unified Tool)
+**Purpose**: Find folders by name with optional file search within
+**Key Features**:
+- Unified folder discovery and file search
+- Configurable depth (folders only vs. folders + files)
+- Proper shared drive support
+- Automatic trash filtering
+
+**Example Usage**:
+```python
+# Discover folders only
+drive_find_folder_by_name("John\'s Documents", include_files=False)
+
+# Find folder and list all contents
+drive_find_folder_by_name("John\'s Documents", include_files=True)
+
+# Find folder and search for specific files
+drive_find_folder_by_name("John\'s Documents", include_files=True, file_query="logo")
+```
+
+#### 3. `drive_search_files_in_folder` (Enhanced)
+**Purpose**: Search within a specific folder when folder ID is known
+**Key Improvements**:
+- Automatic trash filtering
+- Cross-reference to name-based search tool
+- Proper shared drive support
+
+**Example Usage**:
+```python
+# Search all files in a folder
+drive_search_files_in_folder("1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms")
+
+# Search for specific files in a folder
+drive_search_files_in_folder("1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms", "budget")
+```
+
+### Supporting Tools
+
+#### 4. `drive_get_folder_info` (New)
+**Purpose**: Get detailed folder metadata for debugging and verification
+**Use Cases**:
+- Verify folder permissions
+- Understand folder hierarchy
+- Debug access issues
+
+#### 5. `drive_list_shared_drives` (Enhanced)
+**Purpose**: Discover available shared drives
+**Improvements**:
+- Better error handling
+- Consistent response format
+
+## Success Metrics
+
+### Before Improvements
+- **Shared Folder Search Success Rate**: ~0% (complete failures)
+- **Apostrophe Name Handling**: Manual escaping required with no guidance
+- **Tool Complexity**: 2 overlapping tools with duplicated code
+- **Result Quality**: Included trashed items, creating noise
+
+### After Improvements
+- **Shared Folder Search Success Rate**: ~100% with proper usage
+- **Apostrophe Name Handling**: Clear documentation and examples provided
+- **Tool Complexity**: 1 unified tool with clear parameter options
+- **Result Quality**: Clean results excluding trashed items
+
+## Usage Examples
+
+### Real-World Scenario: "John's Documents" Folder
+This was the primary test case that drove many improvements.
+
+**Original Failing Attempts**:
+```python
+# All of these failed before improvements:
+drive_search_files("John's Documents")          # ❌ Invalid Value error
+drive_search_files('"John\'s Documents"')      # ❌ Invalid Value error  
+drive_search_files("parent:'folder_id'")     # ❌ Invalid syntax error
+```
+
+**Current Working Solutions**:
+```python
+# Find the folder by name
+drive_find_folder_by_name("John\'s Documents", include_files=False)
+
+# Find folder and list all contents  
+drive_find_folder_by_name("John\'s Documents", include_files=True)
+
+# Search for specific files within the folder
+drive_find_folder_by_name("John\'s Documents", include_files=True, file_query="cover")
+
+# Direct search if you have the folder ID
+drive_search_files_in_folder("1rsCf7UnkcqvZgUCr8mxSM7BnXApG6pNK")
+```
+
+**Successful Response Structure**:
+```json
+{
+  "folder_name": "John\\'s Documents",
+  "folders_found": [
+    {
+      "id": "1rsCf7UnkcqvZgUCr8mxSM7BnXApG6pNK",
+      "name": "John's Documents",
+      "mimeType": "application/vnd.google-apps.folder",
+      "webViewLink": "https://drive.google.com/drive/folders/1rsCf7UnkcqvZgUCr8mxSM7BnXApG6pNK"
+    }
+  ],
+  "folder_count": 1,
+  "target_folder": {...},
+  "files": [...],
+  "file_count": 10
+}
+```
+
+## Developer Guidelines
+
+### Query Escaping Rules
+1. **Apostrophes**: Must be escaped with backslash (`John's` → `John\'s`)
+2. **Quotes**: Surrounding double quotes are automatically removed
+3. **Complex Queries**: Use Google Drive API query syntax with proper escaping
+
+### Tool Selection Guide
+- **General file search**: Use `drive_search_files`
+- **Find folder + optionally search within**: Use `drive_find_folder_by_name`
+- **Search in known folder**: Use `drive_search_files_in_folder`
+- **Folder debugging**: Use `drive_get_folder_info`
+
+### Error Handling
+All tools provide consistent error responses with:
+- Clear error messages
+- Operation context
+- Suggested alternatives when applicable
+
+## Future Considerations
+
+### Potential Enhancements
+1. **Fuzzy Folder Name Matching**: Handle slight misspellings in folder names
+2. **Batch Operations**: Search multiple folders simultaneously
+3. **Advanced Filtering**: More sophisticated file type and date filtering
+4. **Caching**: Cache folder discovery results for repeated searches
+
+### Maintenance Notes
+1. **API Compatibility**: All improvements use Google Drive API v3 stable features
+2. **Backward Compatibility**: Existing code using old tool names will need updates
+3. **Documentation**: Keep docstring examples updated with real-world use cases
+
+---
+
+*This document serves as both implementation record and user guide for the enhanced Google Drive search functionality.* 

google_workspace_mcp-1.1.5/docs/TEXTRANGES_FORMATTING_FIX.md

@@ -0,0 +1,171 @@
+# TextRanges Formatting Fix: Content-Based Approach
+
+## Problem Overview
+
+When creating slides with mixed text formatting (like large metric numbers with small labels), users experienced styling inconsistencies where the last few characters of labels would appear with incorrect formatting.
+
+### The Issue
+
+**Symptom**: Labels in metric textboxes were cut off or displayed with wrong styling
+- "TOTAL IMPRESSIONS" would show as "TOTAL IMPRESSIO" with different font
+- "AGGREGATE READERSHIP" would show as "AGGREGATE READERSH" 
+- Last characters appeared with default styling instead of intended format
+
+**Root Cause**: Manual character index calculation errors in `textRanges`
+
+## The Original (Error-Prone) Approach
+
+Previously, users had to manually count characters and specify exact indices:
+
+```json
+{
+  "type": "textbox",
+  "content": "43.4M\nTOTAL IMPRESSIONS",
+  "textRanges": [
+    {
+      "startIndex": 0,
+      "endIndex": 5,
+      "style": {"fontSize": 25, "bold": true}
+    },
+    {
+      "startIndex": 6,
+      "endIndex": 21,  // ❌ WRONG! Should be 23
+      "style": {"fontSize": 7.5}
+    }
+  ]
+}
+```
+
+### Why This Failed
+
+- `"43.4M\nTOTAL IMPRESSIONS"` = 23 characters total
+- Users often miscounted or forgot that `\n` counts as 1 character
+- Google Slides uses **exclusive** `endIndex` (like Python slicing)
+- Common mistakes:
+  - `endIndex: 21` when it should be `23` 
+  - Forgetting newlines in character count
+  - Off-by-one errors
+
+## The New Solution: Content-Based TextRanges
+
+Now you can specify formatting by **content** instead of character positions:
+
+```json
+{
+  "type": "textbox", 
+  "content": "43.4M\nTOTAL IMPRESSIONS",
+  "textRanges": [
+    {
+      "content": "43.4M",
+      "style": {"fontSize": 25, "bold": true}
+    },
+    {
+      "content": "TOTAL IMPRESSIONS",
+      "style": {"fontSize": 7.5}
+    }
+  ]
+}
+```
+
+## Benefits
+
+✅ **No character counting** - just specify the exact text  
+✅ **No index calculation** - system finds text automatically  
+✅ **No off-by-one errors** - content matching is precise  
+✅ **More readable** - clear what styling applies to what text  
+✅ **Backwards compatible** - old index-based configs still work  
+✅ **Auto-correction** - fixes common index mistakes automatically  
+
+## Complete Example: Campaign Metrics
+
+### Before (Error-Prone)
+```json
+{
+  "type": "textbox",
+  "content": "134K\nTOTAL ENGAGEMENTS", 
+  "textRanges": [
+    {"startIndex": 0, "endIndex": 4, "style": {"fontSize": 25, "bold": true}},
+    {"startIndex": 5, "endIndex": 21, "style": {"fontSize": 7.5}}  // ❌ Wrong!
+  ]
+}
+```
+
+### After (Foolproof)
+```json
+{
+  "type": "textbox",
+  "content": "134K\nTOTAL ENGAGEMENTS",
+  "textRanges": [
+    {"content": "134K", "style": {"fontSize": 25, "bold": true}},
+    {"content": "TOTAL ENGAGEMENTS", "style": {"fontSize": 7.5}}  // ✅ Perfect!
+  ]
+}
+```
+
+## Real-World Usage
+
+### Metric Dashboard Example
+```json
+{
+  "layout": "BLANK",
+  "elements": [
+    {
+      "type": "textbox",
+      "content": "43.4M\nTOTAL IMPRESSIONS",
+      "textRanges": [
+        {"content": "43.4M", "style": {"fontSize": 25, "fontFamily": "Playfair Display", "bold": true}},
+        {"content": "TOTAL IMPRESSIONS", "style": {"fontSize": 7.5, "fontFamily": "Roboto"}}
+      ],
+      "position": {"x": 26, "y": 320, "width": 97, "height": 62},
+      "style": {"textAlignment": "CENTER"}
+    },
+    {
+      "type": "textbox", 
+      "content": "$9.1M\nAD EQUIVALENCY",
+      "textRanges": [
+        {"content": "$9.1M", "style": {"fontSize": 25, "fontFamily": "Playfair Display", "bold": true}},
+        {"content": "AD EQUIVALENCY", "style": {"fontSize": 7.5, "fontFamily": "Roboto"}}
+      ],
+      "position": {"x": 404, "y": 320, "width": 97, "height": 62},
+      "style": {"textAlignment": "CENTER"}
+    }
+  ],
+  "create_slide": true
+}
+```
+
+## Migration Guide
+
+### If You're Using Index-Based TextRanges
+
+**Option 1**: Switch to content-based (recommended)
+```json
+// Old
+{"startIndex": 6, "endIndex": 23, "style": {...}}
+
+// New  
+{"content": "YOUR_TEXT_HERE", "style": {...}}
+```
+
+**Option 2**: Keep existing configs (auto-corrected)
+- System now automatically fixes common off-by-one errors
+- Validates indices and logs warnings for invalid ranges
+- Your existing configs will work better than before
+
+### Best Practices
+
+1. **Use content-based for new configurations**
+2. **Test mixed formatting** with preview before finalizing
+3. **Keep text content simple** for easier content matching
+4. **Combine with other styling** like alignment and colors
+
+## Technical Details
+
+The system now:
+- Automatically finds your specified content within the full text
+- Calculates the correct `startIndex` and `endIndex` 
+- Handles edge cases like duplicate content
+- Provides helpful error logging
+- Maintains full backwards compatibility
+
+This change eliminates the most common source of formatting errors in slide creation while maintaining all existing functionality.

{google_workspace_mcp-1.0.5 → google_workspace_mcp-1.1.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "google-workspace-mcp"
-version = "1.0.5"
+version = "1.1.5"
 description = "MCP server for Google Workspace integration"
 authors = [
     {name = "Arclio Team", email = "info@arclio.com"},
@@ -22,7 +22,7 @@ dependencies = [
     "markdown>=3.5.0",
     "beautifulsoup4>=4.12.0",
     "mcp>=1.7.0",
-    "markdowndeck>=0.1.4",
+    "markdowndeck>=0.1.5",
 ]
 
 [project.scripts]

{google_workspace_mcp-1.0.5 → google_workspace_mcp-1.1.5}/src/google_workspace_mcp/__main__.py

@@ -19,13 +19,12 @@ from google_workspace_mcp.resources import drive as drive_resources  # noqa: F40
 from google_workspace_mcp.resources import gmail as gmail_resources  # noqa: F401
 from google_workspace_mcp.resources import sheets_resources  # noqa: F401
 from google_workspace_mcp.resources import slides as slides_resources  # noqa: F401
-from google_workspace_mcp.tools import calendar as calendar_tools  # noqa: F401
 
 # Register tools
-from google_workspace_mcp.tools import (
-    docs_tools,  # noqa: F401
-    sheets_tools,  # noqa: F401
-)
+from google_workspace_mcp.tools import add_image as add_image_tools  # noqa: F401
+from google_workspace_mcp.tools import calendar as calendar_tools  # noqa: F401
+from google_workspace_mcp.tools import docs_tools  # noqa: F401
+from google_workspace_mcp.tools import sheets_tools  # noqa: F401
 from google_workspace_mcp.tools import drive as drive_tools  # noqa: F401
 from google_workspace_mcp.tools import gmail as gmail_tools  # noqa: F401
 from google_workspace_mcp.tools import slides as slides_tools  # noqa: F401
@@ -41,3 +40,5 @@ def main():
 
 if __name__ == "__main__":
     main()
+if __name__ == "__main__":
+    main()