mcp-google-drive-server
Provides an MCP server that connects an MCP client (e.g., Claude Desktop) to Google Drive, exposing at least one tool to upload Microsoft Word content to a specified Google Drive folder (returning a Google Docs-view URL). Supports both MCP stdio and an SSE/HTTP transport mode, with OAuth2 protection for the SSE/HTTP mode.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Transport security is implied but not explicitly documented (curl example uses -k and token endpoint is http://localhost:8080, which suggests TLS behavior is unclear). Authentication for Google Drive access uses ADC via GOOGLE_APPLICATION_CREDENTIALS. The server’s SSE/HTTP transport is secured with OAuth2 client_credentials and uses scopes (mcp.read mcp.write) per example, which is a positive sign for authorization segmentation. Rate limits, token handling guidance, and error/exception behavior are not documented in the provided README.
⚡ Reliability
Best When
You want a simple MCP integration to write documents into Google Drive from an MCP-capable desktop client, and you can supply Google Application Default Credentials.
Avoid When
You need a complete REST/SDK experience, well-specified error codes, or strong documented rate-limit/idempotency semantics for repeated tool execution.
Use Cases
- • Uploading Word (.doc/.docx content) to Google Drive via an MCP client
- • Automating Drive organization by selecting a target Drive folder by name
- • Enabling LLM workflows that create and store documents in Google Drive
Not For
- • Production systems requiring robust operational guarantees without further validation
- • Uploading large files or high-volume/batch workloads without confirmed limits and backpressure
- • Use cases needing fine-grained permissions, audit trails, or full CRUD tool coverage (only one tool is documented)
Interface
Authentication
README indicates OAuth2 is used to secure the server for SSE mode; example token response includes scopes like 'mcp.read mcp.write'. For stdio mode, auth is driven by GOOGLE_APPLICATION_CREDENTIALS (ADC).
Pricing
No pricing information provided.
Agent Metadata
Known Gotchas
- ⚠ Tool schema only documents upload_microsoft_world_file; other Drive operations (search/list/delete) may not exist
- ⚠ For SSE mode, token is noted as only valid for ~5 minutes (manual refresh may be needed by the agent)
- ⚠ Auth requirements differ by transport: stdio uses GOOGLE_APPLICATION_CREDENTIALS; SSE example uses OAuth2 client_credentials with a local token endpoint
- ⚠ README does not document idempotency; repeated runs may create duplicate uploads unless the server implements deduplication internally (not stated)
- ⚠ No rate-limit documentation provided
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-google-drive-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.