honest-drive-mcp
A local Google Drive MCP server that gives an AI client full read/write access to your Drive — most notably the sharing and permission management the official connector lacks.
Search files —
list_fileswith Drive query syntax (e.g. name/mimeType filters), optional folder scoping, trashed-file toggle, up to 200 results.Inspect metadata —
get_filereturns full metadata for any file or folder by id.Read content —
read_filedownloads files: text as UTF-8, binaries as base64, and Google-native Docs/Sheets/Slides auto-exported to text or CSV.Upload files —
create_filefrom a text string or base64, with a chosen MIME type and optional parent folder.Create folders —
create_folder, at My Drive root or nested under a parent.Share files/folders —
share_filegrants an email address reader, commenter, writer, fileOrganizer, organizer, or owner access, with an optional notification email and custom message (notifications off by default;ownertransfers ownership).Audit access —
list_permissionsshows everyone with access and their role, returning permission ids.Revoke access —
remove_permissiondeletes a specific permission by id.
Runs entirely on your machine over MCP stdio using your own OAuth credentials — no cloud middleman.
Provides full read/write access to Google Drive, including searching and listing files with Drive query syntax, reading file metadata and content (with Google-native Docs/Sheets/Slides auto-exported to text/CSV), uploading files and creating folders, and — unlike the official connector — managing sharing permissions: granting access by email with roles (reader/commenter/writer/fileOrganizer/organizer/owner), listing existing permissions, and revoking them by permission id.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@honest-drive-mcp Create a folder named 'Project Alpha' and share it with alice@example.com as writer"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
honest-drive-mcp
Local Google Drive MCP server with full permission management — the piece missing from the official connector.
Companion project to honest-gmail-mcp and honest-calendar-mcp.
Why
The official Anthropic Drive connector is competent for read + create, but has one big gap: it cannot set or modify sharing permissions. If you build a workflow like "create a folder for my accountant and share it with her", you hit a dead end — you have to jump into the Drive UI to do the sharing part manually.
This MCP fixes that. Same trust model as the rest of the honest-* family: data flows only between your machine and Google.
Related MCP server: mcp-google-gdrive
Features
Eight tools exposed over MCP:
list_files— search with Drive query syntaxget_file— full metadataread_file— download content (text/JSON returned as UTF-8; binaries as base64; Google-native docs auto-exported to plain text / CSV)create_file— upload from text or base64create_folder— new folder, optionally inside a parentshare_file— grant access to an email (reader/commenter/writer/owner), notification optional, custom message supported ← the piece missing elsewherelist_permissions— see who has access and with what roleremove_permission— revoke a specific permission by id
Requirements
Python 3.10+
A Google account
One-time Google Cloud OAuth setup (~10 min; can reuse the client from honest-gmail-mcp — just enable the Drive API on the same project)
Setup
git clone https://github.com/bartosz-kuc/honest-drive-mcp.git
cd honest-drive-mcp
python3 -m venv venv
./venv/bin/pip install -r requirements.txtOn Windows use venv\Scripts\pip and venv\Scripts\python instead of the venv/bin/... paths shown throughout this README.
Google Cloud steps (same as honest-gmail-mcp):
https://console.cloud.google.com/ → create or select project
APIs & Services → Library → enable Google Drive API
APIs & Services → Credentials → OAuth client ID → Desktop app → download JSON → save as
credentials.jsonhere
Authorize (one-time OAuth):
./venv/bin/python -c "import server; server.get_service()"Browser opens → Allow → token saved to token.json (or DRIVE_TOKEN_PATH). If you skip this step, the server starts the same flow on the first tool call. Running server.py on its own does not start OAuth — it waits for an MCP client on stdin.
Register with Claude Code:
claude mcp add drive-personal /absolute/path/to/venv/bin/python /absolute/path/to/server.pyClaude Desktop claude_desktop_config.json:
{
"mcpServers": {
"drive-personal": {
"command": "/absolute/path/to/venv/bin/python",
"args": ["/absolute/path/to/server.py"]
}
}
}Configuration (optional)
By default credentials.json and token.json are read from (and the token written to) the directory containing server.py. Two env vars override this, e.g. for one instance per Google account, or when installed from PyPI (pip/uvx), where that directory is the package's install location:
Env var | Default | Purpose |
|
| OAuth client file |
|
| OAuth token file (written after browser consent on the first tool call; its directory must exist) |
Use absolute paths, e.g. in claude_desktop_config.json:
"env": {
"DRIVE_CREDENTIALS_PATH": "/absolute/path/to/credentials.json",
"DRIVE_TOKEN_PATH": "/absolute/path/to/token.json"
}Example usage
"Create a folder called 'Faktury dla księgowej' in My Drive and share it with elwira@example.pl as writer."
AI calls create_folder → gets folder_id → calls share_file(file_id, "elwira@example.pl", role="writer"). Done in one shot. No context-switch to the Drive UI.
"Who has access to file X?"
AI calls list_permissions(file_id) → returns all permissions with ids you can pass to remove_permission later.
Data flow
Your AI client
↕ MCP stdio
This server (Python, on your machine)
↕ HTTPS
Google Drive APINo cloud middle. Tokens stay on disk, .gitignored.
Security notes
OAuth scope requested:
drive(full read/write on all Drive files this account can access). Google does not offer a scope that includes permission management without also including read/write to files, which is why the scope is broad.send_notificationdefaults tofalse— AI will not spam recipients unless explicitly asked.role: "owner"transfers ownership — an irreversible action. The tool passestransferOwnership: trueautomatically when this role is requested; consider usingwriterunless you really mean to hand over the file.Revoke access anytime at https://myaccount.google.com/permissions.
credentials.jsonandtoken.jsonare.gitignored.
Author
Bartosz Kuć — Warsaw-based developer, JDG owner running skanfirmy.pl.
Site: https://skanfirmy.pl
GitHub: https://github.com/bartosz-kuc
Email: firma@bartosza.pl
Consulting
Available for consulting on Polish tax and business integrations (KSeF, GUS/NFZ/GIOŚ APIs, mBank data), MCP server design, and AI-assisted tooling for JDGs and small teams. See skanfirmy.pl/uslugi for productized packages (audit 3k PLN, setup 8-15k PLN, retainer 2-4k PLN/mo), or reach out via email.
License
MIT — see LICENSE.
Related
honest-gmail-mcp — local Gmail MCP
honest-calendar-mcp — local Google Calendar MCP
honest-nip-krs-mcp — Polish company registry MCP (biała lista + KRS)
Available Tools
8 toolscreate_fileB
Upload a file. Pass content as text_content (UTF-8 string) OR base64_content (for binary). If parent_id omitted, file lands in My Drive root.
Inputs: name (required), mime_type (required), parent_id, text_content, +1 more.
create_folderB
Create a folder. If parent_id omitted, folder lands in My Drive root.
Inputs: name (required), parent_id.
get_fileC
Get full metadata for a file/folder by id.
Inputs: file_id (required).
list_filesB
List/search files. Use Drive query syntax in query (e.g. "name contains 'invoice' and mimeType='application/pdf'"). Optional folder_id restricts to that folder's direct children.
Inputs: query, folder_id, max_results, include_trashed.
list_permissionsB
List all permissions on a file/folder (who has access and with what role).
Inputs: file_id (required).
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).
Inputs: file_id (required).
remove_permissionA
Revoke a specific permission by permission_id (get ids from list_permissions).
Inputs: file_id (required), permission_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Hosted Google Calendar MCP server for AI agents. No self-hosting or Google Cloud setup.
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables comprehensive Google Drive integration through MCP, supporting file management, content operations, permission handling, commenting, version control, and shared drive management through natural language interactions.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to list, read, create, and manage files in Google Drive. It features automatic conversion of Google Workspace formats into Markdown, CSV, and plain text for seamless integration with AI workflows.35 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to interact with Google Docs, Sheets, and Drive using the user's own Google account.-
- AlicenseNot gradedqualityDmaintenanceMCP server enabling AI agents to read, write, and manage Google Sheets, including sheet manipulation, row/column operations, dropdowns, checkboxes, and conditional formatting.11 npmMIT