Feature request: Google Docs MCP needs write/edit for existing docs (capability gap vs. competing agents)

Summary

The built-in Google Drive/Docs MCP supports create, read, copy, and search, but has no tool to edit an existing Google Doc. Once a doc exists, Claude can't update it in place.

Competitive gap

OpenAI Codex already does this today via its connected Google account — targeted documents.batchUpdate edits (replace text, formatting), with a revision ID for safe concurrent writes and a read-back to verify. Claude Code can't, and it's a visible, user-facing gap when teams compare the two.

Real-world impact

I'm a PM using Claude Code to author living documents (Feature Overviews for sales/CX). Every revision forces create_file → a brand-new doc each time: new URL, lost comments/history/sharing settings, and orphaned copies I can't even delete via the connector. In one session I had to recreate the same doc four times for minor edits.

Proposed addition

An edit_document / update_file_content tool backed by documents.batchUpdate. Even append / replace-section / replace-text would cover the majority of cases.

Note

Previously raised in #72576, which was auto-closed (not_planned / invalid, closed by a bot) — refiling as a considered feature request with a concrete competitive comparison and use case.

Environment

• Claude Code 2.1.204
• Built-in Google Drive/Docs MCP (claude.ai integration)
• Missing capability: write/edit content of existing Google Docs