Google Drive AI Agent
Search and read your Google Drive with an AI agent. Summarize docs, answer questions across files, and automate reports with Oido — self-hostable, multi-provider.
What you can automate with Google Drive + Oido
- Ask 'what's in the Q3 planning doc?' and get a grounded summary in your channel.
- Search across Drive for the contract that mentions a clause — without opening Drive.
- Compile a weekly digest from a folder of meeting notes on a schedule.
- Pull figures out of a spreadsheet and format them into a report the agent emails out.
Oido connects to Google Drive through the Google Drive MCP server, giving your agent search and read access to your files. Your documents become a knowledge source the agent can answer from — on demand or on a schedule.
How it works
The Drive MCP server authenticates with Google OAuth and exposes file search and content reading as agent tools. Oido runs the agent in a channel or on a cron schedule, so the answer to "where's that doc and what does it say?" arrives where you're already working.
Read access is the safe default: the agent reads and reasons over your files, it doesn't modify them. Combine with Postgres or GitHub to blend document context with live data.
Setup
Install the Google Drive MCP server as an Oido extension:
oido extensions install @modelcontextprotocol/server-gdriveOr add it directly to ~/.config/oido/mcp-servers.json:
{
"servers": {
"google-drive": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-gdrive"
],
"env": {
"GDRIVE_CREDENTIALS_PATH": "${GDRIVE_CREDENTIALS_PATH}"
},
"transport": "stdio"
}
}
}GDRIVE_CREDENTIALS_PATH — Path to your Google OAuth credentials JSON (created in Google Cloud Console).
Confirm the exact source and env vars against the Google Drive MCP server — package names occasionally change.