{"id":"bantunes82-mcp-google-drive-server","name":"mcp-google-drive-server","af_score":38.5,"security_score":61.5,"reliability_score":15.0,"what_it_does":"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.","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.","last_evaluated":"2026-04-04T20:00:49.401030+00:00","has_mcp":true,"has_api":false,"auth_methods":["Google Application Default Credentials (ADC) for accessing Google Drive","OAuth2 client_credentials for securing the SSE/HTTP transport (token endpoint at localhost:8080/oauth2/token)"],"has_free_tier":false,"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"],"error_quality":0.0}