google-drive-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_shared_drivesB | List all shared drives the user has access to. |
| get_shared_driveA | Get metadata for a specific shared drive including name and creation time. |
| list_filesB | List files in Google Drive, optionally within a specific folder. |
| search_filesC | Search for files in Google Drive using query syntax. |
| search_file_contentA | Search for files by their text content. Finds files containing the specified text. |
| read_fileB | Read the content of a file from Google Drive. Google Docs/Sheets/Slides are automatically exported to text/CSV format. |
| upload_fileA | Upload a new file to Google Drive with the given text content. |
| update_file_content | Update the content of an existing file in Google Drive. |
| append_to_fileA | Append text content to the end of an existing text file. Does not work with Google Docs/Sheets/Slides. |
| export_file | Export a Google Docs/Sheets/Slides/Drawings file to a specific format like PDF, DOCX, XLSX, etc. |
| create_google_docC | Create a new blank Google Docs, Sheets, or Slides file. |
| upload_binary_fileC | Upload a binary file to Google Drive using base64-encoded content. |
| create_folderB | Create a new folder in Google Drive. |
| get_file_infoB | Get detailed metadata for a file including size, dates, owners, and sharing status. |
| update_metadataB | Update a file's metadata (name and/or description). |
| move_fileB | Move a file to a different folder in Google Drive. |
| copy_file | Create a copy of a file in Google Drive. |
| list_revisionsC | List the revision history (versions) of a file. Shows who modified it and when. |
| get_revisionA | Download the content of a specific file revision (version). |
| share_fileC | Share a file with another user by email address. |
| list_permissionsA | List all permissions (who has access) for a file in Google Drive. |
| remove_permissionB | Remove a specific permission from a file, revoking access for that user. |
| create_share_linkB | Create a shareable link so anyone with the link can access the file. |
| update_permissionB | Update an existing permission's role on a file. |
| trash_fileA | Move a file to trash. The file can be restored later with restore_file. |
| restore_fileA | Restore a file from trash back to its original location. |
| list_trashB | List files currently in the trash. |
| list_recentA | List recently accessed files, sorted by last viewed time. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
Each tool has a clear and distinct purpose, covering various aspects of Google Drive management without overlap. For example, list_files, search_files, list_recent, and list_trash each target different subsets of files.
All tool names follow a consistent verb_noun pattern in snake_case, such as list_shared_drives, create_folder, or update_metadata. This makes the API predictable and easy to navigate.
With 25 tools, the server covers a broad range of Google Drive operations. While slightly above the typical 3-15 tool range, the count is justified given the domain's complexity and is not excessive.
The tool set provides comprehensive CRUD operations, sharing, revision history, and search. Minor gaps include the lack of a permanent delete tool or a function to restore a file to a previous revision, but the core workflows are well-covered.