Official Vendor Server
Google✦ Lab Verified
Google Drive
Access and search Google Drive files including Docs, Sheets, and Slides. Enables AI-powered document retrieval and analysis.
9.1/10
Score
669ms
Latency
100%
Uptime
1
Tools
OAuth
Auth
Ecosystem
Google MCP Servers
4 specialized servers, 47 tools tested independently. Each link leads to a full review with tool-level evidence.
| Server | Score | Security |
|---|---|---|
| Google Calendar | 93/100 | 10/10 |
| Google Maps | 90/100 | 10/10 |
| 87/100 | 10/10 | |
| Gmail | 87/100 | 10/10 |
Quick Verdict
HOOK:
Use this for basic Google Drive file searches. Avoid it if you need write operations or team management since only search was tested. Best area: file discovery. Biggest failure: limited test coverage with just 1 tool verified.
Lab Review
What We Found
What works: The search tool delivers the essentials cleanly. We ran OAuth-authenticated searches against Google Drive's API and got structured file metadata back in 669ms. That latency is reasonable for cloud storage searches - you get file names, IDs and permissions data without authentication hiccups or malformed responses. Where it breaks: Our test coverage hit a wall. Only 1 out of the server's full tool set was executable in sandbox mode. The remaining tools require paid Google Workspace features or live file fixtures that testing environments can't provide. This means we can't verify how file downloads, folder operations, or sharing controls actually perform when you need them. What this means for your workflow: File search operations are solid and you can build read-heavy workflows on them. However, you're flying blind on everything else until you test in your actual Google Workspace environment. The OAuth setup requires manual credential configuration, so budget time for that initial auth dance. For teams doing basic Drive searches, this is ready. For anything beyond search, you need to validate the other tools yourself first.
Lab Observations
What actually happened during testing
During testing, our scanner interacted with Google Drive. 1 tool succeeded.
| Tool | Status |
|---|---|
| search | ✅ success |
Reliability
Full runtime test completed. Score based on transport stability and schema completeness.
Score Breakdown
Reliability
1 of 1 executed tools succeeded.
Security
Score based on schema analysis and dependency audit.
Setup
Remote server with OAuth authentication.
Docs
1 tools with descriptions and input schemas.
Compatibility
Standard MCP protocol. Transport: OAuth.
Maintenance
Based on commit frequency, releases, and contributor activity.
Tools
1 available tools
Search for files in Google Drive
FAQ
Frequently asked questions about Google Drive
What latency can I expect from Google Drive search operations?+
We measured 669ms for the search tool execution during our testing. This represents the time from request initiation to response completion when querying Google Drive files and folders through the MCP server interface.
Which Google Drive scopes are required for basic functionality?+
Our testing used drive:readonly scope, which allowed successful execution of the search tool. This read-only scope provides access to view and search files without modification permissions. The server operated without requesting additional scope elevation during our test session.
How does the server handle OAuth authentication setup?+
The server uses remote_oauth transport for Google Drive API access. During our testing, OAuth credentials were successfully established and maintained throughout the session. We observed no authentication token refresh issues or credential validation failures during tool execution.
What happens when search operations return large result sets?+
The search tool completed successfully in our testing environment, handling the query and response processing within 669ms. We observed proper result formatting and no truncation errors, though our specific test query scope was limited to sandbox data volumes.
Are there limitations in sandbox testing environments?+
We discovered that only 1 out of the total discovered tools was available for execution in our sandbox environment. The remaining tools were excluded due to paid features, fixture limitations, or sandbox constraints rather than security policies.
What error handling occurs during failed operations?+
While our search tool executed successfully, the server implements standard MCP error response protocols. Based on the transport configuration, authentication failures or API quota issues would return structured error messages through the MCP interface rather than raw Google API responses.
How does the server manage Google Drive API rate limits?+
During our single tool execution, we observed no rate limiting interference. The 669ms response time for search includes any API throttling that occurred server-side. The server maintained connection stability throughout the test session without retry mechanisms being triggered.
Related
Explore more
Testing History
Community
Community Reviews
No community reviews yet. Be the first to share your experience!