Google Drive MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_DRIVE_ROOT_FOLDER_ID | Yes | The ID of the root Google Drive folder to restrict access to. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| drive_list_filesA | List files in Google Drive. You can specify pageSize (max 100) and a search query. |
| drive_upload_text_fileB | Upload a text file to Google Drive |
| drive_create_folderB | Create a new folder in Google Drive |
| drive_download_fileA | Download a binary or regular file from Google Drive to the local file system (Note: Cannot download Google Docs/Sheets directly). |
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 4 tools
Each tool targets a distinct action: list files, upload text, create folder, download file. No overlapping purposes.
All tools follow the consistent 'drive_verb_noun' pattern (list_files, upload_text_file, create_folder, download_file).
With 4 tools covering basic Drive operations, the count is well-scoped for a minimal but functional server.
The surface lacks update and delete operations, and upload is restricted to text files, leaving significant gaps in Drive management.