workos-gdrive-mcp-server

workos-gdrive-mcp-server is an MCP (Model Context Protocol) server intended to expose Google Drive capabilities to an AI agent/workflow, typically via WorkOS-related integration patterns.

Evaluated Apr 04, 2026 (40d ago)
Homepage ↗ Repo ↗ Infrastructure mcp google-drive workos ai-agents productivity api-integration
⚙ Agent Friendliness
46
/ 100
Can an agent use this?
🔒 Security
56
/ 100
Is it safe for agents?
⚡ Reliability
10
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
45
Error Messages
0
Auth Simplicity
55
Rate Limits
30

🔒 Security

TLS Enforcement
75
Auth Strength
70
Scope Granularity
35
Dep. Hygiene
50
Secret Handling
45

Security posture depends on how the MCP server stores and forwards OAuth tokens/credentials and how it applies least-privilege scopes. TLS is generally expected for Google API calls, but specific enforcement and secret handling details are not provided in the prompt.

⚡ Reliability

Uptime/SLA
0
Version Stability
0
Breaking Changes
0
Error Recovery
40
AF Security Reliability

Best When

You are already using MCP-based agent tooling and want Drive operations available as callable tools.

Avoid When

You need a documented REST/OpenAPI interface, SDKs, or you cannot manage OAuth credentials/scopes safely.

Use Cases

  • Letting an AI agent list, read, and manage files in Google Drive using MCP tool calls
  • Building agentic automations that operate on Drive content (search, download, upload, metadata updates)
  • Integrating Drive operations into multi-step workflows with an LLM that can call MCP tools

Not For

  • Direct end-user UI applications
  • Handling highly sensitive workloads without a vetted security model and least-privilege OAuth scopes
  • Use cases that require a stable REST/SDK-only integration path (since this package is MCP-focused)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: OAuth (Google Drive access via OAuth credentials)
OAuth: Yes Scopes: No

Auth requirements and exact OAuth/scopes are not provided in the prompt; assume OAuth-based Google authorization for Drive access.

Pricing

Free tier: No
Requires CC: No

Pricing not provided in the prompt (WorkOS and/or hosting costs may apply).

Agent Metadata

Pagination
unknown
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • OAuth/token management pitfalls (refresh, expiry) can break tool calls mid-session
  • Drive operations may have rate limits and quota constraints; agents should expect throttling
  • Large file operations may be slow/time out without chunking or resumable upload handling (if not implemented)
  • Google Drive permissions/sharing model can cause unexpected 403/404 behavior depending on visibility

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for workos-gdrive-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered