Google/Drive/AI

• AI access to Google Drive, Docs, and Sheets

  • Every option for pointing Anthropic's Claude at Google Drive sorts along two axes, and a comparison that collapses either one is misleading. The first is read versus write: search and retrieval are mature and available nearly everywhere, while writing splits further into file-level writes (create, upload, move, trash, share) and content-level writes (change a paragraph in an existing Doc, set a range of cells in an existing Sheet). The second is which surface Claude is running on — claude.ai in a browser, Claude/Desktop, Claude/Cowork, Claude/Code in a terminal, or the Messages API. An option that exists on one surface frequently does not exist on another.
  • The short form of the whole landscape: nothing Anthropic ships can edit the contents of an existing Google Doc or Google Sheet. That capability exists only where something calls Google's Docs and Sheets APIs directly — a community MCP server, or Claude Code running code you supply.
  • Claims below are marked verified when they come from current first-party documentation, linked at the point of the claim; inferred when reasoned from adjacent documented behaviour, with the basis stated; and silent where the documentation does not address the question.

  • The write gap, stated precisely

    • Three tiers of write, and where each is available:

    • Kind of write	What it means	Available from Anthropic?
      File-level	Upload, create folder, move, share, trash	Yes — Google Workspace connector
      New-file authoring	Produce a .xlsx/.docx/.pptx/.pdf and save to Drive	Yes — file creation plus the connector
      Content-level, in place	Rewrite a section of a live Doc; set cells in a live Sheet	No — no Anthropic-shipped path

    • The gap matters because the last row is what most people mean by "modify a Google Sheet." A connector that uploads a new spreadsheet next to the old one is a different operation from one that edits the sheet a team is already working in.

  • Anthropic's first-party Google Workspace connector

    • Verified. The Google Workspace connectors help article documents the Drive connector's capabilities as four read items and four write items. Read: "Search and retrieve Google Docs from your Drive"; "Look up file metadata and preview directly without searching first"; "Read Sheets, Slides, PDFs, images, and MS Office files"; "View file permissions and list recent changes to your Drive." Write: "Upload any file type, with optional auto-convert to Google formats"; "Create folders"; "Share, move, and trash files in Google Drive"; "Save Claude-generated files directly to your Drive."
    • Verified — the list contains no in-place edit. Nothing in that set addresses the contents of an existing Google-native file. Every write is file-level or produces a new file. The connector directory entry is narrower still, naming only share, move and trash as writes, and stating that the connector "does not support adding comments, converting xlsx to sheets, or converting pptx to slides."
    • Verified — two Drive integrations are documented separately, with different scope. Alongside the connector, the Google Drive integration page documents a narrower document-picker for chats and projects: Google Docs only, up to 10MB, text extraction only, with Google Sheets and Google Slides both marked "Not currently supported," and images, comments and suggestions not extracted. Its stated availability is Pro, Max, Team and Enterprise. Which of the two a given surface exposes is not reconciled anywhere in the documentation.
    • Verified — auth is per-person OAuth, gated by the org on Team and Enterprise. "You must authenticate directly with your Google account before using these connectors." On Team and Enterprise, "an Owner or Primary Owner must enable these connectors at the organization level before individual users can authenticate," and "owners decide whether members can allow these actions to run without asking each time." Claude mirrors existing Google Workspace permissions rather than widening them.
    • Verified — connectors reach Claude/Code, but Drive must be authorized on claude.ai first. Per Claude Code's MCP documentation, servers added in claude.ai "are automatically available in Claude Code," and appear in /mcp marked as coming from claude.ai. That inheritance requires the active credential to be a claude.ai subscription login — it does not happen under ANTHROPIC_API_KEY, Amazon Bedrock, Google Cloud's Agent Platform, or a token from claude setup-token. Some Anthropic-hosted connectors, named as Microsoft 365, Gmail and Google Calendar, "don't support local OAuth from Claude Code because the upstream identity provider only accepts the redirect URL that claude.ai registered."
    • Inferred — Google Drive is very likely in that same category. Drive is not named in the list, but it is an Anthropic-hosted Google connector authorized through the same claude.ai OAuth redirect as Gmail and Google Calendar. The practical consequence either way is the same: connect Drive in claude.ai's connector settings, and it appears in Claude Code afterwards.

  • File creation, and what "save to Drive" actually produces

    • Verified. Create and edit files with Claude states that "code execution and file creation is available to all Claude users (Free, Pro, Max, Team, and Enterprise) on the web, Claude Desktop, and Claude Mobile." Claude produces .xlsx, .pptx, .docx and PDF files in a private code-execution environment, with a 30MB per-file ceiling. The announcement offers "Download your completed files or save directly to Google Drive."
    • This is authoring plus delivery, not editing. A spreadsheet built this way arrives in Drive as an uploaded .xlsx; the connector's optional auto-convert can turn it into a Google Sheet on upload. An existing Google Sheet is untouched by the operation.
    • Verified — Claude/Cowork is paid-only and has the same file abilities. Get started with Claude Cowork states "Claude Cowork is available on paid plans (Pro, Max, Team, Enterprise)," across Desktop on macOS and Windows for all paid plans, and web, mobile and the Chrome side panel with narrower per-plan rollout. It uses connectors with per-tool modes of "Always allow," "Needs approval," or "Blocked," and creates and edits files including "spreadsheets with working formulas."

  • The Office add-ins have no Google counterpart

    • Verified. Anthropic ships in-place spreadsheet editing — for Microsoft. Claude for Excel is "generally available to Pro, Max, Team, and Enterprise plans," updates cell values while keeping formula relationships intact, and performs native operations including sort, filter, pivot table edits, conditional formatting and data validation. Word, PowerPoint and Outlook add-ins exist alongside it.
    • Verified — the set stops at four apps. Anthropic's documentation index lists office agents for Excel, PowerPoint, Word and Outlook only. There is no Claude for Sheets, Docs, or Slides add-on in it.
    • Silent. Third-party writing refers to a "Claude for Sheets" add-on on the Google Workspace Marketplace. Anthropic's current documentation does not mention any Google Workspace add-on, so its status, maintenance, and provenance cannot be confirmed from first-party sources. The Marketplace also carries several unrelated community add-ons that expose a =CLAUDE() formula backed by an API key — those call a model from a cell; they are not an agent editing the sheet.

  • Google's own Drive MCP server

    • Verified. Google runs a hosted Drive MCP server at https://drivemcp.googleapis.com/mcp/v1, one of a family that also covers Gmail, Calendar, Chat and People — see supported products. All five are marked Developer Preview, and access "is part of the Google Workspace Developer Preview Program."
    • Verified — one write tool. The Drive MCP tools reference lists search_files, read_file_content, download_file_content, get_file_metadata, get_file_permissions, list_recent_files, copy_file, and create_file. Only create_file writes. There is nothing for editing Doc or Sheet contents.
    • Verified — no Docs or Sheets MCP server exists. Google's supported-products list has Drive, Gmail, Calendar, Chat and People. Docs, Sheets and Slides are absent.
    • Verified — Google documents Claude as a client, and names a plan requirement. Configure the Drive MCP server instructs you to create your own OAuth web-application credential with https://claude.ai/api/mcp/auth_callback as the redirect URI, request the drive.readonly and drive.file scopes, then add it under Settings → Connectors as a custom connector with your own client ID and secret. It states: "To use the Google Drive remote MCP server with Claude.ai or Claude Desktop, you must have the Claude Enterprise, Pro, Max, or Team plan."
    • Setup cost is real here: a Google Cloud project, an OAuth consent screen, a client credential you hold yourself, and preview-program enrollment. In exchange you get Google-operated infrastructure and Cloud IAM controls rather than a community server you host.

  • MCP servers for Google Workspace

    • Verified — the reference gdrive server is archived. The reference server repository lists Google Drive among servers that "are now archived and can be found at servers-archived." That archive repository is itself marked archived, with no push since May 2025. It should not be the basis of a new setup.
    • Verified — the leading community server is active and covers the write gap. taylorwilsdon/google_workspace_mcp is MIT-licensed, not archived, and its default branch was pushed on 2026-08-16 with roughly 3,000 stars. It advertises Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Tasks, Chat, Apps Script and Custom Search, multi-user OAuth 2.1, stateless deployment, and a CLI mode intended for use from Claude Code.
    • Inferred — this is the only ready-made route to in-place Doc and Sheet editing under Claude. It rests on the server's documented Docs and Sheets coverage combined with the confirmed absence of any equivalent from Anthropic or from Google's MCP servers. It is community software, not first-party: it holds Google credentials, and adopting it is a trust decision of the kind catalogued under MCP/Server/Attack/Root Problem.
    • Because it exposes both an HTTP transport and a local stdio mode, the same server can serve claude.ai as a custom connector, Claude Desktop as a local server, and Claude Code — the surfaces differ only in how it is registered.

  • Remote MCP from the Messages API

    • Verified. The MCP connector lets the Messages API call a remote MCP server without a separate client, under beta header mcp-client-2025-11-20. Constraints matter: only tool calls are supported, not prompts or resources; "the server must be publicly exposed through HTTP" and "local STDIO servers cannot be connected directly"; and the feature is not eligible for zero-data-retention. It is available on the Claude API, the Claude Platform on AWS, and Microsoft Foundry, and not on Amazon Bedrock or Google Cloud.
    • You handle OAuth yourself and pass an authorization_token per server. Per-tool enabled flags support an allowlist or a denylist — the documentation recommends denylisting write or destructive tools "when building read-only assistants, or when you want a human confirmation step before state changes."
    • This is the surface where a self-hosted Workspace MCP server and a programmatic agent meet, and where a Google-hosted preview endpoint would be reachable without going through claude.ai's connector UI.

  • Local MCP through Claude Desktop

    • Verified. Claude/Desktop/Extension packages a local MCP server as an .mcpb bundle with single-click install, bundled Node.js, and secrets held in the OS keychain. Connectors documentation puts desktop extensions on "all users on Claude Desktop," while web connectors reach "all users on Claude, Cowork, Claude Desktop, and Claude Mobile."
    • The surface constraint is the point: a locally-running server is reachable from Desktop and from Claude Code, and not from claude.ai in a browser or from the Messages API, both of which require a publicly-addressable URL.

  • Claude Code driving ordinary command-line tools

    • This is the least gated route and the most capable one, because the ceiling is whatever Google's APIs allow rather than whatever a connector chose to expose. It needs no plan feature beyond Claude Code itself, and the credentials stay on the machine.

    • rclone

      • Verified. rclone's Drive backend covers copy, sync, move, delete, mkdir and rmdir, shared drives, trash semantics (--drive-use-trash=false for permanent deletion, rclone cleanup to empty), and both interactive OAuth and service accounts with --drive-impersonate for domain-wide delegation.
      • Verified — no in-place editing of Google-native files. Native Docs and Sheets are handled by conversion on the way in and out, via --drive-export-formats (default docx,xlsx,pptx,svg) and --drive-import-formats. The documentation calls the conversion lossy and warns that export and import formats must match to avoid unintended overwrites. Google-native files also report a size of -1 in listings and 0 under the VFS layer.
      • Best fit: bulk file movement, structured uploads and downloads, backup and mirroring. Not a document editor.

    • GAM

      • Verified. GAM-team/GAM is Apache-2.0, actively pushed, and describes itself as "command line management for Google Workspace." It is an administrator's tool — users, groups, org units, licences, Drive permissions at scale.
      • Inferred — the wrong shape for personal document work. Its scope is domain administration, so it presumes Workspace admin authority and a domain to administer. Reasoned from the tool's stated purpose rather than from a documented restriction.

    • clasp and Apps Script

      • Verified. clasp is Google's Apache-2.0 CLI for Apps Script, installed with npm install @google/clasp -g on Node 20 or later. It creates, clones, pulls, pushes, deploys and versions script projects, keeping the code in a local directory that can live in git.
      • Inferred — this is the in-place write path that needs no third-party server. Apps Script's DocumentApp and SpreadsheetApp services run inside Google's own runtime with full authority over Doc and Sheet contents. Claude Code writes the script, clasp push uploads it, and the script performs the edit. The inference is about the composition, not about either piece: clasp's push and deploy behaviour is documented, and Apps Script's document services are Google's own long-standing API.
      • Cost: a script project per target, an authorization prompt on first run, and a deployment step. Well suited to an edit you will repeat; heavy for a one-off.

    • The Docs and Sheets REST APIs directly

      • Verified. documents.batchUpdate "applies one or more updates to the document," covering text insertion and deletion, text styling, tables, images, headers and footers, footnotes, comments and suggestions, named ranges and tabs, applied atomically as a batch. It requires one of the documents, drive, or drive.file scopes. The Sheets API offers the equivalent for cell values and spreadsheet structure.
      • This is the actual capability every other option is measured against. Claude Code can call it with curl, or with a short script in any language, using a credential you already hold. There is no plan gate, no preview program, and no connector — only the OAuth setup and the code.

  • What the plan tier changes

    • Verified. Connectors themselves are not the paywall. They "work across all Claude plans: free, Pro, Max, Team, and Enterprise," with one documented restriction: "Free users are limited to one custom connector."
    • Verified — the Drive integration's own documented floor is paid. The document-picker integration page states availability on Pro, Max, Team and Enterprise, and Google's Drive MCP setup guide independently requires "the Claude Enterprise, Pro, Max, or Team plan." The Workspace connectors help article says instead that the connectors are "available for all users on Claude and Claude Desktop." These do not agree, and no page reconciles them. Treat Pro as the safe floor for Drive work.
    • Verified — Enterprise adds gating and per-tool control, not new Drive capability. Two admin mechanisms are documented, and neither grants an ability a Pro user lacks. Owners enable Workspace connectors at the organization level before members can authenticate, and decide whether write actions run without per-action approval. Separately, per Claude Code's documentation, an organization can set per-tool controls that Claude Code "reads at startup and enforces locally": a tool set to ask prompts on every call even in acceptEdits, auto and bypassPermissions modes, with allow-rules unable to skip it and dontAsk mode denying instead; a tool set to blocked is filtered out before Claude sees it.
    • Verified — organization-wide connector authorization exists, and does not cover Drive. Enterprise-managed auth is in beta for Team and Enterprise, authorizing a connector once so members inherit access on first login, with Okta as the initial identity provider. Its supported connectors are Asana, Atlassian, Canva, Figma, Granola, Linear, Supabase, and Slack. Google Drive is not among them.
    • The practical reading: Enterprise is a control plane. It decides who may connect and which tools they may call. It does not add the ability to edit a Google Doc, because no plan has that ability.

  • Where the documentation is silent

    • Whether the Google Drive connector supports local OAuth from Claude Code. The exclusion list names Microsoft 365, Gmail and Google Calendar and does not say the list is exhaustive.
    • Which of the two documented Drive integrations — the richer connector or the narrower document-picker — applies on which surface, and whether one supersedes the other.
    • Any Anthropic-published Google Workspace add-on for Sheets or Docs. The office-agent documentation covers four Microsoft applications and does not mention Google.
    • Whether Google's Drive MCP server will gain content-level write tools, or whether Docs and Sheets MCP servers are planned. The preview documentation describes only what ships today.

  • Choosing

    • Need	Route	Surface	Plan floor
      Search and read Drive; pull a Doc into context	Google Workspace connector	Web, Desktop, mobile, Code	Pro (documentation disagrees)
      Add or remove files; move, share, trash; create folders	Google Workspace connector	Web, Desktop, mobile, Code	Pro (documentation disagrees)
      Author a new spreadsheet or document and land it in Drive	File creation plus connector save	Web, Desktop, mobile	Free
      Bulk file movement, mirroring, backup	rclone under Claude/Code	Code	none
      Edit an existing Doc or Sheet, occasionally	Docs/Sheets REST API from Claude/Code	Code	none
      Edit an existing Doc or Sheet, repeatedly	clasp and Apps Script from Claude/Code	Code	none
      Edit an existing Doc or Sheet conversationally	Community Workspace MCP server	All, per how it is hosted	Free (one custom connector)
      Programmatic agent against a remote server	Messages API MCP connector	API	API billing

    • The decision is usually settled by one question: does the work touch the contents of a file that already exists in Drive? If not, the first-party connector is sufficient and the setup cost is a single OAuth grant. If so, Anthropic and Google both stop short, and the choice narrows to trusting a community MCP server or having Claude Code call Google's APIs itself.