MCP field guide / Google Drive
// mcp field guide · productivity
An honest one: today's Drive MCP servers mostly read. The archived reference server is read-only; Google's official one adds only create/copy. So a guard adds little right now — the strong case (sharing a confidential file, permanent delete) is latent, waiting on tools that aren't exposed yet. Here's the sourced picture.
GUARD FIT · TODAY'S SURFACE
LOWRead + create/copy only. Reads have no side effect; a created/copied file can be trashed. A guard here is a light safety net, not load-bearing.
GUARD FIT · IF DELETE/SHARE SHIP
STRONG (latent)Sharing a confidential doc publicly is irreversible once seen; permanent delete is unrecoverable. The moment those tools appear, a pre-commit human gate becomes essential.
Overall fit: WEAK → MODERATE today — and we'll say so plainly rather than pretend otherwise.
1. Reference server (archived) — @modelcontextprotocol/server-gdrive, by Anthropic (MIT). Read-only by design: OAuth scope drive.readonly, a single search tool, and file contents served through MCP resources (gdrive:/// URIs), auto-exporting Workspace files (Docs → Markdown, Sheets → CSV, Slides → text). It was archived on 2025-05-29 and is unmaintained.12
2. Google's official Drive MCP server — part of the Google Workspace MCP servers, a hosted endpoint (drivemcp.googleapis.com/mcp/v1), currently in Developer Preview. This is the effective successor, and it's read-mostly, not read-only: it adds create_file and copy_file but — as documented in Aug 2026 — exposes no update, delete, or permission-change tool.3
| Tool | Risk | What it does |
|---|---|---|
| search | read-only | Full-text search over Drive; returns file names + MIME types. Content read via gdrive:/// resources. |
| Tool | Risk | What it does |
|---|---|---|
| search_files | read-only | Search Drive for files. |
| list_recent_files | read-only | List recently modified files. |
| get_file_metadata | read-only | Fetch a file's metadata. |
| get_file_permissions | read-only | Read sharing/permissions — reads only, does not change them. |
| read_file_content | read-only | Read a file's contents. |
| download_file_content | read-only | Download raw file bytes. |
| create_file | mutating | Create a new file (additive; trashable). |
| copy_file | mutating | Duplicate an existing file (additive; trashable). |
What's not here (as of Aug 2026): no delete tool, no content-update/overwrite tool, and no share / change-permissions tool. Permissions can be read but not modified. Developer Preview means this surface can grow — so we mark the destructive case latent, not absent-forever.
Grounded Q&A / RAG. Search, then read the top hits to answer "what did we decide about pricing in the Q3 doc?" — pure read path.
Report assembly. Read source spreadsheets, synthesize, and create_file a summary doc back into Drive.
Exposure audit (read-only). Walk recent files and call get_file_permissions to flag docs shared more broadly than expected — reconnaissance, no changes.
Today: low. A read-only server has nothing to gate; the official server's create_file/copy_file are additive and trashable, so the stakes are clutter, not catastrophe. An approval step is a reasonable net, but not load-bearing — and we'd rather tell you that than oversell it.
The moment write/share/delete ship, it flips to strong. Two actions carry real, often-irreversible weight:
| Action | Reversible? |
|---|---|
| Ordinary delete → Trash | compensable — restorable ~30 days (platform default) |
| Permanent delete / empty trash | irreversible — gone |
| Share a confidential file publicly | irreversible once seen — revoking the link can't un-disclose |
The honest core: a shared secret can't be un-shared. Once a viewer has read or copied a file, revoking access afterward doesn't undo the disclosure — the textbook "irreversible once observed" case a human should decide before the share happens. That's compensation-is-not-undo, applied to access. The ~30-day Trash window means ordinary deletes are compensable; "delete forever" is not.
ChronoMCP passes reads through and is built to gate the sharing and delete calls on a human — with an honest flag for what can't be un-disclosed.
Read the quickstart → More MCP profilessearch tool, read-only scope): github.com/modelcontextprotocol/servers-archived/tree/main/src/gdrive@modelcontextprotocol/server-gdrive (MIT): npmjs.com/package/@modelcontextprotocol/server-gdriveProfiles describe third-party software from its public sources; ChronoMCP is not affiliated with these projects. The ~30-day Trash window is standard Google Drive platform behavior, not an MCP-server guarantee. Capabilities reflect sources current as of Aug 2026 and can change (the official server is in Developer Preview) — check the source links for the latest.