Claude.ai Google Drive/Gmail/Calendar MCP integrations lack write operations (move, rename, delete/trash)

Summary

The first-party Claude.ai connectors for Google Drive, Gmail and Google Calendar expose only read + create tools. Any operation that modifies existing items — moving a file to another folder, renaming, deleting/trashing, updating metadata — is missing. This makes the integrations effectively read-only and blocks the most common "organize my stuff" use cases that users naturally expect when Claude gets Drive access.

Discrepancy with the connector's own description

The official connector description on claude.ai states:

"Useful for finding project notes, extracting data from spreadsheets, preparing meeting materials, or organizing files scattered across your Drive."

However, the exposed tool surface cannot perform any organizing action. The full tool list shown in the permissions UI is:

Read-only (6): download_file_content, get_file_metadata, get_file_permissions, list_recent_files, read_file_content, search_files

Write/delete (1): create_file

There is no move, rename, trash, delete, update_permissions, or copy. "Organizing" implies moving things between folders and deleting junk — neither is possible today.

Missing operations

• update_file / move_file — change parents (i.e. move between folders)
• rename_file
• trash_file / delete_file
• copy_file
• update_permissions (share/unshare)
• empty_trash

Gmail and Calendar integrations have the same shape: read + create, no edit/move/delete on existing messages, threads, labels, or events.

Real-world scenario that breaks today

A user asked Claude to "clean up my Google Drive": find obvious junk (empty 1KB spreadsheets, abandoned drafts), gather all password/auth notes into a single "Credentials" folder, and gather all finance-related sheets into a "Finances" folder. Claude could enumerate files, read their contents to verify what's really junk, and even create_file the new folders — but could not move a single existing file into those folders, could not delete empty junk, could not rename a mis-named doc. The task fell back to "here are 20 links, please drag them yourself in the web UI," which defeats the point of having the integration.

Why this matters

• The Drive/Gmail/Calendar connectors are auto-loaded for Max users and consume a large chunk of tool-description tokens — users pay the context cost but get a half-functional surface area.
• The underlying Google APIs (files.update with addParents/removeParents, files.delete, files.trash, Gmail messages.modify/trash, Calendar events.patch/delete) fully support these operations. This is purely an MCP-surface gap on Anthropic's side, not a Google API limitation.

Request

Add the standard CRUD surface to each first-party connector, at minimum:

• Drive: move_file, rename_file, trash_file, delete_file, copy_file
• Gmail: modify_message (labels), trash_message, delete_message, send_draft
• Calendar: update_event, delete_event

Happy to test a preview if/when available.