A
licenseA
qualityD
maintenanceEnables AI assistants to interact with Google Drive, supporting file operations like list, search, read, create, update, delete, share, and manage permissions.
7
2,911 npm
4
MIT
A1 Google Drive MCP
by A1-x-Tech
Related Servers
Alternatives to A1 Google Drive MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables AI assistants to interact with Google Drive, including reading, searching, listing folders, and uploading files.71-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to make real in-place edits to Google Drive files—preserving file IDs, revision history, comments, and sharing—while also supporting appends, targeted find-and-replace, reads, searches, and file creation.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to securely access and manage Google Drive files and Google Sheets within a specified folder scope, with support for reading various file types including PDFs and Excel.710 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to automate Google Drive tasks such as provisioning workspaces, reusing templates, inspecting folder structures, updating reports, and sharing files through user-controlled OAuth.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI models to search, list, and read files from Google Drive with automatic format conversion for Google Workspace documents.3,926 npmMIT
TDQS
A4.4/5.0
Scored across 21 tools
Disambiguation5/5
Each tool targets a clearly distinct action or resource: the auth flow is split into unambiguous steps (start_login vs finish_login vs auth_status), file operations are separated by purpose (upload_file vs copy_file, download_file vs export_file, trash_file vs delete_file_forever), and permission/comment management have dedicated scopes. No two tools appear to do the same thing.
Naming Consistency4/5
The vast majority of names follow a clear snake_case verb_noun pattern (get_file, search_files, create_folder, move_file, etc.), but a few deviate—auth_status and setup_instructions are noun-first, logout is a bare verb, and raw_request uses an adjective_noun form. These exceptions are minor and still readable, so consistency is high overall.
Tool Count4/5
21 tools is on the heavy side for a single server, but each tool covers a distinct, non-overlapping operation in a broad Google Drive domain. The auth flow uses six tools for a multi-step login, which is justified by step separation rather than redundancy.
Completeness5/5
The surface provides full lifecycle coverage: authentication, file CRUD/search, folder operations, upload/download/export, permissions, comments, shared drives, and both reversible and permanent deletion. raw_request explicitly covers remaining gaps like revisions, changes, shortcut creation, and resumable uploads, so there are no obvious dead ends.
Maintenance
ActivityMaintained
ResponsivenessNo issues