Refactor Google Drive Server: Transition to Tool-Based Architecture with Enhanced File Handling

[MMoshtaghi]

Description

This PR transitions the server from a resource-based architecture to a tool-based architecture. It introduces new tools for interacting with Google Drive, improves error handling, and adds support for file downloads to a configurable directory.

Server Details

• Server: Google Drive (example-servers/gdrive)
• Changes to: Tools and resource handling logic

Motivation and Context

The changes simplify the server's architecture by focusing on tools rather than resources. This makes the server more modular, user-friendly, and aligned with its intended use cases. Additionally, the introduction of a configurable download directory enhances flexibility.

How Has This Been Tested?

The changes have been tested with an LLM client to ensure the following scenarios work as expected:

• Listing files with pagination
• Searching for files using a query
• Downloading files to the specified directory
• Exporting Google Docs/Sheets/Slides to appropriate formats

Breaking Changes

Yes, this change removes the ListResourcesRequestSchema and ReadResourceRequestSchema handlers. Users will need to update their MCP client configurations to use the new tools (gdrive_list_all, gdrive_search, and gdrive_read_file).

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follow MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context

• Added the dotenv package to manage environment variables.
• Introduced the GDRIVE_DOWNLOAD_DIRECTORY environment variable for specifying the download directory.

[moonray]

Confirmed working

[olaservo]

Thanks for the PR - should we make this backwards compatible? I think we could still introduce these enhancements without breaking changes?

[MMoshtaghi]

@olaservo

Yes, we could, and I made it backward compatible now.

• Now we have 2 unnecessary resources (ListResourcesRequestSchema, ReadResourceRequestSchema) to which the model has no access and will never use.
• I also changed the name of gdrive_search tool back to search