Google Drive MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Nivel de logging (debug, info, warn, error) | info |
| MCP_API_KEY | No | API key para autenticación de requests MCP (opcional) | |
| DRIVES_CONFIG_PATH | No | Ruta personalizada del archivo de configuración | ./drives-config.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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_drivesB | List all configured Google Drive accounts |
| add_driveC | Add a new Google Drive account to the configuration |
| remove_driveC | Remove a Google Drive account from the configuration |
| list_filesC | List files from Google Drive with optional filters (driveId, folderId, modifiedAfter/Before, mimeType) |
| get_file_contentC | Get content from a Google Drive file (Docs, Sheets, TXT, MD) |
| search_filesC | Search files by name in a Google Drive |
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 6 tools
Each tool has a clearly distinct purpose with no ambiguity: account management (add_drive, list_drives, remove_drive), file listing (list_files), file searching (search_files), and content retrieval (get_file_content). The descriptions reinforce these distinct roles, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun naming pattern with snake_case throughout (e.g., add_drive, get_file_content, list_drives). This predictability enhances usability and reduces cognitive load when scanning the toolset.
With 6 tools, this server is well-scoped for Google Drive operations, covering account configuration, file listing, searching, and content access. Each tool earns its place without bloat, aligning with typical MCP server sizes of 3-15 tools.
The toolset covers basic read and configuration operations well but has notable gaps in file lifecycle management. There are no tools for creating, updating, deleting, or moving files, which limits agents from performing full CRUD workflows in Google Drive.