@enterpret/google-drive-mcp

Enterpret's stdio-only Google Drive MCP for app-authorized content in one marked Enterpret folder and resources directly authorized through the host's Google Picker flow. V1 covers My Drive and items shared directly with the connected user when Google exposes them to the active drive.file bearer after Picker selection or app creation. Shared Drive product support is outside the validated and supported V1 scope. This package is a constrained additive build of piotr-agier/google-drive-mcp and uses only the OAuth scope https://www.googleapis.com/auth/drive.file.

Source and issue tracking live in aavaz-ai/google-drive-mcp. The original upstream documentation is preserved separately so npm users see the narrower Enterpret contract on this page.

Runtime contract

The host must run Node.js 22 or later and supply one short-lived access token:

GOOGLE_DRIVE_OAUTH_BEARER='access-token' npx @enterpret/google-drive-mcp

The executable accepts only stdio startup, --help, and --version. It does not implement the Picker UI itself, browser OAuth, token refresh or persistence, HTTP/team/service-account modes, multiple accounts, Calendar, raw Drive queries, binary/local/base64 transfer, public/domain sharing, ownership transfer, or permanent deletion.

The server exposes exactly 27 tools for creation, authorized and workspace-only discovery, bounded reads and updates, organization, reversible trash/restore, and restricted permission management. Every caller-supplied item or parent ID is re-fetched through files.get; successful resources are classified in memory as workspace descendants or directly authorized resources. External folders are metadata and destination-only. Google Docs reads and whole-content replacements support single-tab documents only; multi-tab documents are rejected. Google Sheets reads and updates require an explicit bounded A1 cell or rectangular range. Sheet reads preserve Google's sparse row arrays without padding, so trailing empty rows and cells may be omitted and returned row lengths may differ; create and update values remain rectangular.

Writes are dispatched once. If a dispatched write cannot be proven complete, the tool returns WRITE_UNKNOWN_OUTCOME; callers must not replay it automatically. Provider bodies, bearer values, file contents, and recipients are not included in errors or logs.

See ENTERPRET.md for the complete managed contract and README_UPSTREAM.md for the preserved upstream documentation. Third-party provenance is recorded in THIRD_PARTY_NOTICES.md.