Google Drive MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_TOKEN_PATH | Yes | Path where token.json is stored (OAuth 2.0 access token) | |
| GOOGLE_CREDENTIALS_PATH | Yes | Path to credentials.json (OAuth client ID for Google Drive API) |
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_filesB | Lista archivos y carpetas en Google Drive. Args: folder_id: ID de carpeta. Vacío = raíz (Mi unidad). page_size: Máximo de resultados (1-100). name_contains: Filtro opcional por nombre. |
| search_filesA | Busca archivos por nombre en todo Google Drive. Args: query: Texto a buscar en el nombre. page_size: Máximo de resultados (1-100). |
| get_file_infoA | Obtiene metadatos de un archivo o carpeta (nombre, tipo, enlace). Args: file_id: ID del archivo en Google Drive. |
| download_fileB | Descarga el contenido de un archivo de texto, o exporta Docs/Sheets/Slides. Args: file_id: ID del archivo a descargar. |
| upload_text_fileA | Sube un archivo de texto nuevo a Google Drive. Args: name: Nombre del archivo (ej. notas.txt). content: Contenido en texto. folder_id: Carpeta destino. Vacío = raíz. |
| update_text_fileA | Actualiza el contenido de un archivo de texto existente. Args: file_id: ID del archivo a actualizar. content: Nuevo contenido. |
| create_folderA | Crea una carpeta en Google Drive. Args: name: Nombre de la carpeta. parent_id: Carpeta padre. Vacío = raíz. |
| move_fileA | Mueve un archivo o carpeta a otra carpeta. Args: file_id: ID del archivo o carpeta a mover. folder_id: ID de la carpeta destino. |
| delete_fileA | Mueve un archivo o carpeta a la papelera de Google Drive. Args: file_id: ID del elemento a eliminar. |
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 9 tools
Most tools have clearly distinct purposes (upload, update, download, move, delete, create folder). The only potential overlap is between list_files and search_files, but list_files is folder-scoped with optional filters while search_files is a global name search, which is a meaningful distinction.
All tool names follow the same verb_noun pattern with consistent snake_case naming: list_files, search_files, get_file_info, download_file, upload_text_file, update_text_file, create_folder, move_file, delete_file. The convention is uniform across the entire set.
With 9 tools, the set is well-scoped for a Google Drive server. Each tool addresses a core operation (list, search, get info, download, upload, update, create folder, move, delete) without unnecessary redundancy, striking a good balance between coverage and simplicity.
The toolset covers the essential file and folder lifecycle: create, read, update (content), delete, move, and search. Minor gaps exist such as no rename or copy tool, and no permission/sharing operations, but these are not critical for basic Drive management and can be worked around.