Best for
- Individuals or teams that need an assistant to search Google Drive documents and sheets
- Knowledge workflows using cloud documents as grounded question-answering context
G
55FMRS · C
Cloud-document retrieval is valuable, but OAuth setup and document exposure require strict control; community maintenance and the real authorization flow still need runtime verification.
This community-maintained server uses OAuth to access Google Drive. It supports full-text search and reading Google Docs and Sheets content so cloud documents can be used as conversational context.
Tools
search_files
Search files in Drive by content
read_file
Read document or spreadsheet content
list_files
List files in a folder
export_document
Export a document to another format
Setup
Create OAuth credentials in Google Cloud Console, download credentials.json, and complete the authorization flow once.
claude_desktop_config.json
{
"mcpServers": {
"gdrive": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-gdrive"],
"env": {
"GDRIVE_CREDENTIALS_PATH": "./credentials.json"
}
}
}
}
Fit and risk
Not for
- Highly sensitive organizations that cannot allow model processing of Drive content
- Administrative workflows requiring full edit, sharing, or deletion controls
Required permissions
- Google Cloud OAuth client credentials
- Read access to the target Drive files with the corresponding read-only OAuth scope
Risks and side effects
- Search results and document bodies may contain personal, customer, or internal data
- Overbroad authorization can expose files unrelated to the intended workflow
Troubleshooting
- Confirm the required API is enabled in the Google Cloud project
- Check OAuth consent-screen and test-user settings
- Delete the old token and authorize again after changing scopes
Use cases
Find information across a team's document archive
Summarize data from multiple spreadsheets
Answer questions using source material stored in Drive
Supported clients
Claude DesktopFull support
CursorPartial support