drive-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRIVE_MCP_TOKEN | No | Path where the refresh token is stored | ./token.json |
| DRIVE_MCP_ACCOUNT | No | Expected address; auth.js warns if the token belongs to another account | |
| DRIVE_MCP_CREDENTIALS | No | Path to the OAuth client JSON | ./credentials.json |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_filesA | Search Drive by name, full text, type, folder and modification date. All constraints are ANDed. Returns metadata only; use read_file_content or download_file for contents. Trashed files are excluded unless includeTrashed is true. |
| list_recent_filesB | The most recently modified files that are not in the trash. Default 10. |
| list_folderA | List the direct children of a folder, folders first then by name. Use "root" for My Drive. |
| get_file_metadataC | Full metadata for one file, including its folder path and web link. |
| read_file_contentA | Return a file's content as text. Google Docs export as Markdown, Sheets as CSV (first sheet), Slides as plain text; text, Markdown, CSV, JSON and similar files are returned as-is. Binary files such as PDFs and images cannot be read this way; use download_file. |
| get_file_permissionsC | Who can access a file and with what role. |
| download_fileA | Save a file to a local absolute path. Google-native files are exported (Docs to docx, Sheets to xlsx, Slides to pptx, Drawings to png by default; pass format to change). Refuses to overwrite unless overwrite is true. |
| create_fileA | WRITES. Create a file from text. With convertTo, the text is imported as a Google Doc (from Markdown, HTML or plain text), Sheet (from CSV) or Slides. Without it a plain file of the given mimeType is created. Omit content to create an empty Google file. |
| create_folderC | WRITES. Create a folder. |
| upload_fileB | WRITES. Upload a local file. With convertTo the upload is imported as a Google-native file (e.g. a .docx or .md into a Google Doc, a .csv or .xlsx into a Sheet). |
| update_file_contentA | WRITES. Replace a file's content with new text. For a Google Doc the text is re-imported (Markdown, HTML or plain text), replacing the whole document; for a Sheet pass CSV. The file id, name, sharing and location are unchanged. |
| update_file_metadataA | WRITES. Rename, move, describe or star a file. Only the fields passed are changed. Moving replaces the current parent folder. |
| copy_fileB | WRITES. Copy a file, optionally with a new name and into another folder. Folders cannot be copied. |
| trash_fileA | WRITES. Move a file or folder to the trash. Reversible with untrash_file for 30 days; nothing is permanently deleted. |
| untrash_fileB | WRITES. Restore a file or folder from the trash. |
| share_fileB | WRITES and reaches other people. Grant access to a user, group, domain, or anyone with the link. No email is sent unless sendNotificationEmail is true. |
| unshare_fileA | WRITES. Remove one permission, by permission id (from get_file_permissions) or by the email address it was granted to. Pass emailAddress "anyone" to remove link sharing. |
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 17 tools
Each tool targets a distinct resource and action: separate tools for creating folders vs files, reading content vs downloading, updating content vs metadata, and sharing vs unsharing. Overlaps like list_folder/search_files/list_recent_files are clearly distinguished by scope and filters.
All tools use snake_case with a consistent verb_noun pattern (e.g., create_folder, update_file_content, share_file). Variations like list_recent_files and get_file_metadata are still predictable and readable.
17 tools is slightly above the typical 3-15 range but justified by Google Drive's breadth (files, folders, permissions, sharing, trash, content I/O). No tool appears redundant, though a few could theoretically be merged.
Core lifecycle is covered: create, read, update, copy, trash/untrash, share/unshare. Minor gaps include no permanent delete (trash is reversible) and no dedicated move operation (handled via update_file_metadata), but no critical dead ends.