honest-drive-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_filesB | List/search files. Use Drive query syntax in |
| get_fileC | Get full metadata for a file/folder by id. |
| read_fileA | Download file content. For text files returns UTF-8 text; for binary files returns base64. Google-native docs are exported (Docs→text, Sheets→CSV, Slides→text). |
| create_fileB | Upload a file. Pass content as |
| create_folderB | Create a folder. If parent_id omitted, folder lands in My Drive root. |
| share_fileB | Share a file or folder with someone. Missing in the official connector. Roles: reader (view), commenter, writer (edit), fileOrganizer, organizer, owner. send_notification=false by default (no email sent to recipient). |
| list_permissionsB | List all permissions on a file/folder (who has access and with what role). |
| remove_permissionA | Revoke a specific permission by permission_id (get ids from list_permissions). |
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 8 tools
Each tool maps to a distinct action-resource pair, but read_file (content) and get_file (metadata) are close enough that an agent must read descriptions carefully. The permission trio (share_file, list_permissions, remove_permission) is cleanly separated.
Consistent snake_case verb_noun pattern throughout: read_file, create_file, create_folder, list_files, get_file, share_file, list_permissions, remove_permission. No mixed conventions or vague verbs.
Eight tools is well-scoped for a Drive file-management surface, with each tool earning its place across read, create, list, and permission operations.
Covers read/create/list/get plus permission management, but there is no delete_file, no update_file (rename/move/modify), and no move operation. These are common Drive workflows whose absence will force agents into dead ends.