Drive MCP: create_file creates duplicates, no update_file available

Open 💬 0 comments Opened Jun 29, 2026 by prova2marcofattorini-spec

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

The Google Drive MCP server only provides create_file, which always creates
a new file with a new ID instead of updating an existing one.

There is no update_file or overwrite_file tool available.

This means every session creates a duplicate file on Drive, making it
impossible to maintain a stable file ID for an existing document.

Requested feature: an update_file tool that accepts an existing file ID
and overwrites its content in place, without creating a duplicate.

Proposed Solution

The Google Drive MCP server only has create_file, which always creates a
new file with a new ID. There is no update_file or overwrite_file tool.

This makes it impossible to maintain a stable file ID across sessions.
Needed: an update_file tool that accepts a file ID and overwrites content
in place, without creating a duplicate.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗